Skill · Workflow
support-ticket-triage-bot
Reads each new ticket, routes it to billing, bug or how-to, drafts a reply and waits for an agent to approve before sending. Use when asked to run the "Support triage bot" workflow.
The skill itself. Agents read the name and description first and load the rest only when a task matches.
support-ticket-triage-bot/SKILL.md
---
name: support-ticket-triage-bot
description: Reads each new ticket, routes it to billing, bug or how-to, drafts a reply and waits for an agent to approve before sending. Use when asked to run the "Support triage bot" workflow.
---
# Support triage bot
Reads each new ticket, routes it to billing, bug or how-to, drafts a reply and waits for an agent to approve before sending.
## Inputs
Ask for any of these that the user hasn't given:
- `ticket` (e.g. "I was charged twice for October and the export button does nothing.")
- `product` (e.g. "Acme Invoicing")
- `docs_url` (e.g. "https://docs.acme.test")
## Steps
Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.
1. **New message in #support** — Start: Runs on a new support message ({{ticket}}). Paste one to try it.
2. **Classify the ticket** — Read the customer's message ({{ticket}}) and pick the route that fits best. If it fits two, pick the one with money involved. Pick one route: Save the result as `route`.
- **Billing**: Look up the customer's invoices and explain the charge. Never promise a refund; offer to escalate.
- **Bug**: Ask for steps, browser and a screenshot. Create a GitHub issue with what you know.
- **How-to**: Answer from {{docs_url}} only. Link the page you used.
3. **Draft the reply** — Write a reply to {{ticket}} as {{product}} support, using {{route}}: friendly, under 120 words, one clear next step per issue. Never promise refunds or dates. Save the result as `reply`.
4. **Agent approves** — STOP and ask the user to approve before continuing: Post {{reply}} to the support lead with Approve / Edit / Reject buttons.
5. **Reply in thread** — Finish: Send the approved reply in the original thread and tag the ticket.
## Done when
Every step has run, each approval was given, and you've reported what was produced and where it was saved.