Automation Teardown #5, e-commerce edition: most of the support inbox is the same five questions, and someone still answers each of them by hand.
The manual reality
Where's my order? Can I change my shipping address? How do returns work? Is this back in stock? Why didn't my discount code apply? For every ticket, someone opens the helpdesk, the store admin, and the carrier's tracking page, then writes a reply that's mostly the same as the last one. It isn't hard work. There's just a lot of it, and it grows with every sale.
What the agent does
- Classify. A new ticket gets labeled by type (order status, address change, return, stock, discount) along with a confidence score.
- Look it up. For routine types, the agent pulls the actual order: fulfillment status, tracking, purchase date, and whether it's inside the return window. The reply is built from those facts and your written policies, not from what a model guesses your policy is.
- Draft or send. At first, every reply waits in a review queue. Once the team has seen enough drafts to trust a ticket type, high-confidence replies for that type go out directly.
- Flag the rest. Anything that isn't routine goes to a person with the order context already attached: damaged items, chargebacks, an upset customer, a request outside policy, or a low-confidence classification.
What stays human
Refunds, exceptions, and anything that costs money are a person's call. The agent never offers a discount, waives a fee, or bends a policy to close a ticket. The team decides which ticket types can send without review, and can take any type back at any time. When the agent isn't sure, it says so and stops.
Honest sizing
If routine questions are half the inbox, and for most stores they are, this usually saves several hours a week and cuts first response from hours to minutes. It's typically live in a week or two on a standard helpdesk and store platform. Seasonal stores get the most out of it, because the volume spikes and the team doesn't.
We run free 20-minute teardowns of workflows like this. Start at /discuss or write to hello@fullspecstudio.com.