Zendesk (Tagging + Sentiment)
Automatically tag your tickets and conversations in Zendesk with custom tags and sentiment scores.
Last updated
Automatically tag your tickets and conversations in Zendesk with custom tags and sentiment scores.
Last updated
It can take hours of repetitive work to tag and categorize your support tickets and conversations each month.
But now your AI agent can automatically do this classification and categorization for you, directly in Zendesk, accurately and consistently, so you can focus on understanding what your customers are asking and how they are feeling.
You can find the tagging app in the Zendesk Marketplace here.
To set up your automated ticket or conversation tagging or sentiment scoring in Zendesk please get in touch with us via our live chat and we will assist you with the set-up.
It costs $0.10 to tag and score each conversation within Zendesk, this will be an add-on to your existing subscription and charged at the end of each billing period.
We also offer volume discounts, get in touch with us via our live chat to learn more.
You can use your own custom tagging, categories, reason codes or groupings when tagging your Zendesk tickets or conversations.
The tagging will be captured in up to 2 Zendesk custom fields you define, for each conversation or ticket, or within the ‘Tags’ field if you don’t use custom fields.
You can use Zendesk Explore to interrogate and report on your tags and sentiment scores to see which and how they are changing over time.
We would recommend using fewer than 200 tags.
If you are using Zendesk Tickets you can use our Ticket tagging product to tell the AI agent which tickets it should respond to.
For example, you might have "reason for contact" field in Zendesk that your agents update today, and there might be 10 category options within that.
If "unsubscribe" was the tag added by our AI agent, and that tag was on your block list, then the AI wouldn't reply to it.
Alternatively, you could set up a triage flow for your AI agent, using rules or triggers within Zendesk for where certain tickets should be routed depending on the "reason for contact".
