Live chat is the real-time messaging surface where a human agent talks to a customer inside your website or app, rather than over email or phone. For teams evaluating support channels, it is the lowest-friction way to convert an automated conversation into a human one without losing context.
What live chat actually is
Live chat is a synchronous, text-based channel embedded in a web page or mobile app. A visitor opens a chat widget, a routing layer assigns the conversation to an available agent, and both sides exchange messages in real time. Unlike email, the session is live and typically resolved in one sitting. Unlike voice, agents can handle several sessions concurrently, which is why chat consistently lands as the most cost-efficient human-support channel per resolved contact.
Live chat versus chatbots
A chatbot is an automated responder; live chat is the human surface. The two are complementary, not interchangeable. A workable support stack runs the bot first for triage and simple intents, then escalates to a live agent when confidence drops, the customer asks for a person, or the intent is high-value. Devotel Orbit ships both: conversational chatbot flows for the front line and an agent inbox that receives hand-offs across chat channels with the transcript attached, so the agent picks up where the bot stopped.
What a good live-chat setup includes
- Routing and availability. Conversations go to the right queue based on intent, language, or customer tier, with agent capacity respected.
- Full context on hand-off. The agent sees the bot transcript, customer record, and prior conversation history in one view.
- Channel fallback. If the customer started on the website widget and continues on WhatsApp or SMS, the thread continues rather than restarting.
- Measurable outcomes. First-response time, resolution time, and containment rate (what the bot resolved without a human) are the numbers that matter.
When live chat is the wrong channel
Live chat adds staffing obligations. If volume is sporadic or your team is small, a bot-first flow with asynchronous channels such as WhatsApp or email may answer better than an empty chat window. The decision question is not whether to offer chat, but how the hand-off between automation and humans is designed.
Where it fits in Devotel Orbit
Devotel Orbit treats live chat as one channel in an omnichannel inbox rather than a standalone widget. Agents work web chat, WhatsApp, SMS, and email from the same queue, and bot hand-offs carry the full transcript. See the chat and inbox documentation under /docs for setup details, and /blog/omnichannel-shared-inbox-entry-level-ccaas for the shared-inbox model.