Why chatbots annoy your customers — and what works instead

Chatbots have earned their reputation. The circular menu trees, the "I didn't quite get that," the FAQ regurgitated at a customer whose parcel is genuinely lost — all real, all infuriating. So when store owners tell us "our customers would hate a bot," they're right about the bots they've met. They're wrong about what's now possible, and the difference is one word: resolution.

Deflection vs resolution

Classic chatbots were built to deflect — keep the customer away from your (expensive) humans by pointing at help articles. Customers feel this instantly, because it's true: the bot's goal was never solving their problem.

A resolution workflow is a different animal. When a customer asks "where's my order?", it doesn't link the shipping FAQ — it looks up their actual order, reads the live carrier status, and answers: "Your parcel left our warehouse Tuesday and is out for delivery today." When they request a return, it checks the policy and issues the label. It acts on real data with real system access, which is exactly what the human agent would have done — in one minute instead of one day.

The three rules that keep it likeable

• Answer from data, never from scripts. If the workflow can't access the system that holds the answer, don't deploy it there.
• Escalate fast and visibly. Emotion, edge cases and anything off-script go to a human immediately — with full context so the customer never repeats themselves. The handoff is where trust is won or lost.
• Never pretend to be human. Customers forgive a capable assistant; they don't forgive being tricked. Speed and competence build more trust than a fake first name.

Where to start

Order status and returns for stores, inbox triage for everyone else — the queries with clean data behind them. Get resolution right there, and "our customers would hate a bot" becomes "why didn't we do this a year ago." See the e-commerce workflows.