Call Center OutsourcedPowered by StealthAgents

Call Center Outsourced evidence brief · Desk review · Published

How should a contact center measure the cost of a misrouted contact?

A method for costing a misrouted contact: trace the transfer chain, count the repeat contact, add the agent time and customer wait, and test one routing fix.

How should a contact center measure the cost of a misrouted contact? editorial illustration
On this page
  1. Key stats
  2. Key takeaways
  3. Question and scope
  4. What the evidence supports
  5. Define a misrouted contact
  6. Start from the customer's stated need
  7. Count the transfer chain
  8. Separate a wrong queue from a wrong answer
  9. Measure the repeat contact that follows
  10. Add the agent time and the customer wait
  11. Avoid counting the same contact twice
  12. Check the routing data for a clock error
  13. Compare the cost across call types
  14. Set a threshold for a routing fix
  15. Test one route before changing the menu
  16. Read the cases that were fixed manually
  17. Report the cost beside the volume
  18. Use the finding in the client review
  19. Recheck after the route changes
  20. Limits of the evidence
  21. Manager review questions
  22. Conclusion
  23. Put this into a support lane
  24. Related operating guides
  25. FAQs
  26. Sources

Key stats

  • 2.67 million U.S. customer service representative jobs in 2025 (BLS)
  • $21.53 median hourly wage in May 2025 (BLS)
  • 289,500 projected annual openings, 2025 to 2035 (BLS)

Key takeaways

  • Anchor the misroute at the customer's first stated need, not the final disposition.
  • Count the transfer chain and the repeat contact, and deduplicate before costing.
  • Keep agent time and customer wait in separate columns with stated rates.
  • Test one route change and compare the cost per contact with the volume.

Question and scope

This brief asks how an outsourced contact center should measure the cost of a contact that reaches the wrong queue or the wrong owner. The population is one queue during a defined period, and the unit is a customer contact with at least one avoidable transfer. The question is what the routing error costs in agent time, customer wait, and repeat work. The analysis covers the measurement method, not the price of a specific contract. Record the routing map and the period before sampling.

What the evidence supports

Contact-center standards call for defined processes and measurable results, and federal data-quality guidance calls for documented sources and stated limitations. Neither source provides a standard cost formula for a misrouted contact. The operating inference is to count the chain of work a misroute creates and value it with the queue's own time and wage data. A cost built from assumptions should show those assumptions. The measure is most useful when it compares one route with another, not when it claims a precise total.

Define a misrouted contact

A misrouted contact is one that reaches a queue or owner that cannot resolve the customer's stated need and must transfer it. The transfer may be to another queue, a supervisor, a client team, or a self-service path. A transfer that is required by the process, such as a fraud handoff, is not a misroute. Write the definition with the approved routing map. The reviewer should be able to tell an avoidable transfer from a required one.

Start from the customer's stated need

Read the first clear statement of the need, not the final disposition. The first statement shows whether the original route matched the request. A customer who says billing and is sent to sales has a misroute even if sales eventually transfers the call. Use the recording or the intake note, and record which source was used. The first statement is the anchor for the whole cost calculation.

Count the transfer chain

For each misrouted contact, list every transfer in order, with the time at each stop and the owner who received it. A chain of three transfers costs more than a single wrong queue, and the longest chain is often the most useful case to study. Separate a warm transfer, where the agent explains the case, from a cold transfer, where the customer repeats the story. The chain is the basis for the time and the customer-wait cost.

Separate a wrong queue from a wrong answer

A contact can reach the right queue and still get a wrong answer, or reach the wrong queue and get the right answer by luck. The two failures have different fixes. Record the queue and the answer accuracy as separate fields. A routing fix will not correct a knowledge problem, and a knowledge fix will not correct a menu problem. The cost measure should keep the categories distinct.

Measure the repeat contact that follows

A misroute often produces a second contact after the customer gives up or is disconnected. Match the contacts by customer and request within a stated window. Count the repeat as part of the misroute only when it concerns the same need. Include the wait before the repeat and the outcome. The second contact is often the largest part of the customer cost and the easiest one to overlook.

Add the agent time and the customer wait

Value the agent time with the queue's loaded hourly cost and the measured minutes spent on the transfer, the repeat explanation, and the rework. Value the customer wait separately, because the customer's time is not the same as the agent's. Do not present the customer wait as a wage figure. Keep the two columns separate so the client can see the operational cost and the service cost. State the source of every rate used.

Avoid counting the same contact twice

A contact that is transferred twice may appear in two queue reports. Deduplicate by the customer and the request before adding the time. Use the case identifier and the phone log together. A cost that double-counts the same minute will overstate the problem and undermine the recommendation. Record the deduplication rule with the sample. The report should show the raw count and the deduplicated count.

Check the routing data for a clock error

The queue system, the phone system, and the client report may use different time zones or intervals. Compare the timestamps at the transfer point before calculating any wait. A clock mismatch can move a contact into the wrong hour and make a route look worse than it is. Use one stated clock and convert the other logs to it. Record the conversion in the method note.

Compare the cost across call types

A misroute on a simple address change costs less than one on a payment dispute, even when the transfer count is the same. Group the cost by call type and by route so the client can see where the money goes. A high total may come from one common route rather than many rare ones. Rank the routes by total cost and by cost per contact. Both views are useful for a decision.

Set a threshold for a routing fix

Decide in advance what level of cost would justify changing a menu or a rule. The threshold should include the cost of the change, the risk of a new route, and the time to test it. A small cost on a high-volume route can still justify a fix. Write the threshold with the client so the review does not become an argument about the size of the problem. Record the decision and the date.

Test one route before changing the menu

Change one prompt or one routing rule and compare the misroute cost for the same call type before and after. Keep the hours, the agent group, and the call mix as similar as possible. A second change in the same period makes the result unreadable. Set the success condition before the test begins. The test should show whether the cost moved, not only whether the menu looked better.

Read the cases that were fixed manually

Some misroutes are caught by a supervisor or an experienced agent before the customer notices. Those cases are a hidden cost and a source of learning. Read a sample and record where the fix happened and how long it took. A manual fix that is invisible in the report will keep the route unchanged. Include the caught cases in the cost estimate and in the training review.

Report the cost beside the volume

A large cost with a small volume may be a serious but rare case, while a small cost with a large volume may be the better fix. Show the volume, the cost per contact, and the total cost together. The client should see which routes are frequent and which are expensive. Avoid a single headline number that hides the distribution. The report should let the reader choose the next test.

Use the finding in the client review

Bring the route, the transfer chain, the repeat contact, and the cost compare. Ask for the one routing change the evidence supports and a date to review it. Do not bundle a staffing request into the same decision unless the cost analysis clearly points to capacity. A routing fix can reduce the workload that looked like a headcount gap. Keep the decision and the test result with the report.

Recheck after the route changes

After the change, measure the same cost fields for a comparable period. A drop in transfers with a rise in repeat contacts may mean the new route is not clear. Check the customer wait and the manual fixes as well as the transfer count. A route that only moves the work is not a fix. Record the result and update the routing map.

Limits of the evidence

This brief cannot produce an exact cost for a specific contract or prove that a routing change caused a particular saving. The rates and the time data are estimates, and the call mix may differ between periods. A comparison can show a direction without a precise total. Use the measure to choose a test and state the uncertainty. The client's finance and operations owners decide how the result is used.

Manager review questions

Managers should ask which route creates the most avoidable transfers, how long the customer waits, and whether the repeat contact was counted once. They should also ask which manual fixes are invisible in the report and what test the cost supports. The remaining question is who owns the routing change. Record the answers with the sample and the rates.

Conclusion

The cost of a misrouted contact is the agent time, the customer wait, and the repeat work that the wrong route creates. Start from the customer's stated need, count the transfer chain, and deduplicate before valuing the time. Compare the cost per contact with the volume and test one route before changing the menu. The measure is useful when it points to a specific fix, not when it produces a single dramatic number. Review the route and the cost again after the change.

Put this into a support lane

Bring the routing map, a month of transfer cases, and the owner who can approve a route test.

Review the routing cost

FAQs

Is the customer's wait a wage cost?

No. Report it as a service cost with its own basis, and keep it separate from the agent's loaded hourly cost.

Should a required transfer count as a misroute?

No. A transfer the approved process requires, such as a fraud handoff, is not an avoidable routing error.

Sources

  1. ISO 18295-1:2017 Customer contact centres
  2. GAO-20-283G: Assessing Data Reliability
  3. Occupational Outlook Handbook: Customer Service Representatives
  4. Fact Sheet #64: Call Centers under the Fair Labor Standards Act