top of page
Search

How to Set Up an AI Agent in Zendesk: A Step-by-Step Guide

11 minutes ago
11 min read

A lot of the questions that land in a small business inbox already have an answer written down somewhere. Your opening hours are on the website. Your cancellation policy is in a help center article. The steps to reschedule are the same every time. Someone on your team still has to read each message, find the answer and type it out.


That's exactly the kind of work Zendesk's AI agents are built for. An AI agent can answer customers on your help center and over email using the articles you've already written, and it can walk someone through a simple request, like rescheduling a booking, before handing the conversation to a person.


This guide takes you through the whole setup, step by step, the same way we do it for clients. Keep it open next to Zendesk and work through it in order. Zendesk updates these screens regularly, so if a label looks slightly different on your account, the idea behind each step stays the same.


What a Zendesk AI agent actually does


Before you start clicking, it helps to understand the two ways an AI agent replies, because you set them up in different places.


  • Knowledge answers. When a customer asks a general question, the AI agent searches your help center (and any other knowledge sources you connect) and writes a reply from what it finds. If the answer isn't in your content, it won't invent one. It escalates instead.

  • Procedures. For specific requests you get all the time, you describe in plain English how you want them handled: what to ask, which rules to follow and when to bring in a person. Each procedure is attached to a use case, which is simply a type of request the agent learns to recognize, such as "reschedule an appointment".


When the AI agent can't help, or the customer asks for a human, it hands the conversation to your team as a ticket with everything it has already collected.


Flow diagram: a question arrives from the help center widget or support email, the AI agent checks for a matching use case, follows a procedure if there is one or answers from help center knowledge if not, and escalates to a human ticket when it is unsure

Which Zendesk plans include AI agents


AI agents are available on every current Zendesk Suite plan (Team, Growth, Professional, Enterprise and Enterprise Plus) and on the Support Team, Professional and Enterprise plans. You don't buy them as a separate product. Usage is measured in automated resolutions: each plan includes an allowance, and you pay for extra resolutions beyond it.


This is how it looked on Zendesk's pricing page at the time of writing (October 2026):


Plan

AI agents

Included automated resolutions

Support Team

Yes (email)

5 per agent, per month

Suite Team

Yes

5 per agent, per month

Suite Growth

Yes

Check your plan details

Suite Professional

Yes

10 per agent, per month

Suite Enterprise and Enterprise Plus

Yes

Agreed with Zendesk sales


Extra resolutions were listed at $1.50 each if you commit to a volume up front, or $2.00 each on pay-as-you-go. A few things worth knowing:

  • You're only charged when the AI agent actually solved the request. If it helped but a person finished the job, that doesn't count against your allowance. Zendesk explains the details in About automated resolution tiers.

  • The help center chat experience runs on Zendesk messaging and the Web Widget, which come with the Suite plans. If you're on a Support-only plan, an email AI agent is the place to start.

  • Testing on your live account uses automated resolutions too, so keep your testing focused (or use a sandbox if your plan has one).

  • Prices and allowances change, so confirm on Zendesk's pricing page before you budget.


The setup at a glance


Eight setup steps: prepare your help center, set up your channels, create the AI agent, connect knowledge and set the voice, write the system replies, add a use case and procedure, test everything, go live and keep improving

Set aside an afternoon for the first agent. Most of that time goes into steps 1 and 6, and both pay off for as long as the agent runs.


Step 1: Prepare your help center


Your AI agent is only as good as the content behind it. If an answer isn't in your help center, the agent can't give it. This is the step most people rush, and it's the one that makes the biggest difference.


  1. Pull your last 50 to 100 customer emails or tickets and list the questions that come up again and again. For most small businesses, 10 to 20 questions cover the majority of requests.

  2. Check that each of those questions has its own help center article. In Zendesk, articles are managed in Knowledge admin (open the product tray in the top bar and choose Knowledge).

  3. Write one question per article, and use the question as the title, the way a customer would ask it: "How do I reschedule my appointment?" works far better than "Scheduling policy".

  4. Put the actual answer in the first two or three sentences. Include the specifics: times, prices, notice periods, what the customer needs to send you.

  5. Remove or update anything out of date. The agent will happily quote an old price if it's still published.

  6. Make sure your help center is activated and the articles are visible to customers.


Tip: if you don't have a help center yet, we covered how to set one up in our post How to set up your Zendesk Help Center.


Step 2: Set up your channels


The AI agent works on a channel, so the channel has to exist first. Set up whichever of these you plan to use.


For email


Your support address (for example support@yourbusiness.com) needs to be connected to Zendesk and creating tickets. In Admin Center, check under Channels > Talk and email > Email (then Manage support addresses) that the address is listed, verified and linked to the right brand. Send a test email from a personal account and confirm a ticket appears.


For your help center


Customers talk to the AI agent on your help center through the messaging Web Widget, the chat button in the corner of the page. To add it:

  1. In Admin Center, go to Channels > Messaging and social > Messaging.

  2. Click the name of your Web Widget (or create one if the list is empty).

  3. Scroll down and expand Installation.

  4. Tick Automatically embed Web Widget in your Help Center and click Save.


The widget now appears on every help center page. If the checkbox doesn't show, your help center isn't activated yet. Zendesk's guide to installing the Web Widget also covers adding it to your main website, which is worth doing at the same time.


Step 3: Create the AI agent


  1. Open the product tray in Zendesk's top bar and choose AI agents. This opens the AI agents workspace. (You need admin access to the workspace to create an agent.)

  2. In the sidebar, click Dashboard, then Create AI agent.

  3. Choose the channel: for Messaging (the help center and website widget) or for Email.


Each AI agent works on one channel type. If you want both help center chat and email covered, you'll go through this flow twice and end up with two agents. We suggest starting with the channel that gets the most repetitive questions, getting it right, then creating the second agent using what you learned.


Step 4: Connect your knowledge and set the voice


Connect knowledge


On the Power your AI agent with knowledge screen, select your brand and its help center. You need at least one active knowledge source to continue.

  • For a messaging agent, Zendesk will ask you to turn on help center authentication if it isn't already on.

  • If you keep useful content elsewhere, click Edit sources to connect external sources, or add a web crawler to read pages from your website. Only connect content you'd be happy for a customer to read word for word.


Set the name, tone and language


On the Set language and tone of voice screen, fill in:

  • Name. Something simple, like "Bright Dental Assistant". Avoid giving it a human name and pretending it's a person; customers are fine with an assistant as long as it's honest.

  • Business profile. A short, factual description the agent uses as background for every reply. Keep it to a few sentences.

  • Tone of voice. Pick the option closest to how your team already writes to customers.

  • Languages. Set your default language and add any languages it should translate into. For messaging, you can also upload an avatar, such as your logo.


Here's the kind of business profile that works well:


Bright Dental is a family dental practice in Tampa, Florida. We offer check-ups, cleanings, fillings and teeth whitening for adults and children. We're open Monday to Friday, 8am to 5pm. Appointments can be booked online or by phone. We need 24 hours' notice to change or cancel an appointment.

Step 5: Write the system replies


System replies are the fixed messages around each conversation. They're short, but customers see them constantly, so write them in your own voice rather than leaving the defaults.


For a messaging agent you'll set four:

  • Greeting: "Hi! I can help with appointments, opening hours and our services. What can I help you with today?"

  • Wrap-up: "Glad I could help. Is there anything else you need?"

  • Escalation: "I'm passing you to our team now. We reply during business hours, Monday to Friday, 8am to 5pm."

  • Fallback: "Sorry, I didn't quite get that. Could you tell me a little more about what you need?"


For an email agent you write one: the message customers receive when their email is handed to your team. Set a clear expectation, for example: "Thanks for your email. We've passed it to our team and someone will reply by the end of the next business day."


After the system replies, Zendesk may show an Automate support topics page with suggested articles or procedures based on your past tickets. Open each one with View details and approve the ones that look right. Then let the automatic test run, and click Save and close. Don't activate yet; there's one more important piece to add.


Step 6: Add a use case and a procedure


This is where the AI agent goes from answering questions to actually handling requests. Pick one request you get every week and set it up properly before adding more. We'll use rescheduling an appointment as the example.


Diagram showing a use case named Reschedule an appointment, with its reason for request and reply method, connected to a procedure with five steps: ask for booking details, ask for preferred new time, check whether the appointment is within 24 hours, explain the policy, and hand over to the scheduling team

Create the use case


  1. In the AI agents workspace, select your AI agent.

  2. In the sidebar, click Content > Use cases, then Create use case.

  3. Name: keep it short and clear, for example "Reschedule an appointment".

  4. Reason for request: describe why the customer is getting in touch, for example "Customer wants to move an existing appointment to a different day or time." The agent uses the name and this description to recognize the request, so be specific.

  5. Leave Category and Segment empty for now (they're optional) and click Create.


Tip: the Suggestions tab has a Generate suggestions button that proposes use cases from your past conversations. It's a quick way to see what your customers ask most. Zendesk's guide to creating use cases has more examples.


Write the procedure


  1. Open the use case you just created.

  2. Under Reply method, make sure Use procedure when use case is triggered is selected.

  3. On the Procedure tab, click Create procedure.

  4. Describe, in plain English, how the request should be handled. Write it the way you'd explain it to a new team member on their first day.

  5. Click Generate procedure. Zendesk turns your description into a step-by-step map you can review.

  6. If something isn't right, type a specific change in the box at the bottom (for example "Also ask for a phone number") and click Update procedure. Small, targeted changes work better than rewriting the whole thing.

  7. When you're happy, click Publish procedure.


Here's a procedure you can adapt for your own business:


When a customer wants to reschedule an appointment, ask for the name the booking is under and their current appointment date and time. Ask what new day and time they would prefer, and whether any other times would also work. If the current appointment is less than 24 hours away, explain that we need 24 hours' notice for changes, and that our team will do their best to help. Do not confirm a new time yourself. Thank the customer, tell them a team member will confirm the new time within one business day, and hand the conversation to the scheduling team with all the details collected.

A few things make procedures work well:

  • Tell it exactly what to collect, in what order.

  • Spell out your rules, including the exceptions.

  • Say clearly what it must not do (like confirming a booking it can't actually make).

  • End every procedure with what happens next: a confirmation, or a handover to your team.


If you use a booking, order or CRM system that Zendesk can connect to, procedures can also call those integrations to look things up or make changes, by typing a forward slash (/) in the procedure to insert an action. You don't need that to get value on day one. Zendesk's guide to creating procedures and best practices for writing procedures are both worth reading before you write your first one.


Step 7: Test everything


Don't skip this. Ten minutes of testing will catch the answers that would otherwise embarrass you in front of a customer.


Test the procedure (messaging agents)


  1. Open the procedure and click Test procedure.

  2. In the dialog that appears, click Test without parameters.

  3. Chat with the agent in the test window as if you were a customer. Try the normal case, then try the awkward ones: missing details, a booking in two hours, a customer who changes their mind halfway through.


Testing always uses your latest changes, even unpublished drafts. If something goes wrong, edit the procedure and test again. Every published version is saved, so you can restore an earlier one from the version history if you need to (Zendesk's guide to managing procedures shows how).


Test an email agent


  1. Send an email to the support address the agent is connected to, from a personal email address. The agent ignores tickets submitted by your own team, so a test sent from an agent account won't get a reply.

  2. Check the reply in your inbox, and in the AI agents workspace under Conversation logs.

  3. Adjust your articles, replies or procedures, and send another test.


Once an email agent is live, Zendesk recommends testing changes on a copy of the agent connected to a separate test address, so your customers never see a half-finished change. The steps are in Creating a test email for AI agents.


What to test


Use this as a checklist:

  • Your five most common questions, worded the way customers really write them (including typos).

  • A question that isn't covered in your help center. It should escalate, not guess.

  • A customer asking for a person. It should hand over straight away.

  • Your procedure, from start to finish, including the exception (less than 24 hours' notice in our example).

  • Something completely off-topic, like a sales enquiry or a job application.


Almost every weak answer traces back to a missing or unclear help center article. Fix the article, not the agent, and test again.


Step 8: Go live and keep improving


Activate the agent


  1. Open your AI agent in the AI agents workspace and go to its activation settings (in the creation flow, this is the Go to activation button).

  2. Select the channels: your Web Widget for the help center, or your support address for email.

  3. Click Activate on channels.


For email, the agent starts replying to new emails that arrive on the selected address. For messaging, open your help center in a private browser window and check the widget is there and the greeting appears.


Check two settings before you walk away


  • Who replies. For email agents, go to Settings > General > Sender and use the system user. Don't send AI replies from a team member's account. Zendesk covers this in Managing AI agents connected to email channels.

  • Where escalations land. Make sure tickets handed over by the AI agent show up in a view your team actually watches, and are assigned to the right group. An escalation nobody sees is worse than no AI agent at all.


The first month


The first few weeks are when you get the most improvement for the least effort. Once a week:

  • Read a sample of conversations in Conversation logs, especially the ones that escalated.

  • When the agent couldn't answer, write or update a help center article.

  • Check Reporting in the AI agents workspace for resolution and escalation rates.

  • Add one new use case and procedure at a time, based on what customers actually ask.

  • Keep an eye on your automated resolutions so there are no surprises on the bill.


If you want to try all of this before committing, you can start a free Zendesk trial and build a test agent against a few sample articles. Zendesk's own AI agent setup guide is a good reference if anything on your screen looks different from what we've described.


The short version


A good Zendesk AI agent comes down to three things: help center content that actually answers your customers' questions, clear procedures for the requests you handle every week, and honest testing before you switch it on. Start with one channel and one procedure, watch how it does for a few weeks, and build from there. Your customers get answers faster, and your team gets time back for the conversations that really need a person.



Want help setting up your AI agent?


Our Small Business Launch Bundle gets your Zendesk help desk and help center set up properly from the start, which is exactly the foundation an AI agent needs. Once you're up and running, we can add an AI agent on top and write your first procedures with you.



Already on Zendesk and wondering whether an AI agent makes sense for your business? Send us a message and we'll talk it through.



We share practical Zendesk and small business support guides every week. Subscribe so you don't miss the next one.



 
 
 

Comments


bottom of page