Triage support tickets and draft replies with evidence
Get support messages checked against ticket history, with reported bugs reproduced and reply drafts ready for a person to review and send.
What the agent did
Source-reported example · as described by Varun Dubey
A WordPress agency uses a custom support-triage skill to read customer messages, check ticket history, reproduce reported bugs on a test site, and prepare bug cards and reply drafts. A separate skill files support emails into Basecamp while avoiding duplicates.
The author gives no measured productivity results. People on the team review and send every customer reply.
Limitations
This is an engineering-focused support setup. Bug reproduction happens in a browser before a reply is drafted. The agency's roughly 90 skills cover its whole operation; they are not all prerequisites for this task.
Try it in your business
What you'll need
The original setup uses custom support instructions, integrations with messaging and help-desk tools, and a test environment. The support skill's contents, specific chat and help-desk products, and costs are not disclosed.
The original is a custom-built system. The prompt below is a simpler starting point and won’t reproduce it.
Starting prompt
The author didn't publish their prompt (skill contents not published), so this is our adaptation.
How ours differs from the original setup: Original uses ~90 skills, chat/help-desk integrations and bench sites; ours is a single triage pass with optional reproduction.
Review today's support messages in [inbox or help desk]. Summarize each issue, check the customer's history and [known-issues document], and draft a reply using the evidence you found. For suspected bugs, reproduce the problem on [test site] if available and record the steps and result. Otherwise flag it for investigation. Save drafts for review and list refund requests separately. Do not send replies or issue refunds.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Triage customer support tickets and prepare fixes or replies for your approval
Have Codex triage incoming customer support tickets and prepare a reply or a proposed fix that waits for your approval before anything goes out.
Our suggested starting prompt — not the author's original · untested
You'll need: Codex access; a Linux machine with a dedicated user account per agent; email delivery into Maildir with a trigger that wakes Codex on new mail; scheduled wakeup timers; agent accounts in your support ticketing or bug-tracking system and CI; command-line tools or API access to those services; your own review and approval of each prepared fix or reply
You help me run customer support for my small software business. When a new support ticket or support email arrives [ticket system or mailbox], read it and any related history, then triage it: label it as a bug, question, feature request or duplicate, note its urgency, and link any existing ticket it matches. For questions, draft a reply to the customer. For bugs, investigate in the code repository [repo], reproduce the problem if you can, and prepare a proposed fix on a separate branch with a short explanation, without merging or releasing it. Put each draft reply and proposed fix in my approval queue [where] with a one-paragraph summary and anything you're unsure about. Do not send anything to customers, merge, deploy, close tickets or delete anything; I will review and approve every reply and fix myself.
Draft follow-ups to customers who asked for a feature once it ships
Once a feature ships, have Grok Bot find the customers who asked for it and save personalized Gmail follow-up drafts for your review.
Author's original prompt
You'll need: Grok Bot connected to the mailbox where customers write in (author used Gmail), with permission to create drafts; a shipped feature and the words customers used to ask for it. How Gmail was connected and whether, how or when the drafts were sent are not disclosed.
Go over ALL my HabitKit support emails and check for people who wished for a "Quit habits / Inverse habits" feature (where habits are checked on by default) in HabitKit. Draft a message for them that tell them that it finally landed in the app, apologize that it was a long time coming. Say that I would be super happy if they would check it out. Only drafts in my Gmail!
Run a new client's standard audits and draft the kickoff strategy brief
Have Claude Code run a new client's standard first-week audits and draft a strategy brief with recommended priorities for you to review before the kickoff call.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code; read access to the client's website and, for the analytics and CRM reviews, the client's Google Analytics/Tag Manager and email/CRM tools; a written audit checklist; a brief template; the owner's review before anything is sent
We're onboarding a new client: [client name], website [URL], industry [industry], main goal [goal] (from their intake form in [file]). Please prepare a first-week audit and a draft strategy brief for me to review. 1) Technical SEO: check the public site for crawlability, page titles and descriptions, broken links, page speed and mobile issues. 2) Analytics: from the export or read-only access I've given you [path/access], note whether Google Analytics and Tag Manager are set up and tracking key actions. 3) Competitors: for these competitors [list], compare the main keywords and topics they appear to target. 4) Email/CRM: from my notes [file], summarize their current setup and gaps. Save each audit as a separate file with findings, evidence and what you couldn't check. Then draft a one-to-two page strategy brief with the top 3–5 recommended priorities, each tied to the audit findings, and list open questions for the kickoff call. Keep everything as drafts in [folder]: don't send anything to the client, don't change any site, analytics or CRM settings, don't buy any tools and don't delete anything. Ask me before using any login or access I haven't listed.

