Zendesk Livechat, Enabled Properly
Switching Zendesk livechat on takes about ten minutes. Making it answer the right person within a minute takes a fortnight, and that's the part worth reading about.
Work out which Zendesk livechat product you're enabling
This matters before you follow any instructions, including these.
Zendesk has sold two things that people call live chat. The older standalone Chat product was session-based: the visitor was there or they weren't, and the conversation ended with the tab. The current model is messaging, which persists across sessions and devices and lands in the agent workspace as a normal ticket.
New accounts get messaging. Older accounts may still be running the legacy product, or may have been migrated at some point. Whether that legacy product still exists in any form for your account is worth confirming against the current Zendesk docs rather than against a blog post, because this area has moved repeatedly. If your chats vanish when the visitor navigates away, you're on the old one.
Everything below assumes messaging, which is what "enable Zendesk chat" means for almost everybody today. The conceptual difference is covered in chat and messaging.
Turning it on
The sequence is short. In Admin Center, under the channels section, you configure a messaging channel for a brand, which produces a web widget you then publish and embed. Exact menu labels shift between releases, so navigate by concept rather than by memorising a path.
Then three things people forget on day one.
Getting chats to the right agent
Routing is where live chat is won or lost, and there are broadly three levers.
Groups. The blunt instrument, and usually the right first move. Sales chats to sales, support chats to support, based on which page the widget was opened from or what the visitor picked in the pre-chat form.
Omnichannel routing. If your account has it, this assigns conversations to available agents by capacity rather than letting them sit in a shared queue for whoever notices first. It's the single biggest improvement most teams can make, and it's covered in more depth in the omnichannel routing guide.
Triggers and skills. Finer-grained: language, product area, VIP accounts. Worth adding once the basics work, and a fantastic way to build something unmaintainable if you start here.
Don't route on more than two attributes to begin with. Every additional condition creates a case where nobody matches, and the customer sits there watching a typing indicator that never appears.
Concurrency, status and the queue
An agent handling email does one thing at a time. An agent on chat is expected to juggle, and how many is a setting rather than a law of nature.
Two or three concurrent chats is the honest ceiling for anything requiring thought. Some teams set six. Their reply times look fine in aggregate and every individual customer waits ninety seconds between messages, which feels awful and doesn't show up in the average at all.
Agent status matters just as much. Online, away and invisible do different things to routing, and an agent who forgets to go away at lunch is a black hole that swallows chats. Build the status change into your break routine, or accept that you will lose conversations to it every single day.
And decide what happens when everyone is full. A queue with a stated position is tolerable. A queue with no feedback is where people leave and email you instead, which is how a chat rollout quietly increases your email volume.
Operating hours, said plainly
Set business hours and mean them. Outside those hours the widget should say so and collect a message, not sit there hopefully.
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 waiting for a reply. That's worth repeating, because almost every team gets it wrong at least once.
The first fortnight checklist
Frequently asked questions
What does Zendesk chat setup involve?
Enable the channel, add the widget, set operating hours and agent capacity. Zendesk live chat setup takes ten minutes; making Zendesk online chat answer within a minute takes a fortnight of staffing work.
How do I enable Zendesk livechat?
Configure a messaging channel for your brand in Admin Center, publish the widget, embed the script on your site, then give agents the group and role that receives conversations.
Is Zendesk Chat the same as Zendesk messaging?
Not historically. Chat was session-based, messaging persists across sessions. New accounts get messaging, and the older product has been progressively retired. Check current Zendesk docs for your account.
How many chats should one agent handle at once?
Two or three for anything that needs thinking. Higher limits look efficient in reporting and feel slow to every customer in the queue.
Why is nobody receiving chats?
Almost always agent status, group membership or the role. Check those three before you touch routing rules.
Should chat be on outside business hours?
Only in a mode that collects a message and says when you will reply. An unanswered live chat is worse than no chat at all.
A new channel adds duplicates
Adding chat to an email queue reliably increases the duplicate rate. Ticket Merger matches across channels and merges the pair.
Start free trial14-day free trial. No credit card required.