Containment rate and first call resolution (FCR) are the two numbers most teams use to judge whether their phone channel is working. They measure different things, and pushing one without watching the other can hurt customers. This guide gives you the formulas, shows how the two metrics interact, and lists practical ways to improve both.
What is IVR containment rate?
IVR containment rate is the percentage of calls that are handled entirely within the IVR, without a transfer to a live agent. The formula is:
Containment rate = (calls that end in the IVR without an agent transfer ÷ total calls that enter the IVR) × 100
For example, if 1,000 callers enter your payment IVR and 180 transfer to an agent, the containment rate is (820 ÷ 1,000) × 100 = 82%.
The catch is in the numerator. Basic containment counts every call that did not reach an agent, including callers who hung up in frustration. A more honest version counts only calls that finished the task.
Successful containment rate = (calls that complete their task in the IVR ÷ total calls that enter the IVR) × 100
If 70 of those 820 contained callers hung up before paying, successful containment is (750 ÷ 1,000) × 100 = 75%. Report both, and be clear which one you mean.
What is first call resolution?
First call resolution (FCR) is the percentage of customer issues that are fully resolved on the first contact, with no need for the customer to call back or reach out again. It is also called first contact resolution. The formula is:
FCR = (issues resolved on the first contact ÷ total issues with a first contact) × 100
The hard part is deciding what "resolved" means. Teams usually use one or more of these methods:
- Repeat-contact window: a call counts as resolved if the same customer does not contact you again about the same issue within a set period. Pick a window, such as 7 days, and keep it fixed so trends are comparable.
- Customer survey: ask callers right after the call whether their issue was resolved.
- Agent or system disposition: the agent or IVR records the outcome. This is the easiest to collect and the easiest to inflate, so check it against repeat contacts.
FCR applies to the whole journey, IVR and agents together. A call that the IVR routes to the wrong team, which then transfers it again, can still be resolved on that first call, but the caller's experience is worse than the FCR number suggests, so track transfers too.
How are containment rate and FCR related?
Containment and FCR usually rise together when the IVR resolves tasks well, and move apart when the IVR keeps callers without helping them. A caller who hangs up inside the IVR and calls back tomorrow raises containment and lowers FCR at the same time.
That is why the two should always be read side by side:
| Containment | FCR | What it usually means |
|---|---|---|
| High | High | The IVR resolves the tasks it handles and routes the rest well |
| High | Low | Callers are stuck, hanging up and calling back |
| Low | High | Agents resolve issues, but the IVR is not taking routine work off them |
| Low | Low | Routing and self-service both need work |
When is a high containment rate a bad sign?
High containment is a bad sign when it comes from callers who cannot get out rather than callers who got what they needed. Watch for these warning signs:
- The agent option is hidden, or pressing 0 is ignored
- Callers loop back to the same menu more than once
- Short timeouts end calls before callers find their account number
- A large share of "contained" calls end in a hang-up mid-task
- Repeat calls from the same numbers climb after an IVR change
The goal is not to keep every caller in the IVR. Some calls, such as complaints, complex claims and vulnerable customers, should reach a person quickly. A good containment target depends on your call mix, so set it per task, not for the whole IVR.
Which IVR metrics should you track?
Track a small set of metrics that together show whether callers are being helped. This table gives a starting point.
| Metric | Formula | What it tells you |
|---|---|---|
| Containment rate | Calls ending in IVR without transfer ÷ calls entering IVR | How much work the IVR keeps from agents |
| Successful containment | Calls completing their task in IVR ÷ calls entering IVR | How much work the IVR actually finishes |
| Transfer rate | Calls transferred to an agent ÷ calls entering IVR | Where automation hands off |
| IVR abandonment | Calls hanging up mid-task ÷ calls entering IVR | Friction and confusion |
| Repeat call rate | Callers calling again within your window ÷ unique callers | Unresolved issues |
| First call resolution | Issues resolved on first contact ÷ issues with a first contact | Whether customers got an answer |
| Task success rate | Calls reaching a success step ÷ calls starting the task | How well a specific flow, such as payments, works |
| Loops per call | Times callers re-enter the same step ÷ calls | Confusing menus or prompts |
How to measure containment and FCR, step by step
- Mark a success step in every task. Add a point in the flow that callers reach only when the task is done, such as "payment approved." This makes successful containment and task success measurable.
- Tag every exit. Record whether each call ended in success, transfer (with the reason), hang-up, or error.
- Link IVR data to agent and CRM data. Use the caller's number or account to see whether a contained call led to a repeat contact.
- Ask the customer. A short post-call survey on whether the issue was resolved checks your system-based numbers. See collect customer feedback.
- Review weekly, by task. Averages across the whole IVR hide the one flow that is failing.
How do you improve containment without trapping callers?
Improve containment by fixing the steps where callers drop out, not by making it harder to leave. Start with these changes:
- Fix the biggest drop-off first. Use call path reports to find the step where most callers hang up or transfer, then listen to those calls.
- Match your paperwork. If the bill says "account number," the IVR should say the same, and the number should be easy to find on the page.
- Give callers time. Lengthen timeouts on steps where callers look up information, and repeat where to find it.
- Personalize. Use caller ID to skip identification or suggest the likely task.
- Offer other channels for hard inputs. Send an SMS to collect an email address or send a confirmation.
- Keep the agent option visible. Hiding it raises containment on paper and lowers FCR in practice.
For prompt-level fixes, see IVR call flow design best practices.
How do you improve first call resolution?
Improve FCR by getting callers to the right place the first time and giving whoever handles the call the full picture. In practice:
- Route by intent. Ask callers what they need in their own words or use clear menus, so fewer calls land with the wrong team. See conversational IVR.
- Pass context on transfer. Send the caller's verified identity and intent to the agent's screen so nobody repeats themselves.
- Close the loop automatically. Send confirmations and status updates by text or call, which prevents "did it go through?" calls. See outbound messaging and notifications.
- Study repeat calls. Group repeat contacts by reason; each group points to a broken process, a confusing prompt or a policy gap.
- Give agents the tools to finish. If an agent cannot complete the fix during the call, the customer will call back.
How Plum Voice handles this
Plum VoiceTrends gives teams the data behind these metrics. Its Diagnostic Flow maps the most common call paths and shows where callers transfer out or hang up, and the Event Tracker reports loops per call. Teams can measure task success by adding a step that callers reach only after a successful payment and reading its traffic in the call path view. Plum Insight adds post-call surveys to confirm resolution from the customer's side, and Plum reports that Plum Fuse customers improve CSAT with an average of 80% first call resolution.