Chatbot Escalation Failure

Note: This pattern currently has evidence from only 1 ticket. The minimum for a pattern page is 3 tickets. This page is provisional and should be validated or removed as more tickets are ingested.

Pattern Description

The Zendesk web chatbot ("Zack") fails to escalate to a human agent when a customer explicitly requests one. Instead, the bot repeats generic FAQ links and eventually redirects the customer to submit a support ticket — which increases frustration rather than resolving the interaction.

Evidence

• Ticket #41863 — Customer said "trying to buy compute but nobody is answering" and "no I want to speak to an agent." Bot responded with Sales FAQ links twice, then offered a support ticket submission link. No human ever engaged. The ticket was closed with 0 human agent replies.

Impact

• Lost sales — Customer was trying to purchase compute hardware. The bot's failure to route them to sales likely resulted in a lost opportunity.
• Customer frustration — Customer explicitly expressed frustration and was not de-escalated.
• Brand damage — An interaction where a ready-to-buy customer can't reach a human reflects poorly on the company.

Recommendations

1. Implement escalation triggers — when a customer says "speak to an agent," "talk to a person," or similar phrases, the bot should immediately offer a live transfer or callback
2. Distinguish sales from support — sales-intent visitors should be routed to sales channels, not redirected to submit a support ticket
3. Capture lead information — if no agent is available, the bot should capture contact info and promise a callback within a specific timeframe
4. Limit FAQ repetition — don't show the same FAQ link twice in one conversation

Referenced by

No incoming references yet.