A customer writes on a website at 11:47 p.m. The bot answers the first question. At 11:49, the customer asks for a quote and adds an order number. The conversation then jumps to email, where the support agent asks for the order number again. The customer replies once, waits, and disappears.
The failure was not the greeting. It was the handoff.
KLM was an early, public example of a different approach. The airline used a verified WhatsApp Business account to send booking confirmations, flight updates, and customer-service replies in the channel passengers already used. The lesson is simple: a new channel is useful only when the context travels with the customer.
Zendesk’s CX Trends research, based on thousands of consumers and businesses, repeatedly shows that people judge service by speed, continuity, and whether they have to repeat themselves. As email, WhatsApp, voice, and web chat converge, “we have a chatbot” is no longer a meaningful product description.
What a useful chat stack must do
Start with the question the visitor is trying to answer, not the channel you want to promote. A product demo request, a delivery question, and a technical incident need different routes and different response times.
At minimum, make these moments visible:
• the first human handoff and the information passed with it;
• the trigger that moves a conversation from web chat to email, WhatsApp, or voice;
• the owner, service-level agreement, and next action for every open thread;
• the point where a helpful answer becomes a sales opportunity.
Teams often buy features one at a time and create a fragmented experience. A visitor starts in web chat, receives an automated reply, opens an email ticket, and then calls—while three systems each show only part of the story. The fix is to design the journey first and map each channel to a job.
Before launch, write five failure scenarios: an unanswered question, an angry customer, a lead outside business hours, a request that needs a document, and a conversation that must be escalated. Test whether the transcript, contact details, consent, and promised follow-up survive every handoff. Measure time to useful answer, not just bot containment.
The best live chat features are the ones a customer never notices: clear ownership, preserved context, and a fast path to a person when the situation deserves one. That is how a small support team can feel present without pretending automation is a substitute for judgment.
