# Telegram Alert Routing Template

Route signals into the right chat before they become notification noise.

## Channels

| Channel | Audience | What belongs here | SLA |
| --- | --- | --- | --- |
| Personal review | Solo operator | First-pass signals | 15 min |
| Team triage | Research team | Signals worth group review | 30 min |
| High-priority alerts | Decision makers | Confirmed conviction + context | Immediate |
| Archive / recap | Wider team | End-of-day summaries | Daily |

## Alert Types

| Signal type | Destination | Why |
| --- | --- | --- |
| New discovery |  |  |
| KOL consensus |  |  |
| On-chain surge |  |  |
| Narrative rotation |  |  |
| Score jump |  |  |

## Routing Rules

- Send raw alerts to as few places as possible.
- Escalate only after basic validation.
- Summaries should compress, not repeat, earlier alerts.
- Every alert should imply a next action.

## Review Questions

- Does this alert help someone decide faster?
- Is it better as a brief than a ping?
- Should this go to board instead of chat?