The problem
Support backlogs are mostly noise, and every department downstream of support pays a different tax for it. Genuine P1s get buried under duplicate reports and tickets that belong to a different team — that’s the support team’s pain. Engineering’s bug-triage rotation re-classifies the same ticket because they don’t trust support’s tags. Product spends Monday mornings hand-counting “what are the top three things customers are complaining about this week?” Marketing has no reliable way to surface a customer quote candidate for a case study. The information is right there in the ticket stream — it just isn’t classified once and shaped for everyone.
Author
The customer success lead writes the triage agent in the AgentBundle dashboard wizard — no code. They paste in the team’s classification taxonomy (bug / feature / question / duplicate), the severity rubric, the ownership map (which team owns which surface), and the customer-quote heuristic (“five-star resolution + opt-in for outreach”). They wire MCP connections to Zendesk (or Intercom, Front, whichever support tool the org uses) so the agent reads incoming tickets, and to Linear so it can dedupe against existing issues. The wizard generates the bundle; nobody on the success team needs to know what a bundle is. The reviewer-workflow controls referenced below ship on Business tier and above; see /pricing for what’s gated.
Review
The customer success manager approves the agent before it can publish. The classification taxonomy directly determines routing — a wrong label sends a ticket to the wrong team — so the approval gate matters. Every change to the classification rules is logged in the audit trail with the CSM’s signoff.
Distribute
APM (Microsoft’s open packaging spec for AI agents) ships the agent across every runtime the org uses — Claude Code and Cursor for support engineers and product, the ChatGPT-equivalent web client for sales and marketing, and the AgentBundle dashboard for customer-success leads who don’t want to leave their browser. Same canonical agent, different surfaces. Each install loads the MCP connections the customer-success lead wired in (Zendesk for ticket lookup, Linear for dedupe) so the agent can read the right context when a human invokes it.
Use
The same canonical agent, four different consumer flows. Every flow is a human pasting a ticket (or a batch of tickets) into the agent and getting back a structured response:
- The support team pastes a new ticket into the agent and gets back: classification (bug / question / feature / duplicate), severity, suggested owner team, dedupe match against open Linear issues, and a draft response template aligned to the org’s tone. The support engineer accepts the classification or corrects it, fixes the routing if wrong, and resolves the ticket. The agent does not auto-route — it gives the engineer a strong starting point so the queue moves faster.
- An engineering manager runs the agent on a batch of the morning’s classified-bug tickets to triage them in bulk. Output: severity ranking, dedupe match against open issues, related-issue links pre-attached. The manager escalates the P1s, closes the dupes, and assigns the rest. No more re-classifying tickets the support team already labeled.
- The PM for billing-portal pastes a week’s worth of tickets touching their surface into the agent and gets back themed pain points with sentiment and ticket counts. Monday-morning planning starts with “here are the three things customers said about your surface this week” instead of “let me skim the Zendesk queue for a sense.”
- The case-study lead in marketing pastes opt-in resolved tickets into the agent and gets back candidate quotes — the customer’s actual words, the support engineer who resolved the ticket, the original ticket link. They pick from a real, current pool instead of asking around in Slack.
Four departments. Four different invocation flows. One agent definition.
Iterate
The product team launches a new surface — say, billing-portal v2. The customer-success lead extends the canonical taxonomy in the agent prompt to cover it, adds the new ownership entry, and re-publishes. v2 of the agent rolls out on next sync. Every team’s next invocation picks up the new taxonomy — support sees the new surface in the routing options, engineering recognizes the new bug bucket, the PM finds it in the pain-point themes, marketing’s quote pool segments by it. One change, one re-publish, four teams’ next-invocation behavior updated — none of whom had to be told about it.