Ticket triage
Acknowledge every support ticket at once, sort it by topic and urgency, page someone for the urgent ones, and tell the team.
A ticket queue is first-in, first-out by default, so severity is invisible until someone opens each one; a customer who is stopped waits as long as one with a question. Sorting and acknowledging on arrival tells the customer they were heard and puts the urgent ones on a phone.
How it works
A new ticket in the client’s Zendesk starts it within seconds, because Zendesk reports each ticket as it is opened. The subject and description go to an AI step on the client’s Anthropic key, and it answers on two lines, one topic from the Topics field and then URGENT or ROUTINE. Urgent means the customer is stopped, losing money or data, or angry.
Before anything else happens, the ticket gets a comment acknowledging it, saying the request is with the right person and adding the sentence from When a person replies (“We answer within one working day”). The customer knows they were heard within seconds of writing.
A branch then reads the second line. An urgent ticket sends a text with its number and subject to the Owner’s mobile, whoever is on call. Every ticket, urgent or routine, is posted to the team’s Slack channel with its number, topic and subject.
Six fields set it up, and the Zendesk token has to come from an admin, since the trigger makes a webhook. Topics should be the team’s own short list (billing, bug, how-to, account), because the AI picks only from it.
The steps, as written for B2B software (SaaS)
- Starts whenA ticket is opened
- AgentSort the ticket
- Zendesk: Update a ticketAcknowledge it
- BranchUrgent?
- IfIf yes
- TextText whoever is on call
- IfIf no
- App stepPost to the team
What changes in each trade
| Trade | What differs | Starts | Apps |
|---|---|---|---|
| B2B software (SaaS) | Software companies find it in the Product-led software company pack, together with Conversation triage for the chat inbox, and its ticket topic examples are written for software support. | From Zendesk, within seconds | |
| E-commerce | Two store packs include it, Dropshipping store and Subscription store, and its Topics can follow the store’s service form, from missing orders and damage to returns and product questions. | From Zendesk, within seconds | |
| Marketing agency | A marketing agency installs it separately, and nothing in the steps or fields changes, so it suits an agency that runs a Zendesk help desk for its own clients. | From Zendesk, within seconds | |
| Software development agency | The Retainer dev agency pack opens with it, since response times per severity are what a monthly support client pays for, and its URGENT rule (stopped, or losing money or data) marks the tickets that need the fastest answer. | From Zendesk, within seconds |
Install it for a trade
Each version installs into the client you choose, switched off, with a checklist of the accounts to connect and the details to fill in.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.