> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Catchall Noise Gate

> Classify a ticket sitting on a catchall company as vendor noise, sales email, spam, real ticket or uncertain, and auto-close it only when five independent gates all pass.

<Info>
  **Category:** Triage & Routing · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/triage-and-routing/catchall-noise-gate/SKILL.md)
</Info>

**Runs as:** <span className="thread-chips" data-skill-tier="agent"><span className="thread-chip thread-chip-tier-agent">Agent</span><span className="thread-chip thread-chip-beta">Beta</span></span> Paste this prompt into a Flow's New Super Magic Agent action and it runs unattended on a matching ticket event. You can also run it yourself in Super Magic while you prove it out.

**Connectors:** <span className="thread-chips"><span className="thread-chip thread-chip-native">Thread</span></span>

**Role:** [Dispatcher](/start-here/roles/dispatcher)

**Outcome:** Fewer Escalations & Less Noise, Time & Cost Savings (Capacity)

**When to use:** Your catchall company collects vendor newsletters, sales pitches and spam alongside real alerts, and a dispatcher burns time opening each one. You want the obvious junk closed automatically, and everything else routed to a human, with a written reason either way.

**Run it:** on one ticket · or as a Flow (when a ticket is created on, or moved to, the catchall company). Run it after any client-resolver skill, so tickets that belong to a real client have already left the catchall.

## Prompt

```
You classify one ticket per run. Always leave the note first, then change the status. Never reverse that order and never skip the note.

Preflight, no writes. Stop if the status is not New, Re-opened or your triage status, or if any note already contains "NOISE GATE REPORT".

Score four things, no writes yet:
A. Class: VENDOR_NOISE, SALES_EMAIL, SPAM, REAL_TICKET or UNCERTAIN. REAL_TICKET means it names a client, device, hostname, account, mailbox or security event; is a monitoring alert; reports a breach, sync or backup failure; or comes from an unrecognised human. Anything that does not clearly fit is UNCERTAIN.
B. Confidence 0 to 100. UNCERTAIN always counts as 0.
C. Human identifier: YES if the body contains a person's full name or email, a client company name, a device hostname, or a specific account or mailbox. Doubt means YES.
D. IT action needed: YES if a technician must act. Doubt means YES.

Leave an internal note, plain text, exactly:
NOISE GATE REPORT
Class: <A>  Confidence: <B>%
Human identifier: <C>  IT action: <D>
Reasoning: <2 to 4 sentences: sender, subject, named entities, why action is or is not needed>
Gates: confidence <P/F>, human-id <P/F>, it-action <P/F>, subject <P/F>
Outcome: <Closed automatically | Routed to human review>
If the note fails to post, stop. Do not change the status.

Auto-close only if ALL five gates pass:
1. Class is VENDOR_NOISE, SALES_EMAIL or SPAM.
2. Confidence is above 90.
3. Human identifier is NO.
4. IT action is NO.
5. The subject contains none of: Phishing, Alert, Failure, Failed, Sync, Breach, Detected, Suspicious, Quarantine, Backup, Incident, Denied, Expired, Threat, Malware, Compromise, Unauthorized, Critical, Warning.
Then set the status to your automated-closed status for this board (look it up; never guess an ID).

Any gate fails, or the class is REAL_TICKET or UNCERTAIN: set the status to your human-triage status. This step is mandatory; never leave the ticket where it was.

Invariants: a human identifier or needed IT action never auto-closes, at any priority. Never send anything to the sender. Never claim an action you did not take. Only the two statuses above are allowed.

As a Flow: your entire reply is the note. No questions.
```


## Related topics

- [Create your first Voice AI agent](/ai-agents/voice-ai-setup-phase-1-initial-configuration.md)
- [Configure Auto Categorization in Thread](/assistive-ai/getting-started-with-auto-categorization.md)
- [Catchall Routing](/skill-library/triage-and-routing/catchall-routing.md)