Live Channels
Part of Live chat and messaging support
Comparing synchronous chat with asynchronous messaging
Compare chat and asynchronous messaging by customer presence, staffing, reply expectations and conversation continuity.
Choose synchronous chat when an available agent and customer need a short exchange now. Choose asynchronous messaging when either side may pause and return later. Messaging can be rapid too, so the test is whether the customer must stay for the answer, not how quickly an agent can type.
Compare the customer’s commitment
| Decision | Synchronous chat | Asynchronous messaging |
|---|---|---|
| Presence | Customer and agent stay available during the exchange | Either can return later |
| Likely fit | A question that can be clarified and resolved during the current visit | A question that may need research, approval or an out-of-hours reply |
| Response promise | A prompt human response while chat is offered | A stated next-response expectation |
| Continuity | An unfinished exchange needs a follow-up route | A returning person needs the right thread and history |
These are operating choices, not guarantees about every product. Zendesk describes its live chat as session based and its messaging as resumable; it also says messaging can happen in real time.
An account-access question may suit an available agent asking a few questions while the customer is at the screen. A disputed delivery may need a record check and a later answer. Issue type alone does not settle the choice: availability and identity verification also matter.
Match the promise to staffing
A live option needs staff able to accept and sustain conversations. Help Scout’s Beacon shows chat when a user is available and a message screen when the team is unavailable. That behaviour depends on Beacon’s availability settings; other widgets may work differently.
Asynchronous messaging needs someone to check new messages and replies to existing threads. Tell customers when they can expect the next response, especially outside staffed hours. Zendesk’s messaging Web Widget stays available while agents are offline, and Zendesk advises setting that expectation. A retained thread still needs a monitored return path.
Check continuity
Ask how the product recognises a returning customer, which history the agent sees and what happens when the customer changes device or contact details. Help Scout’s basic Beacon support-history setting uses the visitor’s browser session and device. Its advanced setting requires a secure key for history across devices. Neither setting establishes how another product handles identity.
Also ask how a live chat ends. Can the team retain the transcript, record the remaining action and send an answer through a usable contact route? A transcript does not make an anonymous visitor reachable by email.
Offering both modes may suit a team that can staff live chat for part of the day and monitor messages at other times. Compare an accepted chat, a missed chat, an overnight message and a returning customer. For each, identify the customer’s next step and the team’s next owner.
