Once you’ve enabled Answer Bot, you can create triggers to direct Answer Bot to send results to your end users, and update existing triggers to do the same. Trigger conditions determine when Answer Bot suggestions are sent to an end user, and trigger actions determine what information in included in the email response.
This article discusses the following topics:
Related articles:
- Using Answer Bot in email notifications
- Best practices: Setting up Answer Bot triggers, views, and workflows
- Answer Bot resources
You can also view the following video tutorial:
Creating new triggers for Answer Bot
If you're creating a new trigger, make sure you're familiar with the process. See Creating and managing triggers for information.
To create a trigger that includes Answer Bot
- Click the Admin icon (
) in the sidebar, then select Business Rules > Triggers.
- Click Add trigger.
- Create the trigger conditions. For example, you may want to have Answer Bot send an email with suggested articles to an end user as soon as they submit a help request, but only from a mobile device. That trigger would include the following conditions:
- Ticket | Is | Created
AND
- Requester: Role | Is | (end user)
AND
- Ticket: Status | Is | New
AND
- Ticket: Channel | Is | Mobile
- Ticket | Is | Created
- Next, configure the trigger to perform the following action:
- Notifications: Answer Bot | (requester)
This establishes that all tickets that meet the above conditions will send your Answer Bot email (see below) to the ticket requester.
- Notifications: Answer Bot | (requester)
- When you select Answer Bot from the Actions drop-down, the Answer Bot email field appears:
- Fill out the subject and body text you want to include in the Answer Bot email. Use the following placeholders to customize the email text. You can also click View available placeholders to view and copy placeholder text:
-
{{answer_bot.article_list}}
Required. You must include this placeholder for the feature to work. This placeholder adds a list of up to three articles that best match the request, links to those articles, and inserts buttons the end user can use to choose which article solved the request.
Note: This placeholder includes two pieces of text that are determined by the user's profile language: The header Do any of these articles answer your question?, and the two buttons located underneath each suggested article Yes, close my request and View article. -
{{answer_bot.first_article_body}}
Optional. This placeholder renders the first matching article (full HTML) into the email body, allowing end users to read the article and solve their problem without needing to leave the email experience.
-
{{answer_bot.article_count}}
Optional. This placeholder allows you to create an optional condition to send different body copy to customers based on how many articles are returned, for example:
{% if answer_bot.article_count > 0 %} Here are some great articles that may help: {{answer_bot.article_list}} {{answer_bot.first_article_body}} {% endif %}
Note: Answer Bot is not compatible with the{{header}}
placeholder, which is an unsupported and deprecated placeholder that some customers may still be using in their HTML Email Template. The HTML Email Template can be found here: Admin > Channels > Email > Email Templates > HTML templateWhile this placeholder currently functions with standard email notifications, it produces a malformed header in Answer Bot Notifications. To resolve the issue, remove this{{header}}
placeholder from the Zendesk HTML Email Template. To replicate the look and feel of this placeholder, you can add the following code (with appropriate styling added as desired) to the Email Body section of your account's Notify Requester triggers.<a href="{{ticket.link}}">Ticket #{{ticket.id}}: {{ticket.title}}</a>
-
{{answer_bot.article_list}}
- In the section Configure article labels and test Answer Bot, click Configure and test to filter the list of offered Help Center articles based on labels:
- Ticket brand: Use the drop-down to select a brand to run the test on. The brand selected here is purely for testing purposes, and will not be added to the trigger you are creating.
- Ticket subject: This field is used to test the articles returned when a ticket is filed with this subject.
- Ticket description: Enter a short description of seven or more words, written from the ticket submitter's perspective.
- Article restrictions by label: Enter labels you want to use to filter the articles. As you type into the tag field, autocomplete displays available labels beginning with the same word or characters. Any articles with any of these labels will be used as potential Answer Bot articles.
- Click Show suggested answers for a list of articles the user may receive if these labels are applied when submitting a similar ticket. If you approve, click Apply labels; if you don't, edit the entries and try again, or click Cancel.
- Click Submit.
The new trigger appears in the list on the triggers page, as well as on the Answer Bot admin page.
Converting an existing trigger for Answer Bot
If you're editing triggers, make sure you're familiar with the process. See Creating and managing triggers for information.
To convert an existing trigger for Answer Bot
- Click the Admin icon (
) in the sidebar, then select Business Rules > Answer Bot.
- Find the trigger you'd like to convert from the Recommended triggers list. . If your trigger is not listed there, it likely doesn’t meet the essential conditions needed for Answer Bot triggers.
- When you've found the trigger you want to convert, click the Edit button. The trigger's edit page opens.
- In the triggers Actions section, click the Convert to Answer Bot button.
This updates the trigger, including adding the Answer Bot placeholders into the email body.
- Edit the email as needed, and click Save. The trigger now includes Answer Bot functionality.
72 Comments
I have noticed that recently "Convert to Answer Bot" option isn't displayed for the default triggers for new Zendesk instances. Is this because of the CC inclusion of recent? Most customers are "good to go" with the defaults of this conversion action, so ideally it would continue to be available for new trials/implementations. Otherwise, us freelancers need to start telling customers they will need to pay for the additional time required.
I am not saying it takes that much effort to create the triggers manually = ) But, the convenience of the conversion is desirable.
Any help is appreciated, David.
Thanks for raising this David. That's correct, there is a bug in the system that is causing the 'Convert to Answer Bot Trigger' button to disappear. We have fix on the way and the button should reappear in the next few days. Thanks
I'm not sure if this is mentioned anywhere, but what's the best practice for not sending the default auto-acknowledgment trigger we send for every new ticket? I don't want customers to receive two auto-responses and prefer to send just one.
Hi Allen Lai
I'm not sure I understand your question exactly so let me know if I'm off base here. It sounds like you currently have two triggers, one that auto-replies to tickets (such as the "notify requester of received request" trigger) and another that sends an auto-reply WITH an answer bot answer. You want to make sure your customers only receive one or the other, not both?
If that is the case, yes! You can easily make sure that one does not fire if the other has.
First I want to make a note that the strategy described in this article has you transform/convert an existing trigger (such as the "notify requester of received request" trigger) into an answer bot trigger. So you would not end up with two different triggers, just one that is now active for answer bot. So you wouldn't need to worry about two different duplicate triggers firing. But! If you have a workflow that uses two different triggers anyway, read on :)
To make sure only one or the other trigger fires on a ticket, simply have each of the two triggers add a unique tag to the ticket, and set a condition on each to not fire if the other trigger's unique tag is present.
For example, on Trigger One add the action "Add tags auto_response_sent" and on Trigger Two add the action "Add tags answer_bot_answer_sent". Then in Trigger One add the condition "Tags contains none of the following answer_bot_answer_sent" and on Trigger Two add the condition "Tags contains none of the following auto_response_sent".
Now, each trigger will add a tag when they fire on a ticket and send a message to your customer. And each trigger will NOT fire if the other trigger's tag is present on the ticket (indicating the other trigger already sent the customer a message).
I hope that helps! Let me know if you had further questions!
How are email scanning tools handled with Answer Bot? We have a lot of customers who utilize tools like Proofpoint or FireEye. We had to change our CSAT from including the good/bad options within the email itself, to giving them the URL to rate there because we were getting false responses. With implementing the Answer Bot, that's a concern of ours as well- we'd receive false resolutions.
Thanks!
Hey Karen,
I confirmed with our Answer-bot team and this shouldn't be an issue. Even if email scanning tools are clicking and opening the Answer Bot suggested links, you still need to follow up and confirm that you want to close the case when you get to the help center.
Let me know if you have any other questions!
Thanks Brett! So, we would be required to have the ticket portal in place in order to have email notification answer bot enabled? We do not yet have the ticket portal set up; all tickets are submitted and responded to via email. Thanks!
Hey Karen,
You shouldn't need to have the customer portal enabled for users. They would only need to have access to your Help Center to view the content.
Cheers!
I'm not sure why, but the answer bot, displays null at email:
And it works perfectly and Zendesk:





My trigger:
I hope someone can help me, because I need the articles on email, and this isn't working :/
Best regards, Leonardo
Hi Leonardo,
Did you receive an email at all? Or no email?
Could you share a screenshot of the events on the first comment, so we can verify?
I believe it might either have something to do with trigger conditions or the warning icon in the top right of the first comment.
My Spanish is perfect, but it looks like you are trying to send an email when a [ ticket status ] [ is ] [ new ]
I would recommend to change that to [ ticket ] [ is ] [ created ]. If you set it up like that you have to create less triggers, and the conditions are more event driven.
Hi Kay,




No email...
Sure!
The warning is, "The user Leonardo Jesus, was not connected at the moment when the comment was sent"
But Ticket Is New, is not equal to Created?
Hey Leonardo,
Looks like you haven't received a response on this! Are you still experiencing issues with answer-bot not functioning properly? I'm happy to create a ticket on your behalf to troubleshoot further.
Cheers!
Please sign in to leave a comment.