The belief goes like this: performance is low, so raise the incentive. Put more money on the table and agents will try harder, sell more, answer faster. It sounds like plain common sense, and a lot of operations managers act on it every quarter. Sometimes it even works. But as a general rule it is wrong, and an incentive scheme designed on that belief is more likely to produce a new set of problems than a better floor.

Pay shows people what you really want

An incentive is a message. It tells agents which numbers the company will reward, whatever the posters say about customer delight. There is an old observation, often called Goodhart’s law, that when a measure becomes a target it stops being a good measure. Contact centres demonstrate this daily.

Pay a bonus on low average handle time and some agents will rush callers, transfer difficult calls, or cut the line after a minute of silence. Pay on number of sales and mis-selling rises. Pay on CSAT survey scores and agents begin asking customers for a five, or only passing happy callers to the survey. Pay on attendance and sick people come in. Each of these is the scheme working exactly as written, not an agent being dishonest. The scheme asked for the wrong thing, or for one thing without the others.

Three design questions

What can the agent actually control? An agent cannot control call volume, system downtime or customer mood. A target that depends mostly on these feels like a lottery and stops motivating. Metrics such as quality, adherence, sales conversion on offered opportunities, and resolution are better than raw volume. Even then, check for fairness: an agent given the difficult queue should not be compared with one handling easy calls.

Can the agent see the link between effort and payout? If the formula needs a spreadsheet and a calculator, people stop trying. A good scheme can be explained on one page, and an agent can check during the month roughly where they stand. Frequent feedback, weekly or even daily, beats a number that surprises people on the pay slip.

What happens when targets conflict? This is where gates help. A gate is a minimum standard on one metric that must be met before any incentive on another is paid. For example: sales incentive is paid only if the quality score is above a threshold and there are no compliance fatals. This stops the rush-for-volume behaviour without needing to weigh quality against sales in one formula. A gate is blunt, but blunt is useful for non-negotiables like compliance.

A worked example of cost and shape

Take an invented team of 60 agents with a maximum monthly incentive of ₹4,000 each. If everyone earned the maximum, the monthly cost would be ₹2.4 lakh, or ₹28.8 lakh a year. Nobody earns the maximum, so the real cost is lower, and finance will budget on an expected payout, say 60 to 70% of the maximum. That is a sensible number to plan against, and a good check on whether your slabs are doing what you meant. If 95% of people hit the top slab, the target is too soft and the incentive has become salary. If only 5% hit anything, the target is too hard, and the scheme is noise to the other 95%.

Shape matters too. Steep slabs, where one point decides a jump from ₹500 to ₹2,500, create cliff-edge behaviour in the last week of the month, including gaming. Gentler ramps are harder to game and feel fairer. Team-based components, such as a share linked to the team’s overall service level, encourage helping each other, but a purely team incentive lets weak performers coast. Many schemes use a mix: a mostly individual payout with a smaller team element.

When cash is the wrong tool

Agents do not leave only for money. Reasons people give for leaving include poor supervision, night shifts, no visible career, an unfair roster and feeling unseen. A ₹2,000 bonus does not repair these. Non-cash recognition, a clear path from agent to senior agent to team leader, a say in shift preferences, and a supervisor who explains and listens often do more per rupee. I would not claim they always replace cash, and many surveys of workplaces suggest pay does matter as a basic expectation. The practical point is that incentives work best on top of a fair base, and poorly as a patch for a bad one.

Checks before launch

  • Run last quarter’s data through the proposed formula to see who would have been paid, and ask whether that list looks right.
  • List the three easiest ways to game each metric, then add a control or audit for each.
  • Decide what happens in a month with system downtime or a client-driven change: freeze, adjust or exclude?
  • Plan how disputes are handled. A transparent dispute route builds more trust than a perfect formula.
  • Review after two or three months for unintended behaviour, and be willing to change it. Schemes that never change are being gamed, whether you can see it or not.

Also check with HR and legal how the incentive interacts with salary structure, statutory contributions and any client rules about what may be paid for, since this varies by company and sometimes by state. And note that in regulated sales, such as insurance and loans, incentive design is increasingly scrutinised for mis-selling risk, so compliance should sign off on it.

So, the myth in a sentence: the amount of money matters less than what it is attached to. Choose the metric first and the rupee amount last.

Figures and names in the examples are illustrative.

Leave a Reply

Trending