Weighing live chat vs messaging customer support for your team? Live chat is a session that ends when the customer leaves; messaging is a thread that waits. Pick chat for quick, urgent questions, messaging for the rest.
This guide sits inside our wider look at customer service messaging.
| Item | Value |
|---|---|
| Live chat conversation model (Zendesk Chat) | Session-based and synchronous |
| Messaging conversation model (Zendesk messaging) | Persistent and asynchronous |
| Live chat requests with no response (SuperOffice study) | One in five live chat requests |
| Average wait in that study | More than 2.5 minutes |
| Active threads one async agent can handle (Chatty) | 10 or more threads |
| Zendesk Chat deprecation date (announced August 4, 2026) | January 31, 2028 |
The figures come from Chatty and Macha, two vendor blogs. Figures can change, so check the source before you rely on them.
How live chat and messaging differ
Live chat is synchronous. Help Desk Migration describes it as two parties actively engaging in a live conversation that ends as soon as one party stops responding or leaves, and says so in its guide to asynchronous chat.
Messaging is asynchronous. The same Help Desk Migration guide says participants can pause and resume the discussion as they see fit, so a customer can leave your website and come back later to check for a reply. It lists email, SMS, forums, WhatsApp and Facebook Messenger as examples.
The labels depend partly on software. In a 2018 CustomerThink article, Jeremy Watkin notes that synchronous channels always include phone but, depending on the software, can also include live chat and other messaging channels.
Macha, a company that builds tools for help desks, compares Zendesk’s two products side by side. Treat it as one vendor’s view of one platform, not a rule for every tool:
| Question | Live chat (Zendesk Chat) | Messaging (Zendesk) |
|---|---|---|
| Conversation model | Session-based and synchronous | Persistent and asynchronous |
| When the customer leaves | The session times out and ends | The thread waits and resumes |
| Agent must be online | Effectively yes | No, a later reply is normal |
| History | Tied to the session | Travels with the thread |
Source: Macha. The practical gist is that session versus thread drives most of the other differences.
Where live chat still wins
Watkin’s CustomerThink piece groups phone, in person, video and synchronous chat together. He describes synchronous communication as a live conversation with a clear start and end, usually with faster response times. He credits it with three advantages:
- Escalated issues: he calls a phone call or an in-person visit with someone empowered to solve the issue still the best channel once a conversation needs to cut to the chase.
- A clear start and finish: he notes there is always a start and a finish, generally dictated by the customer.
- Human connection: where a genuine human-to-human connection is required or desired, he says synchronous communication is the way to go.
Help Desk Migration adds that synchronous messaging suits customers who want an instant response to a fairly simple problem or question, as its guide puts it.
Where messaging wins
The classic live chat complaint is the disconnect. Watkin says many contact centers close a chat if customers do not respond in three to five minutes, and that customers often feel abandoned and dread starting all over again, as he writes in CustomerThink.
Messaging avoids that because the conversation never actually ends. He also points to mobile: the rise of messaging channels is due largely to our dependence on mobile devices, and asynchronous conversations travel with the customer. He adds that asynchronous channels pave the way for AI to answer questions that a knowledge base article can solve.
Zendesk, a help desk vendor, argues in a post last updated 4 November 2021 that messaging takes the best parts of live chat and adds ongoing conversations, automation and richer content. Read that as a vendor’s pitch, and read it on Zendesk’s own page before you rely on it.

What the numbers say about waiting and workload
Chatty, a vendor of customer messaging software, cites a SuperOffice study finding that one in five live chat requests receives no response, with average wait times exceeding 2.5 minutes. You can find that claim in Chatty’s article.
The same article says async agents can manage 5 to 6 times more conversations than live chat agents, because they are not locked into real-time sessions and can handle 10 or more active threads at once. That is a vendor claim, not an independent benchmark, so test it against your own team’s workload.
Speed still matters in both models. For more on reply targets, see our guide to the average customer support response time.
Which should you choose?
You probably do not have to pick one. Watkin writes that there is a place in your support operation for both synchronous and asynchronous communication, and he says so in his CustomerThink article.
A simple way to decide:
- List your most common questions and mark which are quick and urgent and which need research or a long back-and-forth.
- Check your staffing. Live chat effectively needs an agent online; messaging does not, according to Macha’s comparison.
- Check whether your tool can run a thread in either mode, so urgent questions get a live reply and slower ones wait.
- Decide when a conversation is allowed to end, so customers are not cut off while they step away.
If you run Zendesk Chat, plan ahead. As of Macha’s September 20, 2026 update, Zendesk announced Chat’s removal on August 4, 2026 and will deprecate it on January 31, 2028, and the same page says messaging can be configured as synchronous, asynchronous or both. You can check the details on Macha’s page.
Tense conversations need a plan in either channel, so read our guide on how to respond to angry customer messages.
Frequently asked questions
Is messaging just live chat with a new name?
Show answer
No. The core difference is a session that ends versus a persistent thread that resumes, according to Macha. Some tools can blur the line, since a thread may be set up as synchronous, asynchronous or both.
Do agents need to be online all the time for messaging?
Show answer
Not in the same way as live chat. Macha’s comparison says that with messaging, a later reply is normal, while live chat effectively needs an agent online. See Macha’s comparison.
Which channel is better for complex problems?
Show answer
Sources differ. Watkin names phone or in-person contact as best for escalated issues, in CustomerThink. Help Desk Migration calls asynchronous messaging a good option for complicated issues that need a longer time to resolve.
Is Zendesk Chat going away?
Show answer
As of Macha’s September 20, 2026 update, Zendesk announced the removal of Chat on August 4, 2026 and scheduled deprecation for January 31, 2028. Check the source for changes before you plan around the date.



