Before you ask for more headcount, pull last week's repeat contacts.
In most centers over 40 seats, a stubborn share of “new” volume is the same customer, with the same problem, on their second or third try.
That is not demand. That is unfinished work coming back through the front door — and you pay for it twice: once in handle time, and again in the customer's patience.
Repeat contacts hide in plain sight. Your telephony counts calls. Your CRM counts tickets. Almost nobody counts problems. So a customer who calls Monday about a missing refund, emails Wednesday, and chats Friday shows up as three contacts, three “resolutions,” and one person who will never trust your first answer again.
The usual fix makes it worse. Leaders push first-contact resolution, and agents learn the fastest way to hit the number is to close the conversation, not the problem. The ticket closes. The refund still has not landed. The customer calls back angrier — and the second agent starts from zero, because the first one's notes say “customer advised.”
Start by measuring the right thing. Pick one contact reason — billing is a good place to start — and link every contact from the same customer on the same issue within 14 days. That linked rate is your real workload number. In center after center it runs far higher than leaders expect, and it concentrates: a handful of broken handoffs and unclear promises generate most of the repeats.
Then fix causes, not agents. Most repeats trace to three failures: a promise with no owner (“someone will call you back”), a fix the customer cannot verify (“it's sorted” — with no confirmation they can check), and a handoff that drops the thread, where the notes record what the agent did, not what the customer still needs.
Each has a boring fix. Every promise gets a named owner and a date. Every resolution gets a customer-visible confirmation. Every handoff opens with what is still unresolved — one line, at the top.
This is the gap we built Pipeline Intelligence to close: one shared record of the problem, the promise, and the owner, so the second contact — if it happens at all — continues the story instead of restarting it.
Do the math before your next staffing request. If a fifth of your volume is customers asking, again, for something you already said was done, you do not have a capacity problem.
You have a completion problem. Hire for that later. Fix it first.
