
Zendesk Flow Builder is a powerful tool that lets you automate repetitive tasks and workflows, freeing up your team to focus on what matters most.
With Flow Builder, you can create custom flows that are tailored to your organization's specific needs.
These flows can be triggered by a variety of events, such as new ticket submissions or customer updates.
By automating these tasks, you can reduce the time and effort spent on manual data entry and other administrative tasks.
Flow Builder also allows you to add conditional logic to your flows, enabling you to make decisions based on specific criteria and take different actions accordingly.
Flow Builder Basics
The Flow Builder is a simple and effective tool. To use it, you need to integrate your WhatsApp account with Zendesk Support, allowing for direct interaction with customers through the world's most popular messaging app.
You can create customized service flows with the Flow Builder. This involves defining triggers and automatic responses for different types of requests.
The process of creation involves selecting predefined building blocks, such as automatic responses, multiple-choice questions, and agent routing. The Flow Builder lets you set conditions for each block, ensuring customers receive relevant responses to their questions or problems.
To get started with the Flow Builder, you need to integrate your WhatsApp account with Zendesk Support. This integration is a prerequisite for using the Flow Builder.
Adding Triggers and Actions
Adding triggers and actions to your Zendesk Flow Builder is a crucial step in creating a seamless customer experience. You can initiate an action flow with a trigger event, such as a ticket event, user event, or Slack event.
To add a trigger, open an action flow and click the + Add trigger button. Select whether you want the action flow to be initiated by a ticket event, user event, Slack event, or a custom trigger. You can also configure conditions that must be met for the action flow trigger to fire.
Here are the different types of triggers available:
- Ticket events: Including ticket lifecycle, such as creation, and ticket updates to: ticket properties, routing, comments, SLAs, schedules, and CSAT
- User events: Including user creation; updates to a user's name, role, organization, group, brand, and so on; adding or changing a profile picture; changes to a user's identity; and changes to a user's status, such as suspended or deleted
- Slack events: Including new message posted in channel, new direct message sent to a user, and new reaction added to message
- Action flow suggested by auto assist approved by agent
- Custom action flow trigger: User-defined triggers designed to listen for an HTTP request from a specific external system
Once you've added a trigger, you can add actions to your action flow. These can include Zendesk actions, external actions, branch steps, and custom actions.
Authentication Info
Using authentication info can make escalation to an Agent easier by pre-filling users' name and email.
You can even have different experiences for VIP users versus regular users, making it a great way to tailor your support to their needs.
Having logged in users assigned to a separate support tier can also help you prioritize their issues and provide more personalized support.
By leveraging authentication info, you can streamline your support process and make it more efficient for both your Agents and your users.
Adding Triggers and Actions
Adding triggers to an action flow is the first step in creating a workflow. Every action flow begins with a trigger event that initiates the flow.
You can choose from five types of trigger events: ticket events, user events, Slack events, action flow suggested by auto assist approved by agent, and custom action flow triggers.
To add a trigger, open an action flow and click the + Add trigger button in the visual workflow builder. Select the type of trigger you want to use and click through the available options to select a single action flow trigger.
For ticket events, you can configure conditions that must be met for the action flow trigger to fire. This can include ticket lifecycle events, such as creation and updates to ticket properties, routing, comments, SLAs, schedules, and CSAT.
Here are the different types of trigger events you can use:
- Ticket events: including ticket lifecycle, such as creation, and ticket updates to ticket properties, routing, comments, SLAs, schedules, and CSAT
- User events: including user creation, updates to a user's name, role, organization, group, brand, and so on
- Slack events: including new message posted in channel, new direct message sent to a user, and new reaction added to message
- Action flow suggested by auto assist approved by agent
- Custom action flow trigger: user-defined triggers designed to listen for an HTTP request from a specific external system
Once you've added a trigger, you can start adding actions to your action flow. There are several types of actions you can add, including Zendesk actions, external actions, branch steps, and custom actions.
To add an action, open an action flow and click the Add step icon in the action builder. Select the type of action you want to add and enter the required inputs for the selected action.
Here are the different types of actions you can add:
- Zendesk actions: perform Zendesk-specific tasks, such as modifying a ticket's priority
- External actions: perform tasks specific to the connected system, such as sending a Slack message or creating a Jira issue
- Branch steps: allow you to create a decision point in your action flow
- Custom actions: user-defined steps that update data using any API the user specified
Flow Builder Features
The Flow Builder is a game-changer for Zendesk users. It allows you to integrate your WhatsApp account with Zendesk Support, enabling direct interaction with customers through the world's most popular messaging app.
To create custom support flows, you can select pre-defined building blocks, such as automated responses, multiple-choice questions, and agent handovers. You can define conditions for each block to ensure customers receive relevant responses.
The Flow Builder also lets you define triggers and automated responses for different types of requests. This means you can set up custom flows that cater to specific customer needs.
Here are some key features of the Flow Builder:
- Zendesk actions
- External actions
- Branch steps
- Adding Send outputs to copilot steps
- Custom actions
With the Flow Builder, you can add actions to your action flows to create a seamless customer experience.
Optimizing and Analyzing
With Zendesk Flow Builder, you can identify bottlenecks and areas for improvement in customer service through the metrics and analyses provided.
You can collect data and use it to optimize your customer service flows, ensuring a continuous process of improvement.
The Flow Builder's metrics and analyses help you pinpoint where to focus your efforts for the greatest impact.
Showing The Status
Showing the status is crucial in optimizing and analyzing your system's performance. It gives you a clear picture of what's working and what's not.
To show the status to your customers, you need to edit the text to include a variable that updates automatically. Under the Success option, select the "[This will be the API step]" message and edit the text to say "Our current status is: ". Then, click the "Select Variable" button and choose the recently created system_status option.
The text should now say "Our current status is: {{system_status}}". This is a simple yet effective way to keep your customers informed about the status of your system.
Readers also liked: Zendesk Customers

Similarly, under the Fail option, you need to add a text block that handles the scenario where you can't retrieve the status. This will provide a clear explanation to your customers when things go wrong.
Here's a step-by-step guide to editing the text:
- Under the Success option, edit the text to say "Our current status is: ".
- Click the "Select Variable" button and choose the recently created system_status option.
- The text should now say "Our current status is: {{system_status}}".
- Under the Fail option, add a text block that handles the scenario where you can't retrieve the status.
Analysis and Optimization
Analysis and Optimization is a crucial step in the optimization process. By leveraging the metrics and analyses provided by the Flow Builder, you can identify bottlenecks and opportunities for improvement in customer service.
This allows you to optimize the service flows, ensuring a continuous process of improvement. With the data collected, you can streamline the service process, making it more efficient and effective.
Automating routine tasks and repetitive tasks frees up the support team to focus on more complex and strategic issues. The Flow Builder speeds up the service process, providing quick and accurate responses to customer inquiries, resulting in increased team productivity and satisfaction.
Benefits and Examples
By incorporating the Zendesk Flow Builder into your customer service strategy, your company can enjoy numerous benefits.
One of the main advantages is the ability to provide personalized automated responses, which can help customers quickly find the information they need.
Automated satisfaction surveys can also be set up to collect feedback from customers, allowing you to identify areas for improvement.
A well-designed flow can also help direct customers to the right agent, ensuring their issue is handled efficiently.
The Flow Builder can be used to create a streamlined process for common problems, freeing up agents to focus on more complex issues.
Here are some examples of how the Flow Builder can be used to improve customer service:
- Personalized automated responses
- Automated satisfaction surveys
- Flows for common problems
- Agent routing
Conclusion
Building a Flow Builder Bot can be a complex process, especially when dealing with multiple intents.
A simple Flow Chart can quickly turn into a tree of over a hundred steps, as seen in the example that ended up with links to Help Center articles and external APIs.
This complexity can be overwhelming, but with the right guidance, you can build a bot that meets your needs.
The author of the documentation in the article hopes that their video and documentation will help you avoid the same issues they encountered.
Featured Images: pexels.com


