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

# Backup Alert Bundler

> Bundle backup alert tickets for the same client only when every protected configuration, classification and severity match, and keep a short rolling status label on the parent title from the newest alert.

Runs asAgent Build it with Agent Builder: add the action to a Flow, choose Prompt the Agent, and paste this in. It runs unattended on a matching ticket event. You can also run it yourself in Super Magic while you prove it out.Works withThreadRole[Dispatcher](https://docs.getthread.com/start-here/roles/dispatcher), [Technician](https://docs.getthread.com/start-here/roles/technician)OutcomeFewer Escalations & Less Noise, Time & Cost Savings (Capacity)Category[Alert Runbooks](https://docs.getthread.com/skill-library/alert-runbooks/overview) · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/alert-runbooks/backup-alert-bundler/SKILL.md)

**When to use:** Your backup platform opens a new ticket for every failed job, boot verification and screenshot check, for the same protected machines on the same appliance. You want one open ticket per real problem, and you want its title to show the latest status at a glance, without ever bundling a warning into a critical or two different machines together.

**Run it:** on one ticket · or as a Flow (when a ticket is created on your backup alerts board). For deciding what the failure means, follow up with Backup Failure Triage (`devices-and-infrastructure/backup-failure-triage`).

## Prompt

```
Bundle this backup alert into an existing ticket only on an exact match, and keep the parent title current.

1. KEYS. From this ticket extract: the client company; every configuration or protected-machine ID in the title (all of them); the appliance or device ID; the severity (for example Critical or Warning); and the type, subtype and item.

2. CANDIDATES. Search open tickets on the same board for the same client created in the last 48 hours.

3. MATCH. A candidate matches only if ALL of these are identical: client, every configuration ID, type, subtype and item, and severity. Critical bundles only with Critical, Warning only with Warning. Any partial match is not a match. No matches: add the internal note "No exact backup alert match. Not bundled." and stop.

4. BUNDLE. The oldest matching ticket is the parent. Merge every newer match, including this ticket, into it, then set each child to your closed status (look up the real status on that board).

5. STATUS LABEL. Read the NEWEST bundled ticket's title for a status line (for example "Boot Verification failed: Blue screen (BSOD)"). Shorten it to a 2 to 3 word label ("Boot Verify BSOD", "Backup Send Error"). If the parent title already ends with " - <old label>", replace that label; never stack labels. Otherwise append " - <label>". No status line: leave the title alone.

6. NOTE. On the parent, add an internal note: how many tickets were bundled, their numbers, the configuration IDs, classification and severity matched on, and the label applied (or "No status label added").

Never bundle across clients, appliances or severities. Never invent IDs. Notes are plain text, no markdown or emojis.

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


## Related topics

- [Alert Runbooks](https://docs.getthread.com/skill-library/alert-runbooks/overview.md)
- [Downloads, Alerts, and Scheduled Delivery](https://docs.getthread.com/analytics/downloading-alerts-scheduling.md)
- [Set Up Single Sign-On (SSO) with Microsoft 365](https://docs.getthread.com/inbox/how-to-setup-single-sign-on-sso.md)