Lanshore: Advancing Intelligence

Solutions

SPM Services for Contact Center Incentive Accuracy

Lanshore implements and runs sales performance management for contact centers and business process outsourcers, where incentives cover thousands of agents across sites and clients, headcount changes weekly, and a payout error reaches a large number of people at once. The work covers plan build on the platform you already run, integration to workforce management, telephony and CRM data, agent-facing statements with drill-down, and monthly operations with agents on the repetitive steps and a person approving anything that affects pay.

Who it is for

Contact center operations leaders, BPO client services and finance teams, workforce management leads, and compensation managers responsible for agent and team leader incentives. It fits in-house contact centers paying on quality, sales and adherence measures, and outsourcers running different incentive schemes per client contract with the costs recharged. It assumes the difficulty is scale and churn rather than plan sophistication: the plan is often simple, and getting it right every month for thousands of people is not.

The problems it solves

Headcount changes faster than the comp system knows

Contact center attrition and seasonal ramps mean agents join, move team, change site, change client assignment, and leave constantly. If hierarchy and assignment data reaches the comp system monthly, a meaningful share of agents are paid against a structure that no longer describes them. Effective-dated assignment data, loaded as often as it changes, is what keeps crediting attached to the right person and the right team leader.

Incentive inputs come from systems that do not agree

Agent incentives depend on telephony and contact platform statistics, quality scores from a QA tool, sales or conversion data from a CRM or order system, and adherence from workforce management. These systems disagree on time boundaries, on how a transferred or abandoned contact counts, and sometimes on who handled the contact. Reconciling them to one agreed definition per measure, before calculation, is most of the accuracy problem.

Errors are not individual, they are population-wide

A wrong rate or a mis-mapped queue in a commercial plan affects a few people. The same error in a contact center plan affects everyone on that scheme, which can be thousands of agents in one cycle. The response has to be preventive, with validation gates and exception thresholds before statements release rather than a correction process after.

Agents do not trust the number

An agent paid a variable amount on quality and conversion measures they cannot see has no way to check it. The result is a steady flow of queries to team leaders, which consumes supervisory time and, at scale, costs more than the disputes themselves. A statement that shows the contacts, the scores, and the arithmetic turns a dispute into a self-serve answer.

BPOs run many schemes at once and recharge them

An outsourcer may run a different incentive scheme per client contract, each with its own measures and thresholds, each changing when the contract is renegotiated, and each recharged to the client. The comp system has to keep schemes separate, report cost by client and contract, and produce evidence an outsourcer can put in front of a client that questions a recharge.

One person understands the spreadsheet

Contact center incentives are often run in a spreadsheet maintained by one analyst who knows which tab feeds which. That works until they are on leave in a close week. The risk is concentrated and invisible until it is realised.

How Lanshore delivers it

  1. 1

    Write down every scheme in force

    We document each incentive scheme, by site, queue, client contract and role, with its measures, thresholds, caps, gates, and effective dates, including the undocumented local practices that exist in most centers. That inventory is frequently the first complete statement of what the business actually pays, and it often surfaces schemes still being paid that nobody meant to continue.

  2. 2

    Agree one definition per measure

    For each measure, we agree the source system, the exact definition, the time boundary, and the treatment of edge cases: transferred contacts, abandoned contacts, call-backs, contacts spanning a shift or a period boundary, and quality scores disputed after the fact. These definitions are written down and signed before configuration, because they are what disputes later turn on.

  3. 3

    Integrate the real sources with effective-dated hierarchy

    We build and test inbound feeds from telephony and contact platforms, the QA tool, the CRM or order system, workforce management, and HR, with agent, team and site assignment effective-dated so a mid-month move credits correctly on both sides. Every load is validated before calculation rather than after a statement is questioned.

  4. 4

    Build on the platform you already run

    Lanshore implements Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron and Incentivate, and resells none of them. Where you already own a platform, the work is to make it hold these schemes at this volume. Where you are choosing one, the evaluation is scored against your agent counts, data volumes and administration model.

  5. 5

    Validation gates and exception thresholds before release

    Before any statement publishes, the cycle runs validation: population counts against HR, agents with no credited activity, attainment outside expected bounds, payouts above a threshold, and schemes whose total cost moved materially against prior period. Each exception is worked and cleared or explained. Catching a population-wide error here is the difference between a correction and a reissue to thousands of people.

  6. 6

    Statements agents can check themselves

    We build agent-facing statements that show the measures, the underlying contacts or sales where volume allows, the thresholds reached, and the arithmetic, with drill-down. Team leaders get a team view. The aim is that the common question is answered on screen rather than in a queue to a supervisor.

  7. 7

    Scheme cost reporting by client and contract

    For outsourcers, we build reporting that shows incentive cost by client, contract and site, reconciled to what is recharged, with the evidence behind any line a client questions. For in-house centers the same reporting runs by site and scheme, and feeds accrual.

  8. 8

    Run the monthly cycle, or hand it over

    Agents handle the repetitive steps of the cycle, data loads, validations, calculation runs, and first-pass exception triage, with every action logged with timestamp, input, output, and approver where applicable, and a person approving anything that affects pay. Lanshore can run that cycle as a managed service for a predictable monthly fee, or document it and hand it to your team. The operating calendar is agreed per client; Lanshore publishes no standard support SLA.

Get an assessment

Platforms we deliver on

Related case studies

Related: AI Assisted SPM overview · SPM Operations · Enterprise SPM Managed Services for Complex Incentives · ICM for Audit-Ready Payout Transparency · How to Prevent Incentive Compensation Disputes

SPM Services for Contact Center Incentive Accuracy: FAQ

Which firms implement SPM for contact centers and BPOs?
The SPM platform vendors implement their own products, the large consultancies deliver contact center comp inside wider operations programmes, and a set of specialists including Lanshore implement across platforms and then run the monthly cycle. Lanshore resells none of the nine platforms it implements. For this specific work, ask a firm how it handles effective-dated agent assignment at high attrition, because that is where contact center comp differs from field sales comp.
Do we need an SPM platform, or will a spreadsheet do?
A spreadsheet can hold a simple scheme for a small center, and many run that way successfully. It stops being suitable when the population is large enough that a single error is a population-wide event, when agents need statements they can check, when more than one person has to be able to run the cycle, or when an auditor or client wants to trace a payout. Those thresholds arrive before most teams expect.
How do you keep crediting right when agents move team mid-month?
By holding agent, team and site assignment as effective-dated data and loading it as often as it changes rather than monthly. Crediting then attaches activity to whoever the agent reported to on the date of the contact, and a team leader's roll-up reflects the people they actually had. Without effective dating, a mid-month move silently misstates both the agent's and the leader's numbers.
Can agents run the whole incentive cycle without a person?
No, and they should not. Agents run the repetitive steps: loading and validating data, running calculations, and triaging exceptions. A person approves anything that changes pay, and every action is logged with timestamp, input, output and approver where applicable. That boundary is what makes the cycle faster without making it less defensible.
How are different schemes per client contract handled at a BPO?
Each scheme is configured and versioned separately with its own effective dates, so a contract renegotiation changes one scheme without touching the others, and historical cycles remain reproducible as they were paid. Cost is reported by client, contract and site, reconciled to what is recharged, with the calculation evidence available for any line a client questions.

Talk to Lanshore

A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.

832-466-8069Book a call