Resolution Rate vs. CSAT: Why One Metric Lies to You
Your resolution rate is 72%—up from last quarter. Your CSAT is 4.2 out of 5, down by 0.3 points. Congratulations: you’ve just solved nothing.
These metrics don’t contradict each other. They measure entirely different things. Resolution rate tracks whether an agent closed a ticket. CSAT tracks whether the customer felt resolved. One is a process efficiency stat; the other is a gut-check on experience. Push too hard on one, and you’ll break the other.
We’ve watched teams optimize for resolution rate by forcing agents to mark tickets closed—even when the customer’s problem wasn’t fixed. Others chase CSAT by letting agents spend 20 minutes on every call, killing productivity. Neither approach works. Here’s how to stop the trade-off.
Resolution Rate: The Metric That Lies
Resolution rate (or first-call resolution, FCR) is the percentage of interactions resolved in a single contact. It’s a favorite of operations teams because it’s easy to measure and directly tied to cost savings. A 1% improvement in resolution rate can cut average handle time (AHT) by 3–5%, depending on your industry [Forrester]. That’s real money.
But resolution rate is a process metric, not a quality metric. It tells you whether an agent followed the script or closed the ticket, not whether the customer’s problem was actually solved. We’ve seen BPOs where agents mark tickets as “resolved” after a 90-second call—only to have the customer call back within hours with the same issue. The resolution rate? 98%. The CSAT? 2.8.
Here’s the dirty secret: resolution rate is a leading indicator of efficiency, not effectiveness. It’s a tool for reducing costs, not improving customer experience.
How Resolution Rate Gets Gamed
- Ticket closure without resolution: Agents mark tickets closed to hit targets, even if the customer’s issue isn’t fixed. Example: A bank call center where agents “resolved” fraud alerts by reading a script—only for customers to call back when their cards were still blocked.
- Over-assignment: Complex issues get split into multiple tickets (e.g., “Account issue” + “Billing dispute” + “Technical support”) to inflate resolution rates on simple interactions.
- Script compliance as success: Following a script counts as “resolved,” even if the customer’s specific problem isn’t addressed. Example: A telecom support agent closing a ticket after reciting a line about “escalating to Tier 2” without actually escalating.
- CSAT surveys sent only to ‘resolved’ calls: If you only survey customers after a ticket is closed, you’re only hearing from the happy few. The rest? Silent frustration.
CSAT: The Metric That Hides Costs
Customer satisfaction (CSAT) is the gut-check metric. It asks, “Did we make this person’s life better?” A typical CSAT survey might look like:
“How satisfied were you with the service you received today?”
1 (Very dissatisfied) – 5 (Very satisfied)
CSAT is sticky. A 0.5-point drop in CSAT can correlate with a 5–10% increase in churn, depending on your industry [Gartner]. But CSAT is expensive to move. Improving it by 1 point often requires retraining agents, overhauling scripts, or adding headcount—all of which eat into your resolution rate gains.
The problem? CSAT is a lagging indicator. By the time you see a dip, the damage is done. And because it’s subjective, it’s easy to manipulate—either by cherry-picking survey samples or by training agents to “fake” enthusiasm.
How CSAT Gets Gamed
- Survey timing: Sending CSAT surveys immediately after a call captures frustration, not resolution. Wait 24–48 hours, and you’ll hear from customers who’ve had time to cool down—or whose issues were resolved by a follow-up.
- Agent coaching on ‘tone’: Teams that drill agents on “sounding happy” without addressing the root issue will see high CSAT but low resolution rates. Example: A support agent saying, “I’m so sorry for the inconvenience!” while doing nothing to fix the problem.
- Selective surveying: Only surveying high-value customers or those with simple issues skews results upward. We’ve seen call centers where agents were told to “transfer the angry ones” before the CSAT survey was sent.
- Ignoring the ‘why’: CSAT scores alone don’t tell you what to fix. A low score could mean slow response times, unhelpful agents, or a broken product. Without digging into the comments, you’re flying blind.
The Trade-Off That Doesn’t Have to Exist
Most contact centers treat resolution rate and CSAT as a zero-sum game. Push one up, and the other goes down. But the best-performing teams we’ve worked with break the trade-off by:
- Measuring resolution quality, not just quantity. Instead of tracking “tickets closed,” track “issues actually resolved.” Use a post-call review where agents and supervisors flag cases where the customer’s problem wasn’t fixed—even if the ticket was closed.
- Aligning CSAT with real outcomes. Stop asking, “Were you satisfied?” and start asking, “Was your problem fixed?” Example: A telecom company we worked with switched to a CSAT question tied to resolution: “Did your service issue get resolved today?” The result? A 12% drop in repeat calls without hurting CSAT.
- Using real-time coaching, not lagging reports. If an agent’s CSAT comments reveal they’re not handling complaints well, coach them before the next survey goes out. Tools like Teamcorr’s real-time QA dashboards let supervisors spot patterns in live calls and intervene immediately.
- Accepting that some issues can’t be resolved in one call. Not every problem should be solved in 3 minutes. For complex issues, set clear expectations: “We’ll resolve this by end of day” or “Here’s what we can’t fix, and here’s our workaround.” Transparency kills frustration.
The One Metric You’re Probably Ignoring
Most contact centers track resolution rate and CSAT—but few track resolution rate by CSAT score. This is the metric that tells you whether your agents are actually fixing problems, not just closing tickets.
| CSAT Score | Resolution Rate | What It Means |
|---|
| 4.5+ | 80%+ | Strong performance. Agents are resolving issues well and customers are happy. |
| 4.0–4.4 | 70–79% | Average. Room for improvement in either resolution or customer experience. |
| 3.5–3.9 | 60–69% | Warning sign. Either agents aren’t resolving issues, or customers feel ignored. |
| 3.0–3.4 | 50–59% | Crisis mode. High repeat calls and low satisfaction. |
| <3.0 | <50% | Failure. Agents are likely gaming the system or the process is broken. |
If your resolution rate is high but your CSAT is low in the same segments, you’ve got a problem. It’s not a trade-off—it’s a failure to deliver.
How to Fix It: Three Concrete Steps
1. Stop Using Resolution Rate as a KPI (Use It as a Leading Indicator)
Resolution rate should inform your operations, not define them. If your resolution rate is 90% but your CSAT is 3.5, you’re doing something wrong. Instead:
- Track repeat call rate by issue type. If “billing disputes” have a 40% repeat rate, dig into why.
- Set minimum resolution thresholds by complexity. A simple password reset should be resolved in one call. A technical support issue might need two.
- Use resolution rate to identify training gaps, not to punish agents. If a team’s resolution rate drops after a script update, it’s a process issue, not a performance issue.
2. Make CSAT Actionable (Not Just a Report)
CSAT surveys are useless if they don’t lead to change. Here’s how to make them matter:
- Tag surveys by agent, issue type, and outcome. If Agent X has a 3.0 CSAT on “refund requests” but a 4.5 on “account updates,” they know exactly where to improve.
- Loop survey comments back to agents. Use tools like Teamcorr’s real-time floor dashboards to surface common complaints in live coaching sessions.
- Tie CSAT to agent incentives—but carefully. Avoid bonuses for high CSAT alone. Instead, reward improvements in CSAT by issue type (e.g., “Increase refund request CSAT by 0.5 points this quarter”).
3. Build a Process That Values Both
The best contact centers we’ve seen treat resolution rate and CSAT as two sides of the same coin—not competing metrics. Here’s how:
- Define “resolved” by customer outcome, not agent action. Example: A “resolved” fraud alert isn’t just reading a script—it’s confirming the customer’s card is unblocked and they can use it.
- Use post-call reviews to reconcile the two. After every call, ask: “Did we resolve the issue?” and “Would the customer say they were satisfied?” If the answers don’t match, investigate why.
- Invest in the right tools. A CRM like Teamcorr that tracks AHT by issue type, flags repeat calls, and surfaces CSAT trends in real time lets you spot problems before they become crises.
The Bottom Line
Resolution rate and CSAT aren’t enemies. They’re two different ways of asking the same question: Are we delivering value? One tells you whether you’re efficient. The other tells you whether you’re effective. Ignore one, and you’ll optimize for the wrong thing.
Here’s the playbook:
- Stop gaming either metric. If your resolution rate is high but your CSAT is low, you’re lying to yourself.
- Use resolution rate to spot inefficiencies, not to punish agents.
- Use CSAT to identify where your process fails customers.
- Invest in tools and training that let you improve both without trading one off against the other.
Most contact centers spend 80% of their time optimizing for resolution rate and 20% on CSAT—or vice versa. The teams that win? They spend 50% on each. And they stop treating them as a trade-off.
Questions people ask
How do you calculate first-call resolution rate accurately?
First-call resolution (FCR) is calculated as: (Number of calls resolved in first contact / Total calls) × 100. However, accuracy depends on defining what ‘resolved’ means. If agents mark tickets closed without fixing the issue, your FCR will be inflated. Use post-call reviews to verify whether the customer’s problem was actually solved.
What’s the ideal balance between resolution rate and CSAT?
There’s no single ‘ideal’ balance—it depends on your industry. For high-volume, low-complexity issues (e.g., password resets), aim for 80%+ resolution rate with CSAT above 4.5. For complex issues (e.g., technical support), accept lower resolution rates (60–70%) if CSAT remains high (4.0+). The key is tracking both metrics by issue type.
How do you prevent agents from gaming resolution rate?
Agents game resolution rate by closing tickets without resolving issues. To prevent this, implement post-call reviews where supervisors verify whether the customer’s problem was fixed. Also, track repeat calls by issue type—if a high percentage of ‘resolved’ tickets reopen, your agents are likely gaming the system.
Why does CSAT drop when we push agents to improve resolution rate?
CSAT often drops when you push resolution rate because agents rush calls to meet targets, leaving customers unsatisfied. The fix? Set realistic resolution expectations by issue complexity. For example, a billing dispute might require two calls, while a password reset should be resolved in one. Train agents to manage expectations with customers.
What’s the biggest mistake contact centers make with CSAT surveys?
The biggest mistake is sending CSAT surveys immediately after a call, which captures frustration—not resolution. Wait 24–48 hours, and you’ll hear from customers who’ve had time to assess whether their issue was fixed. Also, avoid leading questions like ‘How satisfied were you?’ Instead, ask, ‘Was your problem resolved today?’
How do you improve CSAT without increasing AHT?
Improving CSAT without increasing AHT requires focusing on <em>quality</em>, not quantity. Train agents to listen actively, set clear expectations, and follow up if an issue isn’t resolved in the first call. Use tools like real-time coaching to address common complaints before they escalate. Small improvements in resolution quality (e.g., fixing the issue on the first call) can boost CSAT without adding time.