Zendesk bot builder to create guided flows for common issues

Kenneth Pangan
Written by

Kenneth Pangan

Katelin Teen
Reviewed by

Katelin Teen

Last edited October 28, 2025

Expert Verified

Let’s be honest, a huge chunk of the questions in your support queue are the same ones you dealt with yesterday. "Where's my order?" "How do I reset my password?" "Are you open on weekends?" Answering these on a loop is a quick way to burn out your team while more complex problems pile up.

Zendesk's answer to this is their bot builder, a tool designed to help you create automated conversations for these simple, repetitive questions. The idea is solid: build a flow once, and let the bot handle that question forever.

But if you’ve ever tried it, you know the reality can be a bit… messier. Building these flows is often a manual slog, and their success depends entirely on having a perfectly organized knowledge base. This guide will walk you through exactly how to use the Zendesk bot builder, step by step. We'll also get into its limitations and show you a more modern way to get the same job done, but with a lot less headache.

What you'll need to get started

Before you start building your first flow, you need to get a few things sorted out. This isn't exactly a plug-and-play tool, so a little prep work goes a long way.

  • Zendesk Suite Plan: You have to be on the Suite Team plan or higher. The basic support plans won’t work.

  • Admin Access: To create, edit, and publish these bots, you'll need to be an administrator in your Zendesk account.

  • An Active Help Center: The bot builder leans heavily on your Zendesk Guide articles. If your knowledge base is sparse, outdated, or just a bit chaotic, your bot won’t have much to work with and will probably just confuse customers.

  • A List of Common Issues: You can't automate a solution if you don't know the problem. Figure out the top 5-10 simple, high-volume questions your team is tired of answering manually.

Step-by-step guide to using the Zendesk bot builder

Once you have all your ducks in a row, you can jump into the builder itself. Here’s a look at how the process works inside Zendesk.

Step 1: Plan your first guided flow

It's tempting to try and automate everything right away, but that's a classic rookie mistake. Start with one simple, frequent issue. Think "Reset password" or "Track my order."

Before you even log into Zendesk, grab a pen and paper (or open a doc) and sketch out the conversation.

  • What’s the first thing the bot should say?

  • What buttons or options should the customer see?

  • Does the bot need to ask for info, like an order number?

  • When should the bot give up and hand the conversation over to a human?

Having a clear plan makes navigating the sometimes clunky interface a lot more bearable.

Step 2: Access the bot builder and create a new "answer"

Okay, now head into your Zendesk Admin Center. You'll find the tool under AI > AI agents > AI agents.

Here's where you hit the first bit of odd terminology. In Zendesk, a guided flow isn't called a "flow." It's called an "answer." You’ll need to create a new AI agent or add an "answer" to an existing one. Give it a straightforward name that describes the problem it solves, like "Password Reset Flow."

Navigating to the AI agents section within the Zendesk Admin Center to begin using the bot builder.
Navigating to the AI agents section within the Zendesk Admin Center to begin using the bot builder.

Step 3: Define training phrases to trigger the flow

This is the part where you have to play psychic. Zendesk needs you to manually type in examples of what a customer might say to kick off this specific conversation. For a password reset, you might add:

  • "password help"

  • "forgot my password"

  • "can't log in"

  • "reset my login"

Zendesk suggests adding at least 3-5 of these "training phrases." It's a manual process that banks on you guessing every possible way a user might phrase their problem. Good luck with that.

The interface for adding training phrases to trigger a flow in the Zendesk bot builder.
The interface for adding training phrases to trigger a flow in the Zendesk bot builder.

Step 4: Build the conversation flow

Welcome to the visual flow builder. This is where you'll be spending most of your time, and to be frank, it's where a lot of people get frustrated. You build the conversation by adding different types of "steps" and connecting them.

  • Send a message: This is just the text the bot shows. Your first step might be something like, "I can help with password resets."

  • Show help center articles: This step lets the bot search your knowledge base and suggest articles it thinks are relevant.

  • Offer options: This creates buttons for the user to click, like "Yes, that solved it" or "No, I still need help."

You have to manually build out every single branch of the conversation. If the user clicks "No," what happens next? You need another step. If they ask a question you didn't plan for, the flow just breaks. It can get messy, fast.

The visual flow builder interface used in the Zendesk bot builder.
The visual flow builder interface used in the Zendesk bot builder.

Step 5: Configure the handoff to a human agent

No bot is perfect. A smooth handoff to a human is an absolute must. You'll need to add a "Transfer to agent" step somewhere in your flow. This is the escape hatch for customers when the bot hits a wall. Make sure every path has a clear way for a user to talk to a person if they need to.

Adding a 'Transfer to agent' step is a critical part of using the Zendesk bot builder.
Adding a 'Transfer to agent' step is a critical part of using the Zendesk bot builder.

Step 6: Test and publish your flow

Zendesk has a preview tool that lets you click through the conversation like a customer would. You should test every single button and every branch to make sure there are no dead ends or weird loops. Once you feel reasonably good about it, you can hit publish and set it live.

Limitations of the Zendesk bot builder

If that whole process sounds a bit tedious and brittle, you're not wrong. Many teams find that the Zendesk bot builder is an okay starting point, but it has some real drawbacks that make it tough to rely on.

  • It’s time-consuming and rigid: Every flow has to be built by hand. Creating and maintaining these decision trees for every little issue can feel like a full-time job. The interface feels tacked on, not intuitive, especially once you get beyond a simple two-step conversation.

  • It’s only as smart as your knowledge base: The bot can only pull answers from your help center. If the information isn't in a perfectly written, up-to-date article, the bot is useless. It can't learn from all the valuable, real-world knowledge buried in past tickets, internal docs, or your agents' heads.

  • It creates dead ends: The second a customer asks something in a way you didn't predict, or has a follow-up question you didn't build a path for, the whole thing falls apart. This just annoys customers and defeats the purpose of trying to help them.

  • It’s hard to test properly: Clicking through a preview a few times isn't a real test. You have no real idea how the bot will handle thousands of unique, unpredictable customer questions. You're basically just launching it and hoping for the best.

Reddit
Welcome to the visual flow builder. This is where you'll be spending most of your time, and to be frank, it's where a lot of people get frustrated.

A faster, smarter alternative to the Zendesk bot builder

The headaches with manual bot builders are exactly why a new wave of AI tools has popped up. Instead of making you build fragile, step-by-step flows, modern platforms like eesel AI learn from the knowledge you already have and automate support much more intelligently.

Go live in minutes, not months

Forget spending weeks building decision trees. With eesel AI, you just connect your Zendesk account, and you're pretty much ready to go. The platform is self-serve, so you can sign up, set up your AI agent, and see it working without having to schedule a demo or talk to a sales rep.

Connects to all your knowledge, instantly

This is the biggest game-changer. eesel AI doesn't just skim your public help center. It builds a complete brain for your business by training on all your knowledge sources, no matter where they are.

  • Past Zendesk tickets: It reads through thousands of your team's past conversations to figure out customer issues, your brand's tone, and which solutions actually work.

  • Internal wikis: Connect it to your Confluence, Google Docs, Notion, and other internal docs. All that knowledge your team uses behind the scenes can finally be used to help customers.

  • Macros and canned responses: It learns from the shortcuts and templates your agents are already using every day.

Test without the guesswork

Nervous about letting an AI loose on your customers? eesel AI has a simulation mode that lets you test everything risk-free. Before you go live, you can run the AI over thousands of your past tickets. This gives you an accurate prediction of its resolution rate and shows you exactly how it would have answered real customer questions, so there are no surprises.

You're in complete control

eesel AI gives you a flexible workflow engine. You can set specific rules to decide exactly which kinds of tickets the AI should handle. You can also give it custom "actions," letting it do things like tag tickets, look up order info in Shopify, or escalate an issue to the right team. It’s a level of control that you just can't get with static, linear flows.

Common mistakes when using the Zendesk bot builder (and how to avoid them)

Whether you stick with a native builder or use a more advanced tool, a few common slip-ups can derail your efforts. Here’s how to avoid them.

  • Trying to automate everything at once.

  • Relying only on your official knowledge base.

    • The best answers are often buried in past conversations and messy internal docs. To give genuinely helpful answers, you need a tool that can tap into all those different sources and pull the knowledge together.
  • Launching blind.

    • A simple preview isn't enough. You should use a simulation tool to see how your bot performs against thousands of real customer tickets. This gives you a reliable forecast so you can launch with confidence.

Beyond the Zendesk bot builder: True AI automation for Zendesk

While using the native Zendesk bot builder to create guided flows for common issues can be a starting point, it's a manual process at its core. It puts all the work of training, building, and maintaining conversational logic on your shoulders.

Real AI automation flips that around. It comes from systems that learn from all your company knowledge automatically, let you test safely and accurately, and give you fine-tuned control without months of setup. It’s about moving beyond rigid, hand-built flows and toward reliable, large-scale automation in Zendesk.

Ready to see what a modern AI can do for your Zendesk support? Sign up and simulate eesel AI on your tickets for free.

Frequently asked questions

To begin, you'll need a Zendesk Suite Team plan or higher, administrator access to your account, and an active, well-organized Help Center. It's also crucial to have a clear list of the common issues you want to automate.

Building flows can be quite time-consuming and rigid, as each conversation path needs to be manually constructed and maintained. Expanding to many different issues can feel like a full-time job due to the manual nature of defining steps and branches.

The bot's effectiveness is heavily reliant on your Zendesk Guide articles. If your knowledge base is sparse, outdated, or poorly organized, the bot will struggle to provide accurate or helpful answers, potentially confusing customers.

If a customer asks something unexpected or diverges from the predefined flow, the bot can hit a dead end, leaving the customer frustrated. It's essential to configure a clear handoff to a human agent within your flows for such scenarios.

No, a significant limitation is that the bot primarily pulls answers only from your public Help Center articles. It cannot learn from internal documents, past customer tickets, or the unwritten knowledge held by your agents.

Zendesk offers a preview tool to click through conversations, but this provides limited insight. True performance testing involves simulating the bot against thousands of past tickets, a capability often found in more advanced AI platforms, to predict real-world resolution rates.

Share this post

Kenneth undefined

Article by

Kenneth Pangan

Writer and marketer for over ten years, Kenneth Pangan splits his time between history, politics, and art with plenty of interruptions from his dogs demanding attention.