Add-on | Copilot |
Intelligent triage uses artificial intelligence (AI) to enrich your Support and messaging tickets with actionable information without the help of agents or admins. Specifically, intelligent triage predicts the intent, customer sentiment, and language for new tickets. You can then use this information to automate workflows with triggers and automations, set up views for teams, create reports, and more.
This article contains the following topics:
Related articles:
Understanding intelligent triage
When you enable intelligent triage, the system adds new fields to your tickets:
- Intent: A prediction of what the ticket is about. To see the possible values, open the Intents page in Admin Center.
- Intent confidence: How likely it is that the intent prediction is correct. Possible values are High, Medium, and Low.
- Language: A prediction of what language the ticket is written in. To see the possible values, open the Language page in Admin Center.
- Language confidence: How likely it is that the language prediction is correct. Possible values are High, Medium, and Low.
- Sentiment: A prediction of how the customer feels about their request. Possible values are Very Positive, Positive, Neutral, Negative, and Very Negative.
- Sentiment confidence: How likely it is that the sentiment prediction is correct. Possible values are High, Medium, and Low.
These fields are populated via ticket updates by Zendesk’s machine learning model based on the content of the first message of a ticket when it’s submitted. Agents can update the field values if necessary.
When the fields are populated, tags are also automatically added to the ticket to help you build triggers, automations, and reporting. These tags reflect the values in the Intent, Language, and Sentiment fields, and are structured as follows:
- intent__value of Intent field
- language__value of Language field
- sentiment__value of Sentiment field
Understanding intent, language, and sentiment values
Intent
For the Intent field, intelligent triage is trained to identify intents. Additionally, intent and sentiment detection works only for the following languages:
|
|
|
The Zendesk Intent Model includes intents for all of the supported industries. An account with this model has access to relevant intents and use cases based on their ticket conversation data. This model allows us to support accounts with multiple brands, mixed use cases, and industries that cross over between our currently supported industries.
Language
For the Language field, intelligent triage can detect approximately 150 different languages. See Zendesk language support by product.
Sentiment
The Sentiment field is a prediction of how positive or negative a customer feels about the request they’re submitting. The prediction is made based on the text of the first message in the ticket. If configured to do so, the sentiment is updated every time the end user replies.
Sentiment is grouped into one of the following categories:
- Very positive: The message likely contains strong positive words (like “brilliant” or “perfect”), positive words modified by intensity adverbs, or multiple positive sentences.
- Positive: The message likely contains phrases expressing gratitude, or one to two positive sentences.
- Neutral: The message likely contains factual statements without additional negative quantifiers (like “any” or “always”), or a mix of positive and negative statements.
- Negative: The message likely contains phrases expressing frustration, complaints containing negative words, or repetition of the same dissatisfaction.
- Very negative: The message likely contains strong negative words, capitalized text, multiple exclamation marks, or multiple negative phrases.
Intelligent triage is specifically calibrated for customer service. This means that a ticket isn’t assigned a negative sentiment just because a customer has an issue with their order, can’t find the information they need, or some other similar “negative” situation. Instead, the model is tuned to analyze sentiment with the assumption that the customer is contacting customer service because they have an issue that needs to be addressed.
Turning on and configuring intelligent triage
Admins can turn on intelligent triage in Admin Center. By default, this feature is turned on.
Intelligent triage adds predictions to tickets that were created only after it was turned on. For other reasons you might not see predictions on tickets, see Why didn't intelligent triage add predictions to a ticket?
To configure Entity detection, see Automatically detecting unique information in tickets.
To turn on and configure intelligent triage
- Go to the page for the prediction type you want to configure:
- In Admin Center, click
AI in the sidebar, then select Intelligent triage > Intent.
- In Admin Center, click
AI in the sidebar, then select Intelligent triage > Sentiment.
- In Admin Center, click
AI in the sidebar, then select Intelligent triage > Language.
The status of the Intent, Language, and Sentiment prediction types is on by default.
- In Admin Center, click
- On the prediction type's page, deselect the Detect <prediction type> checkbox if you don't want the system to automatically enrich tickets with that prediction type.
- On the prediction type's page, click Manage Settings.
- Choose from the following options:
- (Sentiment and Intent only) Dynamic detection: Select the checkbox to update the sentiment or intent based on the latest end user message in the conversation.
-
Channels: Select the email channels you want to turn on.
The Web form, Email, and Web service (API) channels are turned on by default.
You can also turn on the Text, Web Widget, Mobile SDK, Mobile, Facebook Post, X Corp, and Social Messaging channels. (If you create tickets via channel integrations, select Social Messaging.)
Zendesk generally doesn't recommend turning on additional channels, though you may want to turn them on if you have high ticket volume on those channels. Channels with more conversational messages, system notifications, or spam will have lower-confidence predictions. -
Messaging channels: Select the messaging channels you want to turn on.
The Web Widget, WhatsApp, and Facebook Messenger channels are turned on by default.
You can also turn on the Android SDK, Google RCS, Instagram DM, iOS SDK, LINE, Slack, Telegram, Twilio SMS, X Corp DM, Viber, WeChat, Apple Business Chat, Google Business Messages, KakaoTalk, MessageBird SMS, Native Messaging, and Sunshine Conversations API channels.
Note: Turning on any one of the Web Widget, iOS SDK, Android SDK, or Native Messaging channels automatically turns on all four channels together. -
Exclusion conditions: To exclude tickets created by agents from being enriched with the prediction type, select the Ignore agent-initiated tickets checkbox.
When this checkbox is selected, suspended tickets that are recovered are not enriched with intelligent triage predictions
- (Sentiment and Intent only) Dynamic detection: Select the checkbox to update the sentiment or intent based on the latest end user message in the conversation.
- Click Save.
Note: If you use any third-party tools to make automated updates to your tickets, make sure those tools are configured to use the
safe_update
property so that intelligent triage ticket fields aren’t inadvertently overwritten. See Protecting against ticket update collisions.
Displaying prediction types in the ticket header
For the Intent and Sentiment prediction types, you can configure if the context or sentiment that's detected is displayed in the ticket header of the conversation.
See Viewing intelligent triage predictions to learn about the agent experience.
- In Admin Center, click
AI in the sidebar, then select Agent copilot > Auto assist.
- Scroll down to the Ticket context section.
- Select the Show intent in the header checkbox to display the context that's been detected in the conversation.
- Select the Show sentiment in the header checkbox to display the sentiment detected in the conversation.
If you've turned on Dynamic detection for Sentiment, the sentiment will update in the header based on the latest reply from the end user.
- Click Save.
25 comments
BAKO
Hello;
A large portion of our users are starting their conversation with the bot by requesting a transfer to an agent. So their first message is usually "Live support" or "Talk to human"
This is fine for us, but the Intent for these tickets is settled on "Transfer to agent" and doesn't change.
We know agents can change the intent, however, If the zendesk would let me check the intent form a custom ticket field for example, I can prompt users to ask their issue with a "Ask fo detail" step in the bot and then form the intent over that.
This would allow me to automatically categorize every ticket.
Currently, we can delete an intent using triggers btw. We just need a reverse version of that so the ticket can re-evaluated when it has some context.
0
Jake Bantz
Håvard Skare,
This article is super helpful in tracking down why a ticket was not enriched by intelligent triage: Why didn’t intelligent triage add predictions to a ticket?
Can you please see if that helps to explain the behavior you're seeing? If you don't find your answer there, please feel free to reach out to our Support Engineers as Cheeny mentioned above, and they can help you out.
1
Cheeny Aban
If all the requirements to use intelligence are met and it is still not working on your tickets, I would suggest that you initiate a conversation with us so one of our Engineers will be able to take a closer look into your account.
1
Håvard Skare
Hi.
The intelligence function is still unavailable, even though it is enabled in the settings. Any thoughts on why? (Language: norwegian)
0
Allen Lai | Head of CX at Otter.ai
Thanks, Tony! The use of merging intents is helpful because several intents are very similar. Creating various triggers, automation, views, etc., to include every variation of the same intent is not efficient or effective, so being able to merge them would be helpful.
2
Tony
I'm not too sure about merging multiple intents together. But in the meantime, thank you very much for your feedback. Your feedback helps us grow – so we appreciate taking some time for sharing it with us.
Best,
0
Allen Lai | Head of CX at Otter.ai
It's a great start, but it needs a lot of improvements.
3
Susana
Hello,
Currently the Intent field is not user friendly, there are too many options to choose from and not the possibility to easily search within the available ones. Perhaps a "start typing" feature could be added where the Intent field would show the matching options. Example: If I type "Missing", the field would show me all available options that include the word "Missing". This would make our job much easier in case we need to change the AI pre selected Intent.
Thanks!
4
Erin O'Callaghan
Hi Thomas, I've updated the article to say "Suite Professional and above" to align with the header.
0
Gabriel Manlapig
La clasificación inteligente está actualmente disponible como parte de un programa de acceso anticipado (EAP). Consulte Requisitos para usar la clasificación inteligente.
Puede registrarse para el programa EAP de clasificación inteligente aquí. Si no cumple los requisitos actuales, regístrese de todas formas para ser incluido en la lista de espera.
0
Sign in to leave a comment.