
CX Measurement
Part of Omnichannel customer experience
Measuring whether channel switching solved the problem
Define the customer outcome, link contacts carefully and interpret resolution, repeat contact and missing data after a channel switch.
Measure a channel switch against the customer’s original goal and the result after the switch. A transfer can succeed yet end in a wrong answer, another contact or an unresolved case. Define the outcome first, then connect the parts of the task your records can reliably link.
Define the task and its end point
Pick one case type, such as changing a delivery address after an online attempt. For that request, success means the change takes effect where needed and the customer receives an accurate confirmation. Submission, agent closure and confirmation are separate events. Name the event your measure uses.
Choose an observation window that fits the task before examining results. A simple question may be settled immediately; a request involving later fulfilment needs a later check. Report cases still open at the end of the window separately. An outcome that cannot be determined is unknown, not a success.
Count the switch and the outcome separately
For a defined period, count eligible task starts, cases that moved channels and switched cases with a verified outcome. Use a case reference or another approved method to link contacts.
Check for duplicates, shared accounts and unrelated new issues. Report contacts that cannot be linked. No recorded repeat contact does not prove resolution.
| Measure | Working definition | Limit |
|---|---|---|
| Switch rate | Eligible tasks that moved channel ÷ eligible task starts | Does not show whether switching helped |
| Confirmed resolution after switch | Switched cases with a confirmed successful outcome ÷ all switched cases in the cohort | Unknown outcomes lower the reported share; show them separately |
| Outcome coverage | Switched cases with an assessable outcome ÷ all switched cases in the cohort | High coverage does not establish accuracy |
| Repeat contact | Cases with another contact about the same issue within the chosen window | Repeat contact does not always mean the first answer was wrong |
| Customer-reported result | Respondents saying the original goal was achieved ÷ respondents asked that question | Non-respondents may have different outcomes |
State the window, exclusions and linking method beside any reported figure. Keep unresolved, unlinked and other unknown outcomes visible; do not remove them quietly from the main denominator.
Measuring Success After Channel Switch: Key Metrics and Definitions
- Switch rateEligible tasks that moved channel ÷ eligible task starts
- Confirmed resolution after switchSwitched cases with a confirmed successful outcome ÷ all switched cases in the cohort
- Outcome coverageSwitched cases with an assessable outcome ÷ all switched cases in the cohort
- Repeat contactCases with another contact about the same issue within the chosen window
- Customer-reported resultRespondents saying the original goal was achieved ÷ respondents asked that question
Key Performance Indicators for Channel Switch Evaluation
- Switch rate
- Measured as a percentage of eligible task starts
- Confirmed resolution after switch
- Percentage of switched cases with verified success
- Outcome coverage
- Proportion of switched cases with assessable outcomes
- Unknown outcomes
- Cases still open or unlinked at end of observation window
Investigate the result
Read cases with successful, unsuccessful and unknown outcomes. A customer may have switched because the digital route failed, because a specialist decision was needed or because they preferred a conversation. Separate those reasons.
Review whether the receiving person had enough context and whether the answer agreed with the original channel. A falling switch rate could mean the digital route improved or that help became harder to find.
Ask about the result after the customer could reasonably see it. “Was your address changed for this order?” is more useful here than a general satisfaction question immediately after a call.
Invite comments about unexpected problems. Seek feedback from people who abandoned the digital route or never completed the switch; otherwise the sample mainly reflects those who reached support.
Make a bounded decision
Report results by task and, where data permits, by channel pair and case complexity. Show volumes and unknown outcomes.
If cases resolve but customers repeat their story, improve context transfer. If the transfer completes but the underlying action fails, investigate the receiving process.
Apply the same definitions after a change. An association between switching and resolution does not show that switching caused the result.
Steps to Measure Whether a Channel Switch Resolved the Issue
- Define the task and its endpointSpecify what success looks like (e.g., address change confirmed, delivery updated)
- Set an observation windowAllow time for fulfilment; report unresolved cases separately
- Link contacts using case referencesEnsure accurate tracking across channels; flag unlinked or duplicate cases
- Measure key metricsTrack switch rate, confirmed resolution, repeat contact, and customer-reported results
- Investigate root causesReview why customers switched; check context transfer and process alignment
- Report transparentlyShow volumes, unknowns, and data limitations; avoid hiding unresolved cases



