Scritch vs manual appeal queues
Last updated 6 September 2026
A ticket queue is built to resolve support requests. Scritch is built to produce a complete appeal. This page is for Trust & Safety and support leads who own account appeals, reinstatement requests, and false-positive review. “Manual” here means the usual setup: a ticket queue or shared inbox, plus macro and template replies of the kind Zendesk popularised, all of it designed for general support rather than guided reinstatement. Scritch is not a helpdesk replacement. It covers the appeal path, and most teams keep their existing queue for everything else.
What manual appeal queues and macros usually look like
- Intake arrives as a ticket or a web form, in the same queue as billing and password questions.
- An agent applies a macro or works from an internal checklist.
- Evidence is collected ad hoc, over email replies and attachments.
- The outcome is recorded in the ticket, often without a verified path back to a working account.
Where that breaks under false-positive and reinstatement load
Helpdesk macros are good at what they were built for: fast, consistent replies. Appeals ask for something else, and the gap shows up as volume rises.
- Evidence packs come in incomplete or inconsistent. Two agents working the same policy ask for different documents.
- Decisions are hard to audit. Reconstructing why one appeal was granted and a similar one was not means reading a thread rather than a record.
- Macros answer questions, they do not gather proof. Canned text tells the user what is needed once. It does not walk them through submitting it.
- Capacity goes to back-and-forth. Agent time is spent chasing missing documents instead of on decision quality.
What Scritch is built for instead
- Guided evidence collection. The user is walked through what the appeal requires, rather than left to compose a free-form ticket.
- False-positive and reinstatement cases. The shape of the product is the wrongful or mistaken enforcement case, not every support category.
- A verified reinstatement path where the workflow supports one, so the case ends in a checked outcome rather than a closed ticket.
- Structure for review. The output is a consistent package a Trust & Safety or support reviewer can act on.
Scritch does not decide outcomes and does not replace your helpdesk. Coverage depends on the platforms and workflows in scope, so confirm the fit for your own appeal types before you move intake.
Side by side
| Dimension | Manual queues and helpdesk macros | Scritch |
|---|---|---|
| Primary job | General support tickets | Guided appeals and reinstatement |
| Evidence | Ad hoc, chased by an agent | Guided collection aligned to the appeal |
| Consistency | Macro text helps, case structure still varies | Repeatable appeal structure |
| False-positive focus | Possible with process, not the default product shape | Designed around false-positive and reinstatement cases |
| Outcome | Ticket closed or resolved | Verified reinstatement where the workflow supports it |
| Best fit | Broad support orgs with light appeal volume | Teams where appeal quality and backlog matter |
Open scritch.xyz to see how guided appeals are put together.
Who should stay on queues and macros
- Low appeal volume with simple policy outcomes.
- Appeals already handled end to end inside an existing Trust & Safety case system.
- Teams that need canned answers rather than guided evidence.
Who should evaluate Scritch
- Rising false-positive or reinstatement volume.
- A need for auditable, consistent evidence packs.
- A support and Trust & Safety handoff that stalls on missing documents.
Questions people ask
What is Scritch? Tooling for guided account appeals and reinstatement, with structured evidence collection aimed at false-positive and related review cases.
Is Scritch a helpdesk replacement? No. Scritch is not a general helpdesk. Teams usually keep their ticket system for broad support and use Scritch where appeals need guided evidence and a clearer reinstatement path.
How is this different from macros? Macros speed up replies. They do not systematically collect the right evidence or standardise the appeal package the way a guided flow does.
Who is this for? Trust & Safety and support leads responsible for appeal quality, backlog, and false-positive handling.
Does Scritch guarantee reinstatement? No. Platforms and policies decide outcomes. Scritch helps structure the appeal and the evidence behind it. It does not override a third-party decision.
Can we keep our existing queue? Often yes. Many teams run Scritch for the appeal path and keep the helpdesk for everything else. What the integration looks like depends on how you work today.
What should we evaluate before switching appeal intake? Appeal volume, false-positive rate, time spent chasing documents, audit requirements, and whether macros already fail to produce complete cases.
What happens to the evidence users submit? Appeals involve user documents, so read the data handling policy as part of your review.
Next step
Start at scritch.xyz, or read the product overview for how the guided flow works end to end.