Support triage bot: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

Reads each new ticket, routes it to billing, bug or how-to, drafts a reply and waits for an agent to approve before sending.

Prompt

Installs to .agents/skills/support-triage-bot-multi-step-agent-workflow-for-claude-code-cod/

mkdir -p .agents/skills/support-triage-bot-multi-step-agent-workflow-for-claude-code-cod && curl -sL "https://prompts-gpt.com/prompts/support-triage-bot-multi-step-agent-workflow-for-claude-code-codex-or-chatgpt/raw" -o .agents/skills/support-triage-bot-multi-step-agent-workflow-for-claude-code-cod/SKILL.md
SKILL.md
Preview
---
name: support-triage-bot-multi-step-agent-workflow-for-claude-code-cod
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."
---

# Support triage bot: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

Reads each new ticket, routes it to billing, bug or how-to, drafts a reply and waits for an agent to approve before sending.

## Prompt

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

## Usage Notes

Run it in Claude Code or Codex: save as .claude/skills/support-ticket-triage-bot/SKILL.md (or .agents/skills/ for Codex) and say "run the Support triage bot workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: ticket, product, docs_url. Build or run it step by step at prompts-gpt.com/workflows/support-ticket-triage-bot.

Example output

At a glanceSupport triage run for ticket #4182Workflow pauses at approval; nothing is sent until the lead responds.
  1. New message in #supportStep 1Dana reports a $49 double charge and a broken CSV export
  2. Classify the ticketStep 2Routed to Billing; bug logged as GitHub issue #771
  3. Draft the replyStep 394 words, one next step per issue, no refund promised
  4. Agent approvesStep 4Waiting on @marcus.liu to Approve, Edit or Reject
  5. Reply in threadStep 5Pending: send in #support and tag the ticket

Example for: ticket from "Dana Whitfield" in #support, product "Ledgerly Invoicing", docs_url "https://docs.ledgerly.test".

Support triage bot: run log

Step 1: New message in #support

Ticket #4182 (Dana Whitfield, Brightway Studio, Pro plan)

"Hi, I was charged $49 twice on Oct 3 for my October subscription. Also, the 'Export to CSV' button on the Reports page doesn't do anything when I click it. Can you help?"

Step 2: Classify the ticket

The ticket covers two issues: a duplicate charge and a broken export button. It fits both Billing and Bug. The rule says to pick the route with money involved.

route = Billing (with a secondary bug note)

Billing lookup:

InvoiceDateAmountStatus
INV-20931Oct 3, 09:14$49.00Paid
INV-20932Oct 3, 09:14$49.00Paid

Both invoices were created within the same minute. This looks like a duplicate charge from a retried payment. No refund will be promised, and the case will be escalated to Finance.

Secondary bug captured: GitHub issue #771 was created. "Export to CSV on Reports page unresponsive (Pro plan, reported via #4182)." Its labels are bug and needs-repro. Browser and steps are still unknown.

Step 3: Draft the reply

reply:

Hi Dana, thanks for flagging both of these!

Duplicate charge: I can see two $49.00 charges on Oct 3 (INV-20931 and INV-20932). That definitely looks like a duplicate. I've escalated it to our billing team for review, and they'll follow up with you directly.

Export button: Sorry it isn't working. Could you send the steps you took, which browser you're using, and a screenshot of the Reports page? That will help our engineers track it down quickly.

Thanks for your patience!
The Ledgerly Invoicing Support Team

(94 words, one next step per issue, no refund or date promised.)

Step 4: Agent approves (STOPPED)

The draft was posted to the support lead, @marcus.liu, in #support-review:

Ticket #4182: Billing + Bug
[ Approve ] [ Edit ] [ Reject ]

⏸ The workflow is waiting for approval. Reply with Approve, Edit (and include your changes), or Reject to continue. Nothing will be sent to the customer until you respond.

Step 5: Reply in thread

Pending approval. Once the reply is approved, it will be sent in the original #support thread. The ticket will then be tagged billing, bug, escalated-finance and awaiting-customer.

Status so far
  • Produced: route (Billing), reply (draft), GitHub issue #771, and a Finance escalation note for INV-20932.
  • Saved to: the ticket #4182 internal notes and the #support-review thread.
  • Remaining: approval from @marcus.liu, then sending the reply and tagging the ticket.
Written by AI from this prompt. Your results will vary.

Run it in Claude Code or Codex: save as .claude/skills/support-ticket-triage-bot/SKILL.md (or .agents/skills/ for Codex) and say "run the Support triage bot workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: ticket, product, docs_url. Build or run it step by step at prompts-gpt.com/workflows/support-ticket-triage-bot.

Make it repeatable

Keep using this prompt without pasting it in every time.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in AI Business Workflows