How to Set Up Zendesk Messaging (Step by Step)
If you're tackling Zendesk live chat setup — a live-chat-style experience on your website or app, but one where the conversation doesn't vanish the moment the customer closes the tab — what you actually want to set up is Zendesk messaging, not the old live Chat. Messaging is Zendesk's modern, persistent conversational channel: the thread stays put, picks up where it left off across web and mobile, and lands in your team's queue as a regular ticket. This guide walks through setting it up, step by step, from flipping it on in the Admin Center to testing it live.
One thing to get straight first, because it's the most common point of confusion in any "Zendesk live chat setup": Zendesk now steers all new setups to messaging rather than the legacy live Chat product. If you're starting fresh, messaging is the channel you turn on — there's no separate "live chat" toggle. For how the two differ (and why messaging won), see our companion guide on Zendesk messaging vs. live chat. Every step below is verified against Zendesk's own documentation; Zendesk revises its UI periodically, so confirm labels in your own account.
Before you start: what you'll need
A few prerequisites save you a mid-setup detour:
- Admin access. Turning on messaging and adding channels happens in Admin Center, which requires an admin role.
- Agent Workspace turned on. Messaging requires the Zendesk Agent Workspace — it's the unified interface where chats, email, and other channels share one ticket view. Most accounts already have it on; new accounts get it by default.
- A decision on where you want chat to appear. Website, mobile app, social DMs, or some combination. You can add more channels later, so don't overthink it — but knowing your first target makes Step 3 quick.
Step 1 — Turn on messaging
Messaging is enabled at the account level first, then configured per channel. To turn it on:
- In the Admin Center, click Channels in the left sidebar.
- Select Messaging and social, then Messaging.
- If it isn't already on, open Manage settings, tick Turn on messaging for your account, and click Save settings.
The full path is Admin Center → Channels → Messaging and social → Messaging. One caveat that saves confusion: on most newer accounts, messaging is already on by default — Zendesk creates a default Web Widget for you, so you may land on this page with messaging live and nothing to switch. The explicit "turn on messaging" step mainly applies to older accounts (or ones that previously ran legacy live Chat). Either way, this is the page you manage it from.
Flipping messaging on activates it across the Web Widget, the Android SDK, and the iOS SDK (Unity is also available) — one switch unlocks every place a messaging conversation can live. You're not committing to all of them; you're just making them available to configure.
Step 2 — Select your brands
If your account runs multiple brands (separate storefronts, products, or help centers under one Zendesk), you'll be prompted to choose which brands messaging applies to. Use the drop-down to select them.
Why this matters: each brand gets its own messaging configuration and its own widget, so customers on different brands can see different greetings, business hours, and even different AI agents. If you run a single brand, this is a non-decision — messaging simply applies to it. Multi-brand teams should map out which brands need chat before configuring, so you don't half-configure one and forget the other.
Step 3 — Add your channel(s)
Now you tell messaging where to appear. On the Messaging page, click Add channel and pick the type:
- Web Widget — the chat bubble on your website or help center. This is the most common starting point. Enter a channel name, select the brand, and Zendesk generates a code snippet you (or a developer) drop into your site's
<head>. If you've used the Zendesk Web Widget before, this is the same widget — now powered by messaging instead of legacy Chat. - Mobile SDK (Android / iOS / Unity) — chat inside your native app. Create the channel, assign it to a brand, and Zendesk gives you a Channel ID. Hand that ID to your development team along with the linked install instructions; they embed the SDK and reference the Channel ID to wire it up.
- Social channels — under the same Messaging and social section, you can connect WhatsApp, Facebook Messenger, and Instagram so DMs from those platforms flow into the same queue as your widget conversations. Each requires authenticating the relevant account.
The big win: all of these — website, app, WhatsApp, Messenger — feed into one unified conversation stream for your agents.
Step 4 — Configure the conversation experience
A blank widget that just opens a text box is a wasted opportunity. The conversation experience is where you make messaging feel intentional. For your Web Widget or SDK channel, configure:
- The greeting. The first message a customer sees. Keep it specific ("Hi! Ask us anything about orders, returns, or your account") rather than a generic "How can I help?" — it sets expectations and nudges better first messages.
- Business hours. Tell messaging when your team is available so it can set the right expectation off-hours (e.g. "We're away until 9am — leave a message and we'll reply by email"). This prevents the worst chat experience: a customer typing into the void at 2am.
- An AI agent to answer first. When you turn on messaging, Zendesk automatically creates a default AI agent (bot) for the channel. It greets customers, suggests help-center articles, gathers details, and answers common questions before a human is needed — then hands off when it can't resolve something. You can customize its responses; for what Zendesk's AI can and can't do, see our guide to Zendesk AI.
Even a lightly configured AI agent changes the math: it handles the "where's my order?" volume so your humans see the conversations that actually need them.
Step 5 — Set up routing and agent capacity
Turning messaging on doesn't automatically decide who gets each conversation. That's the job of omnichannel routing, which routes messaging tickets to agents based on availability, skills, and how much they're already handling.
Two things to configure:
- Omnichannel routing. Enable it (Admin Center → Objects and rules → Omnichannel routing in most accounts) so messaging conversations are assigned to available agents automatically rather than sitting in a pile waiting to be grabbed.
- Agent capacity rules. Define how many concurrent conversations an agent can handle across channels — for example, one phone call but up to three simultaneous messaging chats. Capacity rules keep messaging from overwhelming a person who's already on a call, and they're what make "live" chat actually feel live instead of leaving customers waiting.
If you skip routing, conversations still arrive — but assignment becomes manual, which falls apart the moment you have more than a couple of agents.
Step 6 — Tune the Advanced settings
Back on the Messaging settings page, the Advanced section holds the controls that separate a tidy setup from a messy one. The ones worth setting deliberately:
- Download transcripts. Let end users save a copy of their conversation — useful for support records and a small trust signal.
- Multi-conversations. Allow a customer to run more than one conversation at a time (e.g. a billing question and a shipping question as separate threads) instead of cramming everything into one. Turn this on per channel — Web Widget, Android, or iOS.
- Ending sessions. Let end users explicitly end a conversation when they're done. Note the dependency: ending conversations requires multi-conversations to be turned on first, so enable that one first if you want this.
- Capacity release. Decide how long a conversation can sit idle (no customer reply) before Zendesk frees up the agent's capacity so they can take a new chat. In Advanced, open Capacity release, confirm auto-release is on, and set an inactivity period — a whole number from 3 to 15 minutes. This is the unsung hero of a busy queue: without it, agents stay "full" of customers who've already wandered off.
Most teams leave the defaults alone at first and revisit capacity release and multi-conversations once they see real traffic patterns.
Step 7 — Know how conversations land for agents
This is the reason messaging beats legacy live Chat: a messaging conversation arrives in the Agent Workspace as a persistent ticket — not an ephemeral chat window that disappears when the customer leaves, but a real ticket with full message history, sitting alongside the customer's email and phone tickets.
Practically, an agent can step away, the customer can close the browser, and the conversation simply waits and resumes — same thread, same context, days later if need be. Your agents work messaging like any other ticket: reply, add internal notes, apply macros, set status, route to another team. There's no separate "chat console" to learn. (This persistence is the core difference from legacy Chat — full comparison in messaging vs. live chat.)
Step 8 — Go live and test
Before you announce it, run the full loop yourself:
- Publish the widget. Make sure the Web Widget snippet is live on your site (or the SDK build is shipped). Load the page and confirm the chat bubble appears.
- Start a conversation as a customer. Open the widget, read the greeting, and ask a question your AI agent should handle. Confirm it responds.
- Trigger a handoff. Ask something the bot can't answer and verify it escalates to a human and that the conversation shows up as a ticket in the Agent Workspace, routed to the right agent.
- Reply as an agent, then check the customer side receives it. Test the off-hours message too, if you can, by checking outside business hours.
If anything misfires — the widget doesn't load, conversations don't route, the AI agent stays silent — retrace the matching step. Ninety percent of "it's not working" comes down to the snippet not being on the page, omnichannel routing being off, or the channel not assigned to the right brand.
Best practices and common mistakes
A few habits separate a messaging setup that helps from one that frustrates:
- Set business hours and an away message from day one. The fastest way to sour customers on chat is letting them message into silence overnight. Configure expectations before you go live.
- Let the AI agent take the first turn. Even a basic configuration deflects the repetitive questions and routes the rest with context. Launching with no bot means every "where's my order?" hits a human.
- **Turn on omnichannel routing and capacity rules together.** Routing without capacity limits buries your fastest agents; capacity without routing leaves conversations unassigned. They're a pair.
- Don't forget capacity release. Without it, idle conversations keep agents marked "full" and new customers wait behind people who already left.
- Test the handoff, not just the greeting. The greeting almost always works. The escalation-to-human path — and whether it lands as a routed ticket — is where setups actually break.
- Don't expect messaging to replace legacy Chat one-to-one. Some old Chat features behave differently or move; if you're migrating, audit them rather than assuming parity.
Where AI takes messaging further
Messaging's built-in AI agent is a great start — it greets, suggests articles, and collects details. But notice its ceiling: it mostly deflects with help-center content and hands off anything beyond a known flow. For a lot of teams, the gap is everything in between — the questions that need a real answer pulled from your knowledge base, past tickets, or another system, resolved right there in the thread.
That's the layer an AI agent like Macha adds. Macha isn't a help desk and it's not a Zendesk replacement — it runs on top of your existing Zendesk messaging channel. Instead of only suggesting an article or escalating, it reads the customer's actual question, pulls from your connected knowledge and past conversations, and resolves the issue inside the same messaging thread — while still handling the ticket housekeeping (tagging, status, routing) and escalating to a human, with full context attached, whenever it isn't confident.
The honest framing: it's another integration to configure, and it's only as good as the knowledge you connect to it. On cost, Macha bills per AI action — any automated step it takes, whether drafting a reply, tagging, routing, or resolving — not per closed conversation, because most automation isn't a tidy "resolution," it's work done along the way. If your messaging volume is mostly repetitive questions your help center could answer, that's the line where the built-in bot stops scaling. You can try it free — 7-day free trial, no credit card required.
Frequently asked questions
Where do I turn on Zendesk messaging? In the Admin Center: go to Channels → Messaging and social → Messaging. If messaging isn't already on (most new accounts have it on by default), open Manage settings, tick Turn on messaging for your account, and Save settings. This activates messaging across the Web Widget, Android SDK, and iOS SDK. From there you add specific channels.
Is "Zendesk live chat setup" the same as setting up messaging? For new accounts, yes — Zendesk now steers all new setups to messaging rather than the legacy live Chat product, so when people search for "live chat setup" they're almost always configuring messaging. Messaging is the modern, persistent successor; there's no separate "live chat" toggle to enable. See messaging vs. live chat for the difference.
How do I add Zendesk chat to my website? Add a Web Widget channel (Admin Center → Channels → Messaging and social → Messaging → Add channel → Web Widget), name it, pick the brand, and Zendesk generates a code snippet. Paste that snippet into your site's <head> and the chat bubble appears.
Can I add WhatsApp, Messenger, or Instagram? Yes. Under Messaging and social you can connect WhatsApp, Facebook Messenger, and Instagram so those DMs arrive in the same queue as your widget conversations. Each requires authenticating the relevant account.
Where do messaging conversations show up for agents? In the Agent Workspace, as persistent tickets. A messaging conversation isn't a disappearing chat window — it's a real ticket with full history that agents handle like any other, with the conversation resuming across sessions.
Do I need to set up an AI agent for messaging? You don't have to, but it's recommended. Turning on messaging automatically creates a default AI agent that greets customers, suggests articles, and answers common questions before handing off to a human. You can customize it, and you can layer a more capable AI agent on top later.
The bottom line
Setting up Zendesk messaging is a clear sequence: turn it on in Admin Center → Channels → Messaging and social → Messaging, pick your brands, add a channel (Web Widget snippet, mobile SDK, or social), configure the experience (greeting, business hours, an AI agent to answer first), set up routing and capacity, tune the Advanced settings (transcripts, multi-conversations, capacity release, ending sessions), then test the full loop before you go live. Remember the headline: messaging is the modern, persistent successor to legacy live Chat — conversations land as real, resumable tickets in the Agent Workspace. For the concepts behind the channel — how messaging differs from live Chat and when each made sense — see messaging vs. live chat.
Setup steps verified against Zendesk's official documentation, June 2026. Zendesk updates its product periodically — confirm labels in your own account before relying on them.
