AI Agents in Customer Support: Where It Breaks
Most tickets are the same forty questions.
The loop, as it actually runs
- Ticket arrives
- categorised
- routed
- answered
- resolved
- tagged and closed
Where it breaks
Not in the steps. In the joins between them:
- Repeat questions consume the queue
- Routing is done by whoever reads it first
- Context is lost on escalation
- Tagging is skipped so reporting is useless
What that actually costs
A support queue where repeat questions consume most of the capacity has a specific pathology: the hard tickets wait behind the easy ones. The forty questions everyone asks are individually trivial and collectively the reason the genuinely difficult ticket sits for two days. Adding headcount fixes this temporarily and expensively. Removing the repeats fixes it structurally — and it also removes the tagging problem, because tagging is skipped under time pressure and time pressure is what the repeats create.
What we would build first
Answering the repeat questions from your own help documentation goes first. It is the highest volume, the lowest risk, and it is the change that makes everything else in the queue possible. Routing, escalation context and tagging are all worth building, but each of them is an improvement to how you handle tickets, while this one reduces how many you handle. Reduce the volume before optimising the handling.
It runs inside Zendesk, Slack, Shopify, Stripe, Gmail — the tools already in use.
How this one goes wrong
The failure mode is a confident answer drawn from a help article that was accurate two releases ago. A human hesitates because they remember the change; an agent has no memory of what used to be true, only what is written. It answers cleanly, the customer acts on it, and support has created the ticket it will handle next week. The guards are grounding in documents that carry visible last-reviewed dates, an explicit path for the agent to say it does not know, and exclusion of stale documents from grounding rather than trusting them because they exist.
The individual jobs inside this loop — what starts each one and where it has to hand back to a person — are covered under sales & CRM.
Where it lands hardest: insurance brokerages, freight brokerage & 3PL, HVAC & home services, property management and managed service providers. Each of those pages carries the sector’s own economics — the three roles that absorb the work, and the season that decides when a build can start.
In most companies this work sits with customer service reps, order clerks, receptionists and claims processors. Each of those pages carries the wage arithmetic for that role, and says plainly where the numbers do not justify the spend.