Autoreplies with articles are automated responses to customer support requests sent via email, that include up to three recommended articles from your help center. These responses use the autoreply with articles trigger action to identify relevant articles and add them to your notification email.
This article includes the following topics:
Related articles:
Understanding the end-user experience
When you configure autoreplies with articles for email notifications, the end user receives an
automated email response to their support request. The email includes a list of recommended
articles, along with other information provided by the placeholders used in the
autoreply with articles
trigger action.
In the email, the end user can read the top suggested article in its entirety, and click any of the following options:
-
Suggested article links opens the help center article in a new tab. From there, the
user can read the article, click to see their help request, and indicate whether it helped them
answer their question:
- Request number opens the request in a new tab.
- Yes, close my request opens the article in the help center and close the help request.
- No opens a feedback screen requesting more information about why the article didn't help. This screen is optional for the end user.
- Yes, close my request on any of the suggested articles opens the article in the help center and closes the help request.
- No beneath the top article opens an optional feedback window asking for more information about why the article didn't help.
End users can return to the email and access the links as often as they like. Suggested articles are sent in the language defined in the end user's profile, when available.
Setting up autoreplies with articles for email notifications
Before you can set up autoreplies, you need a Guide help center with articles that can address your customers' questions. SeeGetting started with Guide for your help center for more information. When your help center is ready, you can turn on autoreplies in Admin Center.
To send a list of recommended articles, your email notification triggers must include the
Autoreply with articles
action. You can add this action to existing triggers,
such as the default Notify requester and CCs of received request and Notify requester of new proactive ticket. See Managing triggers.
To set up autoreplies with articles for email notifications
- In Admin Center, click Channels in the sidebar, then select AI agents and automation > AI agents.
- Click Manage AI agents for email and web form.
- Click Get started with autoreplies. If autoreplies are already activated, this option doesn't appear. You can stop at this step and create your triggers later – autoreplies with articles will not be sent until you create the trigger.
- Click Create triggers. An admin page to create a new trigger opens.
- Configure the trigger conditions for requests submitted via email. For example:
- Ticket > Ticket | Is | Created
- Requester > Role | Is | (end-user)
- Ticket > Channel | Is | Email
- Next, configure the trigger action. The action needs to include
Notify by > Autoreply with articles | (requester)
to establish that all tickets meeting the conditions will send your autoreply email to the ticket requester. The autoreply email field appears: - Fill out the email subject and body text to include in the autoreply email. Use the
placeholders listed below to customize the email text.
-
{{autoreply.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.
- {{autoreply.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.
-
{{autoreply.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 autoreply.article_count > 0 %} Here are some great articles that may help: {{autoreply.article_list}} {{autoreply.first_article_body}} {% endif %}
-
{{autoreply.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.
- In the section Configure labels and test autoreply, click Configure and test
to filter the list of help center articles offered based on labels:
- Ticket brand: 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: Enter a subject 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.
- Search articles by label (optional): Enter any article labelsyou want to use to filter the results. As you type into the tag field, available labels beginning with the same word or characters are displayed. Any articles with the selected labels are considered in autoreplies.
- Click Show suggested articles for a list of articles the user may receive if these labels are applied when submitting a similar ticket. If the results are acceptable, click Done to save the trigger. If the results are not acceptable, edit the entries and try again, or click Cancel.
- Click Create (if you're creating a new trigger) or Save (if you're updating an existing trigger).
Testing email notification results
To test autoreply results
- Create a new autoreply with articles trigger, or open an existing trigger already configured for autoreplies with articles.
- At the bottom of the Actions section on the trigger's edit page, click the Configure and test button.
- In the testing window, fill out the
following information:
- Ticket brand: 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.
- Search articles by label (optional): Enter any article labels you want to use to filter the results. As you type in the field, available labels beginning with the same word or characters are displayed. Any articles with the selected labels are considered in autoreplies.
- Click Show suggested articles to display a list of articles your user might receive in an email notification, for a ticket with the labels and ticket information applied.
- If the results are acceptable, click Done to save the trigger. If the results are not acceptable, edit the entries and try again, or click Cancel.
26 comments
Maarten Wildeman
Is there any way i can change the text of the email messages? The translation is not what i want (too formal in Dutch) and i want to make some adjustments.
0
Michael Froeming
Hi Maarten,
Yes, you can change the text of the Answer Bot's email notifications. You can create your own trigger to personalize the message. Here's a related article on Creating and managing triggers for Answer Bot.
Best,
0
Greytip Software Pvt Ltd
Does total no. of answer bot emails sent, count against your total allowed API call limit based on no. of resolutions limit in your plan?
0
Gab Guinto
Hi Vijayendra,
Answer bot notification emails per se are not counted against the no. of resolutions purchased with the plan. Only if the end user takes action (example, marks the ticket as solved after viewing the article) will it be counted against and be deducted from the available resolutions per month. You can read more on this here: How are resolutions determined?
Thanks!
1
Firstbeat Technologies Oy
Can I make the Answer bot to search and suggest articles in several brands when we have only one support email set up? For example, we have three brands, thus three Help Centers, but we have only one email address for support that helps with all the brands. Also can I set up the Answer bot to the Sandbox when I have it purchased to my main account?
0
Ahn Letran
Hi, Nelli!
You may want to create or modify existing triggers you have to provide Answer Bot suggested articles by brand. The steps are found here. Also, yes, you can apply Answer Bot on your testing environment.
Cheers!
Ahn L. | Customer Support Advocate
0
iQmetrix
The links that answer bot provides have an auth token in the url which allows users to access the articles without signing in. This link can also be shared and allows anyone to log in, as that original requester with no sign in. Can you still require sign in for answer bot suggestions and not include the embedded auth token?
0
Dave Dyson
There's a note in yellow above that states: "End users may be able to view restricted help center articles using the Answer Bot suggestion links without signing in. However, any further restricted action, such as accessing other restricted articles or viewing a profile, will require user authentication as determined by your security setup." So all the other users would be able to do is view those specific articles recommended by Answer Bot. Aside from that, there's not a way to for Answer Bot's answer to omit the authorization token.
1
iQmetrix
Thanks, that's exactly what I needed, and also shows I need to pay more attention to the notes...
1
Dave Dyson
No worries – glad I could help!
0
Fiona Witham
@... regarding that note - I'm not sure I fully understand it. Our setup means that we have some articles which are public and require no sign in to view, but then we also house internal-only articles which are marked as visible ONLY to agents and admins. Does this mean that Answer Bot may suggest and then show articles that are actually only for internal eyes?
Thanks
Fiona
1
Dane
Even though they may show internal articles, the bot suggestion is limited to what segment the user belongs to. Let's say for example you have enabled "Signed-in user" in your help center, even without signing in the end-user can still access the link the bot provided. But it's limited to articles that belong to their segment. They can't see any other articles that belongs to another user segment like "Agents and Admins".
Hope this helps!
0
Fernando Duarte
I am hoping someone has an insight on how to change the behavior of the answer bot as the experience is frustrating for some customers,
In their own words:
it appears to be sent me a help article and when I open it, a pop-up asking me if it answers my question, which I don’t know yet because I didn’t read it. If I click yes it says it will close my ticket, which I don’t want. If I click no, then it asks me why and I don’t know yet, again, because I haven’t read it yet. It blocks the article so it’s difficult to read, and if I click the X then it just goes back to the first question.
2
Jeff C
Hi Fernando,
Unfortuantely there is not a way to change this behaviour with ease as its designed in the system to be that way. I you feel this isn't working well enough, we would appreciate it if you can open a feature request on this page for product improvement.
0
LVB
Is there any documentation on how much of the inbound email is processed by Answer Bot to define the list of recommended articles?
0
Dane
You can use Explore recipe: Analyzing Answer Bot activity. More Answer bot related reports are available in our Explore Recipe for Zendesk Guide.
1
Chad Susa (Gravity CX - Zendesk Partner)
Hi All
Do I have to enable labels on articles for AnswerBot to work in the email and webform channels? In the AnswerBot testing and configuration modal it says 'optional.'
The weird thing is that AnswerBot successfully suggests articles when we search via the Widget (Classic) but not Email or Web forms.
The search criteria we are using is 'Store Locations' which is exactly the same for each channel (email - Set as the email subject and in the email body; Web Form - set as the form subject and in the body; Web Widget - search string we enter into the widget) - only in the web widget does AnswerBot successfully suggest the article.
'Store Locations' is the subject and in the first paragraph of the article.
I've confirmed that the AnswerBot enabled trigger runs on each request (email and web form) but it doesn't suggest the 'Store Locations' article.
Although I think it's a different technology, the Knowledge Capture App also successfully suggests the correct article.
And we have 498 resolutions left for this month.
I have a feeling I'm missing something but just not sure what.
Thanks
Chad
0
Beth_Borghi
Is there a way to turn off Answerbot suggestions in emails and only leave it on for webforms?
OR
Is there a way to turn off the user's ability to solve a ticket? I see this option in Knowledge Capture but not in Answerbot.
Scenario: we have a small percentage of users who are accidentally solving and closing tickets after reading suggested articles in the automated emails. They then are understandably upset because our support team hasn't replied to them (because they closed the ticket).
0
Dave Dyson
When you set up Answer Bot, you'll need to set up Triggers that tell Answer Bot when to offer article suggestions -- so you can use the Channel Is trigger condition to limit which channels Answer Bot should offer suggestions for (you'd want to create one trigger that acknowledges the incoming ticket and offers articles, and another that just acknowledges the ticket without offering suggestions). See Creating and managing triggers for Answer Bot (and Creating and managing triggers if you haven't worked with triggers before).
1
David Drysdale
Hey team, a few questions:
1) Is it possible to change the text for:
'Do any of these articles answer your question?'
'Does this articles answer your question?'
'Yes, close my request'
2) Where does the feedback go if a customer replies 'No' ?
3) Is it possible to turn off closing the ticket if the customer replies 'Yes' ? We'd like to keep tickets open as a safety net while we build confidence with Answer Bot.
0
Anne Ronalter
I can see, that you have a few questions about the Article Recommendations which I will answer here now.
1. It is not possible to change the sentences, this is due to the fact, that they are part of placeholders.
More details about this topic can be found here:
https://support.zendesk.com/hc/en-us/articles/4408825385242
2. Article recommendations can be found in Explore. Our article "Analyzing article recommendations from Answer Bot" will provide you with more details:
https://support.zendesk.com/hc/en-us/articles/4409155069466-Analyzing-article-recommendations-from-Answer-Bot
3. Natively this is not possible, but you might be able to customize something like that with Triggers to find here:
https://support.zendesk.com/hc/en-us/articles/4408894189082-Best-practices-Setting-up-Answer-Bot-triggers-views-and-workflows#h0sj62mlybt1v22j6318w7tje224ap8
0
Josh
This is such a great feature!
0
Sami
Where do we customize the icons used in the autoreply? the icons are too big.
0
Ivan Miquiabas
Thanks for reaching out!
Can you provide a screenshot of what specific icon are you referring to?
Cheers!
0
Pedro Rodrigues
Hey Zendesk team, just a suggestion: it would be great having an additional placeholder for autoreply.first_article_link. This it would allow us to edit the autoreply content in order to link to the article, especially in cases where we only send the first matching content (e.g. “It looks like this article may have the answer to your query: …”). Thanks!
0
Yvonne P.
Can anyone here confirm, when exactly the tag “ai_agent_automated_resolution” is added to tickets? As far as I understood it should be like this:
1. Requester submitts tckts, receives article suggestions > tag “ar_suggest_true” is added
2. If requester marks articles as helpful/unhelpful tags are added accordingly as well
3. ONLY if the requesters selects “Yes close my request” the tag “ai_agent_automated_resolution” should be added ?
We tested this last year already and noticed buggy behaviour, where tag “ai_agent_automated_resolution” was added, when it really should not be. Now we assumed there have been fixes etc. in that regard, so we gave it another careful test period - already have a ticket again, where the requester only viewed articles, tckt stayed open and had to be handled by a human agent - but in between the system added the tag " “ai_agent_automated_resolution” - can anyone explain to me why that happens?
Assuming towards the Automated resolutions usage - that we will eventually be charged for, all tickets marked with the tag “ai_agent_automated_resolution” will be counted?
0