The 4 operational performance indicators to lock in
An offshore customer support SLA without precise operational indicators is a contract that protects the provider, not you. These first four KPIs measure what your customers directly experience.
First response time: not the average delay, the P95
The classic trap: your provider tells you their average first response time is 12 minutes. Great. Except 5% of your customers are waiting 4 hours. And those are the ones leaving scathing Google reviews.
Never negotiate an average time. Demand a 95th percentile. That means 95% of tickets must receive a first response in under X minutes. The remaining 5%, you cap with an absolute ceiling.
Concrete example: an e-commerce business based in Lyon outsourced its chat support. Their contract stated "response within 15 minutes on average". Their provider met the number. But Friday evening peaks? 45-minute wait times. Cart abandonment exploded without the SLA being technically breached.
Your clause must stipulate: P95 under 15 minutes, no ticket beyond 30 minutes without automatic escalation. That's how you protect the real experience of your customers, not a misleading average.
First Contact Resolution rate (FCR): the indicator that gets expensive when it's low
Every time a customer has to call back or follow up, you pay twice. The cost of the second handling. And the frustration that erodes loyalty.
FCR is the percentage of requests resolved from the very first interaction. Good offshore B2C support should aim for a minimum of 75%. In B2B, 65% is acceptable if topics are technical.
The problem: many providers inflate their FCR by closing tickets prematurely. The customer hasn't replied within 48 hours? Ticket closed. Resolved. Except the customer simply gave up.
Your SLA must precisely define what constitutes a resolution. A ticket is only resolved if the customer confirms it, or if no reopening occurs within 7 days. Add a quarterly audit clause: you randomly pick 50 tickets and verify them. If the actual FCR is more than 10 points below the declared FCR, there's a penalty. It's the only way to get an honest number. As with tout SLA offshore, la clause sans contrôle ne vaut rien.
Total resolution time: segment by criticality or the number is useless
A forgotten password and a lost order are not the same issue. Yet the majority of offshore contracts measure an overall resolution time. That drowns urgent matters in the noise.
Demand a minimum three-tier segmentation. P1: direct business impact — the customer cannot use the product or has not received their order. Resolution within 4 hours. P2: significant inconvenience but workable. Resolution within 24 hours. P3: question, information request. Resolution within 48 hours.
A B2B SaaS leader learned this lesson after losing a €40,000-per-year account. A critical bug had been handled with the same priority as a billing request. The provider was within the bounds of their overall SLA. The customer left for a competitor.
Your contract must define the classification criteria. Who decides a ticket is P1? Your team, not the provider. That is non-negotiable. A provider that classifies its own tickets controls its own scoring. You see the problem.
The 2 perceived quality indicators to contractualize
Speed alone is not enough. You can respond quickly and poorly. These two indicators measure what your customers actually think of the support you offer them through your offshore team.
Post-interaction CSAT: the thermometer your provider must not control
CSAT is the satisfaction score the customer gives after each interaction. Simple, direct, impossible to game if you are the one managing the survey send.
And that's where things break down. Many offshore providers send the CSAT surveys themselves. They choose the timing, the wording, sometimes even which tickets are eligible. Result: 92% satisfaction. Magnificent. Completely biased.
Your SLA must specify that the CSAT measurement tool is under your control. You decide the frequency, the channel, the question asked. The provider receives the results, not the other way around.
Recommended threshold: CSAT above 85% on a monthly basis, with a minimum 30% response rate for the number to be statistically valid. Below a 30% response rate, the CSAT does not count. That prevents the provider from subtly discouraging dissatisfied customers from responding. And it gives you a number on which you can make decisions.
Quality Assurance score: rate interactions, not just outcomes
CSAT measures customer perception. The QA score measures the reality of the work. Both must coexist in your contract.
The QA score is based on an evaluation grid that you define together. Typical criteria: did the agent use the right tone? Did they follow the escalation procedure? Did they propose a relevant solution? Did they personalize the response?
At Taram, every support team member is dedicated to a single client. European management conducts regular listening sessions and reviews using a grid calibrated to the client's requirements. This is not an annual audit. It's continuous quality control.
Your SLA must require a minimum QA score of 80%, calculated on a sample of at least 5% of monthly interactions. Below that, a corrective action plan within 15 days. If the score remains below the threshold for two consecutive months, financial penalty. The QA score is the only indicator that tells you whether your brand is being correctly represented at a distance, as detailed in ce guide sur la qualité en relation client externalisée.
The NPS trap in an offshore contract
Many providers want to include NPS in SLAs. Refuse.
NPS measures overall loyalty to your brand. It is influenced by the product, price, delivery, and marketing. Your support provider only controls a fraction of the NPS. Attributing the whole thing to them is unfair and above all useless for managing support quality.
Keep NPS as an internal strategic indicator. For the contract, stick to per-interaction CSAT and QA score. These are metrics the provider directly controls and can be held accountable for.
The leader of a 30-person SME in the healthcare sector had included NPS in their offshore contract. Their NPS dropped following a supply chain issue. Their support provider, who was doing solid work, took the penalty. The relationship deteriorated, the provider moved their best agents elsewhere. Double penalty.
Moral: don't pollute your SLAs with indicators the provider doesn't control. Every contractual KPI must be actionable by the party that bears responsibility for it.
The 2 structural indicators that protect your business
The previous indicators measure day-to-day performance. These last two protect your service continuity and your ability to react when things go sideways.
Availability rate and coverage hours: what "24/7" really means
Your provider announces 24/7 coverage. Ask the question: with how many agents at night? Often, the answer is one. Sometimes shared across multiple clients. If that agent is sick, you have zero coverage and no contractual breach because the contract says "24/7" without defining minimum staffing.
Your SLA must specify the minimum number of agents per time slot. European business hours: 3 agents. Evening: 2 agents. Night and weekend: 1 dedicated agent. Not shared. At Taram, one team member works for one client. Period. No sharing, no dilution of attention.
Add a service availability rate: minimum 99.5% per month, measured in minutes of downtime. If the ticketing tool goes down, if the agent is not logged in, it counts. Every hour of downtime beyond the threshold must trigger a credit on the next invoice. Without that, your provider has no financial incentive to maintain continuity. As explained in cet article sur la gouvernance offshore, follow-up rituals replace physical supervision, but the SLA remains the safety net.
Escalation procedure and notification deadline: the invisible SLA that saves accounts
When a VIP client threatens to leave, you want to know within 15 minutes. Not in the monthly report.
Your contract must define an escalation matrix with precise deadlines. Level 1 escalation to team leader: immediate. Level 2 escalation to your team: within 30 minutes for a P1, within 2 hours for a P2. Notification to the business leader: within 1 hour if the matter involves a risk of client loss or a legal issue.
An SLA without an escalation procedure is like a fire alarm system with no fire department phone number. You know it's burning, but nobody comes to put it out.
Also specify the escalation channels. Not an email that will sit unread in an inbox. A Slack or Teams message in a dedicated channel, with a mandatory mention of the relevant person. The contract must name the contacts on both sides with their direct details. And those names must be updated within 48 hours if there is a change.
The penalty and bonus mechanism: what makes the other 7 indicators real
Everything you have read up to this point is worthless without financial consequences.
An offshore customer support SLA without penalties is a statement of intent. Your provider knows it. You should know it too.
Recommended structure: a credit of 5% of the monthly invoice per indicator not met, capped at 20% of the total amount. Beyond 3 consecutive months of non-compliance on the same indicator, right to terminate without notice.
And the other side: include a bonus. If all indicators are exceeded for a quarter, pay a 5% bonus. That aligns interests. It motivates teams. It creates positive momentum instead of a relationship built on mistrust.
One last clause not to overlook: the right to audit. You must be able to access raw data, listen to calls, read tickets, verify timestamps. A provider that refuses the right to audit refuses transparency. That is an immediate red flag. Taram provides full access to the client's tools because the team member works in your environment, with your tools, under your supervision.
An unnegotiated SLA is a blank cheque signed over to your provider
Eight indicators. Not twelve, not three. Eight. First response time in P95. FCR with a strict definition of resolution. Resolution time segmented by criticality. CSAT under your control. QA score with a shared grid. Availability with minimum staffing. Escalation with named deadlines and channels. Financial penalties and bonuses.
Every indicator absent from your contract is an area where your provider will do as they please. Not out of malice. Out of economic rationality. They will optimize what is measured and neglect the rest.
You outsource your customer support to gain efficiency and reduce costs. If your contract does not protect the quality perceived by your customers, you save on the provider's invoice and pay for it in churn. The math never works out.
Every week without a structured SLA, you accumulate customer service debt that hasn't yet shown up in your numbers.
