Skip to main content

vimiTeam

Group employees into a commission team where collective sales or service performance drives tiered rewards for everyone.

What is it?โ€‹

vimiTeam is how you turn individual effort into a shared goal. You group staff into a named team, decide the reward tiers (M1 through M5), pick whether the team is driven by sales revenue or service targets, and set each member's share of the payout. Throughout the cycle, every sale a member submits through vimiSales is automatically aggregated into the team's total - you don't need to re-enter anything. The team's current tier updates in real time, and when the cycle ends, qualifying members receive their share of the tier reward in vimiBank.

The boss-as-reviewer piece is what makes vimiTeam useful: by linking vimiGoal records to a team, you can require every member to hit a minimum goal completion rate before they qualify for the team reward. Someone who is a top seller but regularly skips their daily check-ins won't collect. This gate is what stops payout from becoming a popularity contest.

Use vimiTeam when the reward should belong to the team collectively - retail branches, property teams, kitchen crews, service squads. For purely individual commission, stay with vimiSales.

Quick Startโ€‹

  1. Go to "vimiTeam 2.0 Settings".
  2. Click the "New vimiTeam" card.
  3. Fill Step 1 (name, "Period", "Type" = Sales or Service), assign employees, click "Next".
  4. Walk through Step 2 (link vimiGoals), Step 3 (link vimiSales), and Step 4 (set tier rewards and each member's "Percentage (%)").
  5. Click "Publish".

The team is live. Members see their team's progress in the mobile app; the tier updates every time a linked sale is submitted.

For Admins (Employer / HR / Manager)โ€‹

How to create a sales teamโ€‹

  1. Navigate to "vimiTeam 2.0 Settings". Click the "New vimiTeam" card.
  2. Step 1 - vimiTeam Information:
    • "vimiTeam Title" - e.g. "KL Flagship Sales Team".
    • "Select Template" - click the industry card that matches your business (Retail, F&B, Property, etc.) to pre-fill suggested tiers.
    • "Start Date" / "End Date" - cycle boundaries.
    • "Period" - Monthly is standard.
    • "Repetition (Maximum 99)" - e.g. 12 for a year of monthly cycles.
    • "Type" - "Sales" for revenue-driven, "Service" for days- or quantity-driven.
    • "Mission Type" - what the targets measure: $, QTY, or DAY.
    • "Exclude Goal" - leave as "No" to require goal completion, or "Yes" to bypass the goal gate.
  3. Assign team members, click "Next".
  4. Step 2 - Set vimiGoal: link one or more existing vimiGoal records. These act as the qualification gate.
  5. Step 3 - Set vimiSales: link the vimiSales records whose submissions should flow into the team total.
  6. Step 4 - vimiTeam Settings:
    • Under "No. of Mission(s) Enabled", toggle "M1" through "M5" for the tiers you want.
    • Fill the "Sales Team Allowance" table: "Label" (e.g. Bronze, Silver, Gold) and "Reward ($)" per tier.
    • In "Rewards Allocation (Sales)", set each member's "Percentage (%)". The total must equal 100%.
  7. Click "Publish" (or "Save as Draft").

Warning: "Type", "Period", and "Mission Type" are locked once you publish. To change them, copy the team and edit the draft.

How to set up a service teamโ€‹

Use this for restaurants, clinics, cleaning services - any team where performance is days worked or tasks completed, not RM revenue.

  1. In Step 1, set "Type" to "Service" and "Mission Type" to "DAY" or "QTY".
  2. In Step 4, you'll see a "Service Team Mission" table alongside the reward table. Fill both:
Tiers for a restaurant kitchen (DAY type):

M1 Standard 20 days RM 200
M2 Good 23 days RM 400
M3 Excellent 26 days RM 600

A cook who attends 24 days โ†’ at M2 โ†’ gets RM 400 ร— their allocation %.
  1. Pick "Rewards Formula":
    • "Standard" - reaching M3 earns only the M3 reward.
    • "Accumulative" - reaching M3 earns M1 + M2 + M3 combined (requires your company to have the Accumulative formula module enabled).

How to add a support team allowance (hybrid)โ€‹

Sometimes a sales team has back-office staff who should also earn when the team hits targets, just at a different rate.

  1. On Step 4, tick "Add support team?". A "Support Team Allowance" table appears.
  2. Fill it with the support-side amounts (e.g. M1 RM 100, M2 RM 200, M3 RM 300).
  3. In "Rewards Allocation (Support)", assign percentages to the support members. Totals must equal 100%.

Sales and support members now earn from their own tier table when the team's collective sales cross a threshold.

  1. Create the team with "Exclude Goal" = "No" (the default).
  2. On Step 2, search and pick the vimiGoal records to link.
  3. Confirm in Company Settings that minimum_goal_requirement is set to the threshold you want (typical values: 70 or 80).
  4. When payout runs, members whose average goal rate is below the threshold are marked "Not Qualified" and excluded.
Team "North Sales" has two linked goals.
Minimum requirement: 80%.

Ahmad - daily activity 90%, weekly calls 70% โ†’ average 80% โ†’ qualifies.
Budi - daily activity 60%, weekly calls 65% โ†’ average 62.5% โ†’ NOT qualified.

Team hits M2 tier. Ahmad gets his M2 share. Budi gets nothing.

To bypass the gate for a specific team, set "Exclude Goal" to "Yes".

How to close a team and run the payoutโ€‹

  1. When the cycle ends, the team auto-closes (status changes to Closed โ†’ Pending Payment). If "Manual Closing" is ticked on the team, close it yourself from the team dashboard.
  2. Navigate to "Payouts" โ†’ "Select Month". Pick the relevant month.
  3. Step through "Select Department".
  4. Review the member list - anyone marked "Not Qualified" was below the minimum goal rate.
  5. Confirm the payout.

Members see the commission split into two tranches in their vimiBank history - "Team Commission (Small)" released after the Bank A buffer (typically 3 months) and "Team Commission (Big)" after the Bank B buffer (typically 6 months). Your company can adjust these buffers in Company Settings.

How to handle a member exceptionโ€‹

When someone goes on leave or leaves the team mid-cycle:

  1. Open the team's "vimiTeam Settings" from the dashboard.
  2. In the member list, create a member exception with the start and end dates of the exclusion.
  3. Historical records are untouched; the exception takes effect at the next cycle boundary.

If the team uses manual split mode, the departed member's reward share goes to "Pending Split" status. Go to the main "vimiTeam 2.0 Settings" page, click "Split Rewards Manually", and allocate the share to the remaining members. In auto split mode, the system redistributes proportionally without you doing anything.

For Employeesโ€‹

How to see your team's progressโ€‹

  1. Open the vimigo mobile app.
  2. Navigate to Commission โ†’ vimiTeam.
  3. Pick the active team. You see:
    • "Current Mission" - the tier the team is at right now (e.g. M2).
    • A progress bar showing where the team stands between M1 and the maximum tier.
    • Your projected reward at the current tier.
    • A "vimiTeam Ends in" countdown.

If your team's achieved amount is hidden, your admin has the "Show Achieved Amount to Members" setting off. Ask them to enable it if the team wants the number visible.

How to check your goal qualificationโ€‹

If your team has linked vimiGoals (and the goal gate isn't excluded), your individual goal completion rate decides whether you qualify for the reward.

  1. On the team dashboard, tap the "vimiGoal" tab.
  2. It shows the "Overall Goals Performance" percentage - the team average.
  3. Your personal rate is compared against the company minimum (e.g. 80%).
  4. If yours is too low, submit outstanding vimiGoal progress before the cycle ends.

How to understand your reward statusโ€‹

When the cycle closes, the payout list shows one of these statuses next to your name:

StatusWhat it means
Not ProcessedCycle ended; payout hasn't been initiated yet
Paid Bank ASmall payout (typically 3 months after close) has been credited
Paid Bank BLarge payout (typically 6 months after close) has been credited
All PaidBoth banks paid
Not QualifiedYour goal rate was below the minimum - no reward this cycle
NILNo reward (team didn't reach M1)
Pending SplitA member left mid-cycle; admin is splitting the share manually

How push notifications workโ€‹

When the team crosses a new tier, every member gets a push notification ("Your team has reached M2!") and an in-app alert. No action needed - the alert fires automatically from a teammate's vimiSales submission.

If you aren't getting pushes, check that notifications are enabled for the vimigo app on your phone and log out and back in to refresh your device token.

Settings & Configurationโ€‹

SettingWhat it doesDefaultWhere
"Type"Sales (revenue-driven) or Service (attendance/quantity-driven)-Step 1
"Mission Type"$, QTY, or DAY - the unit of the targets-Step 1
"Period"Daily, Weekly, Monthly, Quarterly, Biannually, Triannually, or YearlyMonthlyStep 1
"Repetition"How many cycles in a row (max 99)1Step 1
"Exclude Goal"Yes bypasses the goal qualification gateNoStep 1
"Add support team?"Adds a separate Support Team Allowance tier tableOffStep 4
"No. of Mission(s) Enabled"Tick any combination of M1โ€“M5 (at least M1 required)M1Step 4
"Rewards Formula"Standard (highest tier only) or Accumulative (all tiers stack)StandardStep 4 (Service teams)
"Manual Closing"Admin closes each cycle manuallyOffStep 4
"Split Reward Manually"Manual split requires admin action when a member leaves; auto-split redistributes automaticallyAutoStep 4
Show Achieved Amount to MembersWhether the team total is visible in the mobile appOffCompany Settings
Minimum Goal RequirementMinimum average goal rate (%) for payout qualification-Company Settings
Bank A / Bank B BufferMonths between cycle close and each payout tranche3 / 6Company Settings

Reward types availableโ€‹

The commission payout can be distributed through several channels depending on how your company has configured Bifrost automations:

ChannelWhat the member sees
vimiBank Cash (Bank A)Transaction labelled "Team Commission (Small)"
vimiBank Cash (Bank B)Transaction labelled "Team Commission (Big)"
DiamondPush notification + Diamond balance update (via Bifrost)
EWF CreditAppears in the Employee Welfare Fund wallet
BadgeShows on the member's profile
vimiRewards ItemAppears in the member's vimiRewards history

Bifrost is the automation engine that fires rewards automatically when the team crosses a tier. Ask your account admin which channels are configured for your company.

FAQโ€‹

Q: The team was created but shows as "Draft" with no data.

A: You didn't finish the wizard. Open it, walk through all four steps, and click "Publish". Drafts don't accumulate data.

Q: "Failed to create setting. You need to reduce the assigned staffs or reduce the repetition to be less than 31."

A: Your "Start Date" is far enough in the past that the system would need to generate too many historical records. Either move the start date forward or lower the "Repetition" count.

Q: Members can't see the team's achieved amount in the app.

A: The "Show Achieved Amount to Members" setting is off. Ask your system admin to enable it in Company Settings.

Q: Goal completion rate shows 0% for all members.

A: Goals are linked but nobody has submitted vimiGoal progress yet for this cycle. Either get members to submit, or if goal tracking isn't appropriate for this team, toggle "Exclude Goal" to "Yes".

Q: A member shows "Not Qualified" even though the team hit a tier.

A: Their average goal completion rate is below the company's minimum goal requirement. Check their goal submissions for this cycle. To qualify them, they need more goal completions, the admin needs to lower the minimum, or the team needs the goal gate disabled.

Q: The tier hasn't moved even though we submitted vimiSales records.

A: Verify the vimiSales record is linked to the team - check the "vimiSales" tab on the team dashboard. If it's linked, the recalculation runs as a background job; give it a few minutes.

Q: I removed a member but they still appear in the next cycle.

A: Member removals are applied as exceptions that take effect at the next cycle boundary. Your server admin may need to verify the scheduled job that converts exceptions is running.

Q: Payout shows "Pending Split" for a member.

A: That member's reward is in manual split mode. Go to the main "vimiTeam 2.0 Settings" page, click "Split Rewards Manually", and allocate the share.

Q: Can I change the interval type after publishing?

A: No. "Type", "Period", and "Mission Type" are locked after publishing. Use "Copy" to duplicate the team, change what you need in the draft, and publish that instead.

Q: Copying a team - does it bring the members?

A: Yes. The copy starts in Step 1 of the wizard with the same commission structure and member list.

Q: Can I add members to a live team?

A: Yes. On the team dashboard, go to "vimiTeam Settings" and add the new member. They'll receive cycle records from the current cycle onward; closed cycles aren't affected.

Q: Two teams have the same sales people - will their sales double-count?

A: Yes, by design. The same vimiSales record can be linked to multiple teams and counts in each team's total. If you don't want that overlap, link different vimiSales records to each team.

Q: What's the difference between Standard and Accumulative formula?

A: With Standard, reaching M3 gets you only the M3 reward. With Accumulative, reaching M3 gets you M1 + M2 + M3 added together. Accumulative requires a company module flag - ask your admin whether it's on.

  • vimiGoal - link goals to a team as a qualification gate. Members below the minimum rate forfeit the reward.
  • vimiSales - every sale from a team member flows into the team total automatically; vimiSales is the engine that powers a Sales-type vimiTeam.
  • vimichallenge - for one-off team dares with a fixed deadline, use vimiChallenge rather than creating a short-lived vimiTeam.
  • vimireview - customer ratings can feed vimiClass, which some companies weigh alongside team performance.
  • Diamond - Team-wide diamond awards for hitting joint targets.
  • vimiBank - Team commission distribution.