Sistava

Zendesk AI Agents: How to Set Up One for Messaging

How-to — — by Mahmoud Zalt

A step by step walkthrough of turning on the Zendesk messaging widget, creating an AI agent, and publishing it so it answers customers live.

The most common way people get stuck here is assuming this is one setting. It is not. Zendesk keeps the chat window and the thing that answers in it as two different objects, configured in two different parts of Admin Center, and joined only at the moment you publish. Once you see it that way the whole process stops feeling confusing.

This walkthrough follows the order Zendesk's own documentation follows: widget first, agent second, publish third. Do it in that order and each step has something to point at. Do it out of order and you will create an agent with nowhere to live, which is a common first attempt.

What do you need before you start?

You need admin access and an active help center. Zendesk's documentation is explicit that creating an AI agent requires you to be an admin in both Support and Knowledge, and that the brand you attach the agent to must have an active help center, otherwise the brand selection returns an error.

On plans, their article on creating an AI agent lists availability across all Suite plans, meaning Team, Growth, Professional, Enterprise and Enterprise Plus, and across Support Team, Professional and Enterprise. Their messaging setup article says messaging is switched on in your account already and ready whenever you are, so there is usually nothing to purchase before you begin.

One thing worth doing before you touch any settings: write down the five questions your customers ask most. You will need them later to test the agent, and having them ready stops the test phase turning into an hour of typing whatever comes to mind.

How do you set up the Web Widget for messaging?

You configure it in Admin Center under Channels, then Messaging and social, then Messaging. Zendesk's documentation notes that a basic Web Widget named Zendesk already exists in your Channels list, so most accounts are editing a widget rather than creating one. Accounts created before 2 November 2021 use Add channel and then Web Widget instead.

The setup runs through three named sections. Start with the basics holds the channel name, the brand if you run more than one, and an option to add a privacy notice with a link to your own. Install on your site gives you the code snippet, or an option to embed the widget in your help center automatically if that help center is active. Make it your own covers the primary color, the widget title and an optional logo, with a live preview.

  1. Open the messaging channel list — In Admin Center, click Channels in the sidebar, then select Messaging and social, then Messaging. Click the existing widget named Zendesk, or use Add channel on older accounts.
  2. Fill in Start with the basics — Confirm or change the channel name, pick the brand if you have several, and decide whether to add a privacy notice. Click Next.
  3. Style it under Make it your own — Set the primary color with the picker or a hexadecimal value, set the widget title that shows in the header, and upload a logo if you want one. Use the preview to check it.
  4. Install it — Copy the code snippet from the install section and add it to your site, or send it to whoever owns the site. For a Zendesk help center, use the option to embed the widget automatically instead of pasting anything.
  5. Load a page and look for the bubble — Before going any further, confirm the widget actually appears on a real page. If it does not, the snippet is either missing or placed somewhere the page never reaches.

Two practical points that independent write ups raise and the official pages do not dwell on. Placing the script immediately before the closing body tag is the usual convention, and adding an async or defer attribute keeps the widget from delaying the rest of your page. The other is that the messaging widget and the older Web Widget known as Classic are different products, and only the messaging one supports AI agents and conversation history that survives a closed browser.

How do you create the AI agent?

You create it in Admin Center under AI, then AI agents, then AI agents, and click Create AI agent. The form is short. You give it a name, choose a tone of voice, and pick the brand whose help center it will draw on.

Zendesk's own guidance on the name is worth following: choose something that makes it obvious the customer is not talking to a person. That is partly a trust matter and partly a practical one, because customers who believe they are talking to a human phrase things in ways an automated answer handles badly. The tone options their documentation lists are Professional, which is the default, Informal, and Enthusiastic.

  1. Open the AI agents list — In Admin Center, click AI in the sidebar, then select AI agents, then AI agents.
  2. Click Create AI agent — Enter a name in the Name field. Pick one that signals clearly that this is an automated assistant rather than a member of staff.
  3. Choose the tone — Select Professional, Informal or Enthusiastic. Professional is the default and is the safe starting point for most support teams.
  4. Select the brand — Choose the brand from the dropdown. Its help center must be active, or Zendesk returns an error at this step.
  5. Test before you go further — Click Next and run your five real customer questions through the test. This is the step people skip and then regret.
  6. Open Advanced settings or move to publish — Advanced settings holds further configuration. Go to publish takes you to the step that makes the agent live.

How do you publish the agent to the widget?

Publishing is what connects the two objects, and until you do it the agent is invisible to customers. Zendesk's documentation on brand and channel configuration puts these controls on the Settings tab of the individual agent, inside an expandable Brand and channels section.

That section holds a dropdown for which brand's help center the agent uses, an option about showing titles and previews for restricted articles, and separate groups of channel checkboxes for messaging channels and for email and web form channels. Their documentation notes that enabling the email and web form group also enables the API channel. It also states plainly that channel changes do not reach customers until you publish the agent.

So the mental model is: edit the settings, then publish. Editing alone changes nothing your customers see. If you make a change and it does not appear on your site, the publish step is the first thing to check, not the widget.

Why does some Zendesk documentation say Essential and Advanced?

Because the packaging changed partway through 2026 and the documentation is catching up. Zendesk announced on 30 March 2026 that the distinction between the Essential and Advanced AI agent plans is being removed and all customers move to a single offering.

Their announcement gives the rollout as beginning 11 May 2026 and ending 12 June 2026, with capabilities previously limited to the Advanced add-on, including agentic reasoning, multi-step procedures and external API integrations, becoming available across plans. The same announcement says development stops on Essential and legacy functionality by 31 August 2026 and that the full shutdown is 10 December 2026, and that no immediate action is required.

The practical effect for you today is that search results will surface pages titled Legacy alongside current ones, and the steps differ. Check the title of any Zendesk help page before you follow it. If it says Legacy and your account is on the newer packaging, the screens will not match and you will waste an afternoon looking for a menu that is no longer there.

What should you check before you trust it?

Run the five questions you wrote down at the start, then run five more that the agent should refuse. Billing disputes, account deletion requests, anything with a legal or financial edge. What you are looking for is not a perfect answer, it is a clean handover to a person.

Then watch it on real traffic for a week before you widen its reach. Most first week problems are not the software. They are a help center that does not actually contain the answer, or an agent published to more channels than anyone intended.

That week of watching is also where the difference between products shows up. Zendesk gives you a configured agent that behaves consistently within what you set up, which is genuinely what a lot of support teams want. At Sistava we went the other way and made the thing you hire behave more like a colleague, so that briefing it in a paragraph replaces the configuration entirely. Neither is the right answer for everyone, and knowing which shape suits you is worth more than any feature list.

FAQ

Do you need the Web Widget before you can create a Zendesk AI agent?

Not strictly, you can create the agent first. But the agent has nowhere to appear until a messaging channel exists, and publishing is the step that joins them. Setting up the widget first means every later step has something concrete to point at, which is why Zendesk's own getting started material puts messaging setup ahead of agent creation.

Can a Zendesk AI agent answer on more than one channel?

Yes. Zendesk's brand and channels documentation describes separate groups of channel checkboxes, one for messaging channels and one for email and web form channels, on the agent's Settings tab. It also notes that enabling the email and web form group enables the API channel too. Changes only reach customers after you publish the agent.

Why is my Zendesk AI agent not appearing on my site?

Work through it in order. First check the widget itself loads on a real page, because if the snippet is missing nothing else matters. Then check the agent has been published, since Zendesk's documentation states that channel changes do not reach customers until publication. Then check the channel checkbox for that widget is actually selected on the agent's settings.

What tone options does a Zendesk AI agent have?

Zendesk's article on creating an AI agent lists three: Professional, which is the default, Informal, and Enthusiastic. Tone is set when you create the agent and shapes how its replies read. Professional is the sensible default for most support teams, and you can change it later.

Does the Zendesk AI agent need an active help center?

Yes for the brand you attach it to. Zendesk's documentation says selecting a brand whose help center is not active returns an error at that step. This makes sense given the agent draws on help center content to answer, so a brand with no live knowledge base gives it nothing to work from.

Is the messaging Web Widget the same as the older Zendesk chat widget?

No. The messaging widget and the older Web Widget known as Classic are separate products. The messaging one is the one that supports AI agents and keeps conversation history when a customer closes their browser. If you are setting up an AI agent today, the messaging widget is the one you want.

Sources