Chatbots That Don’t Annoy Users

Users don’t hate chatbots. They hate bots that stall, hallucinate policy, or trap them in loops while a human is three clicks away. The fix is product design, not a warmer system prompt.

Intent map first

List the top intents from real tickets or call logs. For each intent, decide: automate, assist a human, or refuse. If you can’t classify 70% of volume into clear intents, you’re not ready for a bot - you’re ready for better FAQs and search.

1. 01Automate: status checks, password resets, hours, shipping tracking
2. 02Assist: draft replies for agents, retrieve policy snippets
3. 03Refuse + hand off: billing disputes, legal, medical, anything high-stakes

“A good bot knows when to shut up and get a human.”

Handoff is a feature

1. 01

   Detect stuck states

   Two failed clarifications, repeated “that’s not what I meant,” or any safety intent → escalate.

2. 02

   Pass context

   Transcript, user ID, and attempted intent must land with the agent - not a blank ticket.

3. 03

   Set expectations

   Tell the user who is next and when - “Connecting you to support” beats fake typing forever.

Knowledge that doesn’t rot

Retrieval only works if the source of truth is owned. Pick a small set of canonical docs. Version them. Block the bot from answering outside that set. Hallucinated policy is worse than “I don’t know - here’s a human.”