Tickets land in one queue and a person sorts them by hand, guessing at urgency and missing that the unhappy customer from last week is back again. Priorities get set by who shouts loudest, not who is actually at risk.
sonnet4 daysZendeskOpenAISlack
Claude
79ROI
90Scale
$3k94Saved
ROI for
README.md
Why this subagent
Tickets land in one queue and a person sorts them by hand, guessing at urgency and missing that the unhappy customer from last week is back again. Priorities get set by who shouts loudest, not who is actually at risk.
This agent reads each ticket, weighs intent and urgency against the account's CSAT history, and routes it to the right queue at the right priority. An at-risk customer jumps the line automatically. The team works a queue that is already sorted by what matters instead of by arrival order.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Tag intent, urgency, and product area, and check past CSAT for this account.
pending
Route the ticket to the right queue and set priority, escalating angry or at-risk customers.
pending
Apply the tags in Zendesk and notify the assigned team when priority is high.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
For a ticket, return intent, urgency, target queue, and priority, raising priority when the account has low recent CSAT.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.