The core paradox

The numbers tell a common story.

We met every SLA we set,  yet nearly 1 in 12 customers still left dissatisfied. The grit to say "these should both be 100%" is understandable, but it reveals something important: SLAs and CSAT measure different things.

SLAs measure your promises to yourself. CSAT measures the customer's experience of reality.

For payment support teams, this matters more than it might in other industries. When a merchant's terminal goes down or a certification test fails unexpectedly, the stakes are higher than a delayed email response.

Payment support quality measurement has to account for the urgency customers feel, not just the speed at which tickets are closed.

Is this an anomaly? What does the industry say?

Not at all. In fact, a 100% SLA alongside sub-100% CSAT is the industry norm, not the exception. The reason is structural.

SLAs are compliance metrics used to measure whether your team responded within a defined window. CSAT is an outcome metric that measures whether the customer is sure that their problem was resolved well.

These outcomes can change for several reasons, even when SLAs are completely met:

• A ticket closed in 45 minutes with a partial fix is still just a 1-hour SLA.
• A customer who waited until Monday morning for an issue raised on Friday night may feel delayed even if your clock only started on Monday.

Across B2B support benchmarks, a CSAT score of 85-95% is generally considered excellent. At 92%, we were performing well. The gap is not a signal that something is broken. It is a signal that our SLA definition and our customer expectations are not perfectly aligned.

The Friday night problem, and why it's central here

Our 18/5 SLA is good for a contract, but it creates a time gap for customers. A customer who raises an issue at 8 PM on Friday experiences 60 hours of an unresolved issue before our SLA starts on Monday morning. Our SLA says "resolved in 1 hour," but their lived experience says "waited all weekend."

CSAT vs SLA payments are not just a metrics debate. It reflects a mismatch between how a support team measures its own performance and how a customer experiences the same interaction. In payment services, where a bug or downtime has a direct financial impact on the merchant.

It is likely responsible for a significant share of our 8% CSAT gap. It's not that we failed our SLAs. It's that the SLA itself doesn't capture what the customer experienced.

Are our SLAs wrongly defined?

Not wrongly defined, but incompletely defined. There are two distinct problems.

Problem 1: SLAs measure speed, not resolution quality. A ticket can be closed within the SLA window with a workaround, a partial fix, or even a "we'll look into this" response. The customer can still rate their experience on whether their problem was genuinely solved. Payment support SLA metrics that only track response time will show strong performance while masking resolution quality issues that affect CSAT.

Problem 2: The SLA clock does not reflect customers' perception of time. Customers do not experience business hours. They experience wall-clock time. Our 18/5 schedule is a legitimate business constraint, but it creates invisible wait time that no SLA currently accounts for.

How to realign SLAs and CSAT

We brainstormed and decided to implement the following levers in phases:

1. Add a CSAT threshold to our SLA definition. Instead of "resolved within 1 hour," we'd redefine it as "resolved within 1 hour and a customer satisfaction rating of 4 stars or above." It makes the SLA a true quality measure, not just a speed measure. Composite SLAs like this are a more honest reflection of payment support quality because they tie the contractual commitment directly to customer outcomes.
2. Segment CSAT by timing of the issue. With 48 tickets, we can identify which were requested on Friday nights and which were requested on weekdays. If Friday night support tickets have lower CSAT, it would confirm the perception gaps theory and be the next action item.
3. Track first contact resolution alongside CSAT. We currently do not measure first-contact resolution as standard practice, and we have decided to add it as a metric. FCR measures whether the issue was resolved in a single interaction, without follow-up. Low FCR tends to drag down CSAT even when the SLA is met. If tickets are being closed and reopened, that pattern will surface here. For payment teams specifically, repeat contacts on the same issue are a reliable signal that the resolution was incomplete the first time.
4. Review payment team performance KPIs beyond speed. Response time is the most visible KPI but not the most important one for customer satisfaction. Resolution completeness, escalation rate, and reopen rate are payment team performance KPIs that give a fuller picture of whether the support function is actually solving problems or just closing tickets within the window.

Here is the takeaway

The 8% CSAT gap is not a red flag but a diagnostic signal. Together, a 100% SLA and 92% CSAT indicate that the team is operationally disciplined. But it also indicates that the SLA definition does not yet fully capture the customer experience, meaning it doesn't cover off-hours submissions.

SLA compliance in payment services is a necessary baseline. But baseline compliance and genuine customer satisfaction are not the same thing.

The teams that close this gap are the ones that treat CSAT as having the same weight as SLA, not as a secondary metric reviewed quarterly.

The most important single action is to identify which tickets drove the 4-star ratings that pulled us down from 100%, and to see whether they share a pattern in timing, issue type, or resolution completeness. That analysis has already been completed for the 48 tickets we reviewed, but it is written as a forward-looking action item for us to execute consistently.

That analysis will tell us exactly which lever to pull first. And pulling the right lever, rather than all of it at once, is what turns a diagnostic signal into a measurable improvement.