Support 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.

RouterHuman approvalRuns in Slack bot, Email, Claude Code

Running it here

1 step needs a connector (slack). Run here, those steps are skipped or shown to copy, and the rest still runs. In your own agent with those tools connected, every step runs. Runs here start by hand; to start it from slack, run it in your agent or automation tool.

  1. TriggerNew message in #supportRuns on a new support message ({{ticket}}). Paste one to try it.→ slack · manual start here
  2. RouterClassify the ticketRead the customer's message ({{ticket}}) and pick the route that fits best. If it fits two, pick the one with money involved.
    • BillingLook up the customer's invoices and explain the charge. Never promise a refund; offer to escalate.
    • BugAsk for steps, browser and a screenshot. Create a GitHub issue with what you know.
    • How-toAnswer from {{docs_url}} only. Link the page you used.
  3. AgentDraft the replyWrite a reply to {{ticket}} as {{product}} support, using {{route}}: friendly, under 120 words, one clear next step per issue. Never promise refunds or dates.
  4. ApprovalAgent approvesPost {{reply}} to the support lead with Approve / Edit / Reject buttons.→ slack · shown here to copy
  5. OutputReply in threadSend the approved reply in the original thread and tag the ticket.→ slack · shown here to copy

Good for

Small support teams that want each ticket sorted and a reply drafted, with a person approving every reply before it goes out.

Last reviewed

Install as a skill

The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “Support triage bot”.

Get the support-ticket-triage-bot skill

What each step does

  1. 1. New message in #support (Trigger)

    Runs on a new support message ({{ticket}}). Paste one to try it.

  2. 2. Classify the ticket (Router)

    Read the customer's message ({{ticket}}) and pick the route that fits best. If it fits two, pick the one with money involved.

    • 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. 3. Draft the reply (Agent)

    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.

  4. 4. Agent approves (Approval)

    Post {{reply}} to the support lead with Approve / Edit / Reject buttons.

  5. 5. Reply in thread (Output)

    Send the approved reply in the original thread and tag the ticket.

Use it in your own agent

Fill in the inputs
Open in ClaudeOpen in ChatGPT3 inputs use their example until you fill them in.

Save as .claude/skills/support-ticket-triage-bot/SKILL.md for Claude Code, or .agents/skills/support-ticket-triage-bot/SKILL.md for Codex and other Agent Skills tools. Then ask: “run the Support triage bot workflow”.

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.

Want different steps? Open it in the workflow builder.