Zendesk Chat and Messaging
Two similar-sounding things with a meaningful difference: one expects the customer to stay, the other does not.
The distinction that matters
Live chat is synchronous. The customer is on your site now, waiting for a person, and if nobody answers within a minute or two the experience fails.
Messaging is asynchronous and persistent. The conversation continues across sessions and devices, the customer can leave and come back, and the thread survives.
Messaging is far more forgiving to staff, and it is the right default for most teams unless you have the coverage to answer live chat quickly and consistently.
Staffing reality
Live chat only works if you are genuinely there. A chat widget with nobody behind it does more damage than no widget, because the customer has now been ignored in real time rather than merely waited for a reply.
Be honest about coverage. Turn chat off outside your hours and switch to a contact form or messaging, rather than leaving a hopeful widget that nobody answers.
The duplicate pattern chat creates
A customer starts a chat, waits, gives up, and emails instead. Or the chat ends unresolved and they email to follow up rather than reopening the thread.
Either way you get two records of one problem, minutes apart, on two channels, worded differently. Adding chat to an email queue reliably increases the duplicate rate, and the increase is proportional to how slowly you answer chats.
Frequently asked questions
What is the difference between Zendesk Chat and messaging?+
Chat is synchronous and session-based. Messaging is asynchronous and persistent across sessions, which is easier to staff.
Should we turn chat off outside business hours?+
Yes, or switch it to messaging or a form. An unanswered live chat is worse than no chat.
Chat then email is one request
Cross-channel duplicates are the most common kind and the hardest for a human to spot. Ticket Merger matches across channels.
Start free trial14-day free trial. No credit card required.