Every support-tooling vendor now claims AI agent capability. Almost none of them agree on what the agent is actually allowed to decide on its own. This is the breakdown we give clients before scoping a support-agent build.
§ 01What an AI agent means in a support context
A support agent that reads a ticket, checks it against order or account data, and takes an action, replies, refunds, escalates, updates a record, without a human writing that response first. This is different from AI-assisted support, where a human agent gets a drafted reply to review and send. Most vendor demos show the second thing and sell it as the first.
§ 02Where agents handle tickets end-to-end today
- Order status, shipping, and tracking questions, high volume, low ambiguity, low stakes if occasionally wrong.
- Password resets, account access issues, and other deterministic account actions.
- FAQ-style questions with a clear, policy-backed answer.
- Standard, in-policy refunds and returns within a defined value ceiling.
§ 03Where agents draft, and a human decides
- Any complaint involving dissatisfaction with the product or service itself, not just a process question.
- Refunds or credits outside standard policy bounds.
- Anything where the customer references multiple issues, orders, or a prior unresolved case.
- Retention conversations, a customer signaling they might cancel or leave.
§ 04Where agents should not operate unsupervised
- Legal, medical, or safety-related claims made by the customer.
- Anything involving a payment dispute or chargeback.
- Escalations that already involve a human agent or manager by name.
- Any ticket where the agent's own confidence in classification is low, route these to a human by default, not as an edge case.
§ 05What this actually costs
Scoped narrowly, one or two ticket categories, integrated with your existing helpdesk and order system, realistic build costs run in the same range as other single-purpose production agents: several thousand dollars for the integration and eval work, plus ongoing model and monitoring costs that scale with ticket volume. Vendors selling full inbox automation out of the box are usually selling the draft-and-review version, not full autonomy, regardless of how the demo looks.
§ 06The decision rule
If a wrong answer costs you a refund you'd have approved anyway, let the agent act. If a wrong answer costs you a customer's trust, a legal exposure, or a number you can't easily reverse, keep a human in the loop, draft-and-review, not full autonomy, until your eval data proves the agent's error rate on that category is low enough to change that.
──
Evaluating a support-agent build? A 30 minute discovery call will tell you if it's viable, and which ticket categories to start with. See the full engagement models and prices on our Hire page.