Skip to content

User ticket sweep into scrubbed issues you approve

Sweeps new and reopened user tickets in your app, checks the facts in the codebase and drafts one thing per ticket: an issue, a question back to the sender or a close note. Drafts never quote the ticket or name the sender, and nothing is filed, asked or closed until you approve each one.

SupportWorks with Claude Code · CursorCommunity example
Build your promptSee requirements

What it does

  • Collects tickets that are new, reopened or have a new reply
  • Checks the attached screen, release and recent actions before calling anything unclear
  • Drafts an issue in the repo's style with no sender name or quoted text
  • Drafts at most two questions per ticket, then flags it for you to ask in person
  • Flags anything that looks like patient detail for redaction

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Opening any issue
  • Sending a question to the sender
  • Closing a ticket

You decide what happens next.

More about this workflow

This setup is for support leads and small teams who answer customers every day. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it collects tickets that are new, reopened or have a new reply. Next, it checks the attached screen, release and recent actions before calling anything unclear. Then it drafts an issue in the repo's style with no sender name or quoted text. After that, it drafts at most two questions per ticket, then flags it for you to ask in person. Finally, it flags anything that looks like patient detail for redaction. It works with your help desk, git host and issue tracker, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before opening any issue, sending a question to the sender and closing a ticket, and says plainly if a step cannot be undone.

“Nothing is published, asked or closed without approval.”
mshamblin5150-code mshamblin5150-code on GitHub · Sep 26, 2026
Before you startHelp desk · Git host accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • Zendesk

    Handles the help desk part of this job. Grant a limited agent seat that writes internal notes.

    API required: Yes. Needs an API token or OAuth client created by a Zendesk admin.

    Sign up: Zendesk

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Linear

    Handles the issue tracker part of this job. Grant read plus create in one triage team.

    API required: Yes. Needs a personal API key or an OAuth app.

    Sign up: Linear

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Writes careful replies and reads long ticket threads.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Made for sorting and routing at high volume.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

app admin page

default 2

2Your prompt

4 of 4 still empty
Fill these in before you run it: [WHERE TICKETS LIVE: app admin page] [TRIAGE LABELS FILE] [STAFF LIST TO CHECK DRAFTS AGAINST] [MAX QUESTIONS PER TICKET: default 2] You are the User ticket sweep into scrubbed issues you approve agent. Sweeps new and reopened user tickets in your app, checks the facts in the codebase and drafts one thing per ticket: an issue, a question back to the sender or a close note. Drafts never quote the ticket or name the sender, and nothing is filed, asked or closed until you approve each one. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Collects tickets that are new, reopened or have a new reply - Checks the attached screen, release and recent actions before calling anything unclear - Drafts an issue in the repo's style with no sender name or quoted text - Drafts at most two questions per ticket, then flags it for you to ask in person - Flags anything that looks like patient detail for redaction What you must never do without a yes from a person: - Opening any issue - Sending a question to the sender - Closing a ticket Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Zendesk with its own login, not yours. Grant a limited agent seat that writes internal notes.
  2. 2Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  3. 3Connect Linear with its own login, not yours. Grant read plus create in one triage team.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: opening any issue, sending a question to the sender, closing a ticket.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for User ticket sweep into scrubbed issues you approve](https://trustcase.dev/badge/user-ticket-sweep-into-scrubbed-issues-you-approve.svg)](https://trustcase.dev/use-cases/user-ticket-sweep-into-scrubbed-issues-you-approve)
HTML
<a href="https://trustcase.dev/use-cases/user-ticket-sweep-into-scrubbed-issues-you-approve"><img src="https://trustcase.dev/badge/user-ticket-sweep-into-scrubbed-issues-you-approve.svg" alt="Trustcase trust score for User ticket sweep into scrubbed issues you approve" height="20"></a>

More support workflows

  • Ticket triage

    Sorts new tickets by topic and urgency so the right person sees them first.

  • Reply suggester

    Drafts answers to common questions using your help docs.

  • Refund checker

    Checks refund requests against your policy and lays out the facts.

  • Help doc gap finder

    Spots questions customers keep asking that your docs do not answer.

Other workflows that use the same tools

  • Weekly delivery status report

    Operations. Pulls your team's work items once a week and builds a status report grouped by initiative. It puts at risk items first and flags anything with no update in two weeks.

  • Overnight safe task picker

    Engineering. Each night it looks over the day's unfinished work and picks 3 to 5 coding tasks that are safe to run overnight. It only writes a report with a ready prompt for each one.

  • Morning ticket dashboard with tick to approve queue

    Engineering. Every morning an agent refreshes a one screen dashboard in your notes from the issue tracker, your workstream notes and inbox. It reads only, proposes board changes as checkboxes and drafts first pass PR reviews that are never posted.