← Back to list

From Chat to Talk: redBus’ Story of Enhancing Customer Support for Real-Time Issues

When a traveler is stranded at a bus stop at midnight, unsure if their bus is coming, the last thing they need is to wait in a chat queue…

Sibi in redbus India Blog · 2026-04-03 05:32 · 0 claps · 3.7 min read
#redbusproduct #customer-experience #customer-support #customer-satisfaction #redbus
Open on Medium ↗
Wiki topics: ✈️ · Travel

From Chat to Talk: redBus’ Story of Enhancing Customer Support for Real-Time Issues

When a traveler is stranded at a bus stop at midnight, unsure if their bus is coming, the last thing they need is to wait in a chat queue or be involved in a lengthy chat with a customer support representative. They need answers — fast. This tension between the scalability of chat and the urgency of real-world travel problems is one we’ve been grappling with at redBus for some time. Our answer: Chat-to-Voice Deflection — a smarter, context-aware support system that puts the right channel in front of the right customer at exactly the right moment.

The Problem with One-Size-Fits-All Support

Our support ecosystem is built to be efficient. The Self-Help flow handles the bulk of common queries, and for more complex situations, customers are connected to a live chat human agent. Chat has clear operational advantages — a single human agent can manage multiple conversations simultaneously, letting us serve higher volumes without proportionally scaling headcount.

But efficiency has its limits.

Two metrics told us something was broken: chat drops and missed chats.

  • Chat drops happen when a customer abandons the conversation after a human support agent has already connected — tying up that customer support representative in a dead-end interaction. The customer can typically abandon the conversation when the human agent is taking time to resolve an important issue that requires co-ordination with multiple parties.
  • Missed chats occur when customers give up waiting in queue before reaching a human support agent at all.

These two problems feed each other in a vicious cycle. Chat drops occupy human chat agents unproductively → queues grow longer → more customers abandon before connecting → more pressure on the remaining chat agents. For customers dealing with a live journey crisis — a no-show bus, a safety concern, a wrong boarding point — every minute of that delay compounds their anxiety.

The numbers confirmed what we intuitively knew: chat CSAT consistently lagged behind voice CSAT for time-critical issues. When the human agents need to loop in bus operators or drivers to gather real-time information, relaying that back through text introduces friction and delay that a phone call would eliminate in seconds.

For certain situations, chat isn’t just suboptimal. It’s the wrong tool entirely.

The Solution: Give Customers a Choice — But Only When It Matters

We didn’t want to abandon chat. It remains the right channel for the majority of support interactions. What we needed was a way to intelligently surface voice support for customers who needed it most, without overwhelming our voice capacity or degrading the experience for everyone else.

The result is Chat-to-Voice Deflection: a hybrid support model that presents a “Call” option alongside “Chat” — but only under two specific conditions.

1. The Nature of the Issue

The problem must qualify as a real-time, journey-critical situation:

  • Bus not showing up, breakdowns, or changes in boarding/drop-off points
  • Safety concerns — harassment, accidents, or disrespectful staff behavior
  • Operator-initiated bus cancellations
  • Live tracking failures
  • Boarding issues, such as needing the driver’s number or boarding point confirmation

2. The Timing

The customer must be within a defined window around their journey — currently 2 hours before departure or 2 hours after arrival.

Only when both conditions are met does the “Call” option appear. Everything else routes to standard chat. This precision ensures our voice support capacity is reserved for genuine emergencies, not routine queries.

Cutting the IVR Friction

One of the less obvious but significant wins of this feature is what it bypasses: our IVR system.

Traditional IVR flows — press 1 for this, press 2 for that — are a known pain point. Navigating a menu tree when you’re stressed and pressed for time is the opposite of helpful. While we’re actively rolling out an AI-powered voice bot to replace our legacy IVR, Chat-to-Voice Deflection offers an immediate shortcut: customers are connected directly to a live customer support representative, skipping the IVR tree entirely.

For someone in crisis, that’s not a small thing. It’s the difference between feeling supported and feeling abandoned.

The Results: Metrics That Matter

We launched Chat-to-Voice Deflection towards the end of last year, and the data has exceeded our expectations.

Customers Voted with Their Fingers

When given the choice, customers in urgent situations overwhelmingly chose to call with more than 50% customers preferring voice over chat. The preference is on similar lines for women travellers. The signal is clear: when customers in distress are given the option to speak to someone, they take it.

Additionally we saw a significant drop in missed chats while the chat CSAT also showed an improvement.

The Bigger Picture

At its core, Chat-to-Voice Deflection is about meeting customers where they are — not just geographically, but emotionally. A traveler dealing with a journey crisis isn’t just looking for information. They’re looking for reassurance. And sometimes, only a human voice can provide that.

By marrying the efficiency of chat with the empathy of voice, we’re not just improving metrics. We’re making the promise of a smooth journey feel a little more real — even when things don’t go according to plan.


메타데이터
post_id
033eb6e466f3
slug
from-chat-to-talk-redbus-story-of-enhancing-customer-support-for-real-time-issues-033eb6e466f3
url
https://medium.com/redbus-in/from-chat-to-talk-redbus-story-of-enhancing-customer-support-for-real-time-issues-033eb6e466f3
canonical_url
https://medium.com/redbus-in/from-chat-to-talk-redbus-story-of-enhancing-customer-support-for-real-time-issues-033eb6e466f3
author_url
https://medium.com/@sibi5161
status
ok
fetched_at
2026-06-10 18:44:10