Proactive Alerts
Overview
GTM teams spend 30% of their time checking dashboards that should be checking
themselves. Proactive alerts invert this: the system watches your pipeline and
signals 24/7, pushing notifications only when something needs attention.
This skill designs an alert architecture: what to monitor, when to alert, who
to notify, and how to route each signal type to the right person at the right
time — all without alert fatigue.
When to Use
- "Set up pipeline alerts"
- "Notify me when a deal stalls"
- "Alert the team on buying signals"
- "Build a deal risk monitoring system"
- "Set up Slack notifications for pipeline changes"
- "Create a signal-to-Slack pipeline"
Authoritative Foundations
Alert design draws from UnifiedPipeline's deal risk scoring methodology
(transparent scores, daily briefings), SyncGTM's 15+ signal monitoring
system, and Alysio's pipeline risk detection layer (engagement, sentiment,
velocity, and qualification signals).
Prerequisites
- CRM with webhook or API access (HubSpot, Salesforce)
- Slack or Teams for delivery
- Signal data sources (job boards, funding databases, tech stack monitors)
Step-by-Step Process
Phase 1: Alert Categories
| Category |
Examples |
Urgency |
Channel |
| Pipeline Risk |
Deal stalled >7 days, close date pushed, amount decreased, stage moved backward, missing next steps, no activity |
High — requires action today |
Slack DM to rep + manager |
| Buying Signals |
Funding raised, hiring surge, exec change, tech stack shift, job change, website visit spike |
High — time-sensitive outreach |
Slack channel + CRM task |
| Positive Signals |
Deal revived, amount increased, close date pulled in, new large deal created |
Medium — awareness |
Daily briefing |
| Operational |
Bounce rate spike, domain health alert, sequence completion, credit usage threshold |
Medium — requires monitoring |
Slack channel |
| Forecast |
Commit deal at risk, large deal slipped, pipeline coverage below target |
High — executive visibility |
Slack to CRO + weekly report |
Phase 2: Alert Configuration by Role
| Role |
Alerts They Receive |
| SDR |
New lead assigned, lead response overdue, sequence bounce alert |
| AE |
Deal stalled, close date pushed, competitor detected, champion left company |
| Manager |
Team pipeline coverage, rep activity gaps, deal inspection flags |
| CRO |
Forecast changes >20%, large deal at risk, pipeline coverage drop |
| RevOps |
CRM data quality flags, integration failures, enrichment gaps |
Phase 3: Routing and Delivery
- Real-time / Urgent → Slack DM or dedicated #pipeline-alerts channel
- Daily briefing → Scheduled message at 7am with ranked risk list
- Weekly digest → Summary of all alerts, trends, and actions taken
- Escalation → If alert acknowledged but no action in 24 hours → manager notified
Phase 4: Alert Fatigue Prevention
- Max 5 high-priority alerts per person per day
- Group related alerts into single messages
- Allow per-user alert configuration (mute categories, adjust thresholds)
- Track alert-to-action rate — if alerts aren't driving action, tune thresholds
- Monthly alert audit: remove or adjust alerts with <10% action rate
Output Format
Alert architecture document with alert catalog, routing rules, delivery
templates, threshold configuration, and fatigue prevention rules.
Quality Check
Common Pitfalls
Alerting on everything. A Slack channel with 50 alerts/day becomes
invisible. Curate ruthlessly. Only alerts that require action should fire.
No owner. An alert that goes to a channel with no named owner gets
ignored. Every alert type has one person accountable.
Alerting without context. "Deal X stalled" without "it's been in Demo
for 14 days, last contact was a bounce, and the champion changed jobs"
doesn't help. Context drives action.
Same alert for everyone. An SDR doesn't need CRO-level pipeline alerts.
Tailor by role or risk burnout.
No alert audit. Alerts that were urgent 6 months ago may be noise now.
Audit monthly and remove or tune.
Execution Artifacts
references/framework-notes.md — named frameworks, citation anchors, and operating assumptionstemplates/output-template.md — copy-paste deliverable structure for the userscripts/check-output.py — local checklist validator for required sections
This skill includes lightweight artifacts the agent can load on demand:
Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Related Skills
- signal-scoring: The signal detection that feeds buying signal alerts
- pipeline-management: Pipeline structure that enables risk detection
- deliverability-monitoring: Bounce and reputation alerts
- gtm-metrics: Dashboard metrics that complement alerts
1---2name: proactive-alerts3description: Set up proactive GTM alert systems — CRM pipeline alerts, buying signal notifications, Slack/email routing, risk scoring. Use when building alert systems, monitoring pipeline health, detecting buying signals, or setting up automated notifications for GTM teams. Triggers on: "alerts", "notifications", "pipeline alerts", "signal alerts", "monitor pipeline", "deal alerts", "Slack alerts", "pipeline monitoring", "proactive", "warning system", or any request about automated detection and notification.4license: MIT5---67# Proactive Alerts89## Overview1011GTM teams spend 30% of their time checking dashboards that should be checking12themselves. Proactive alerts invert this: the system watches your pipeline and13signals 24/7, pushing notifications only when something needs attention.1415This skill designs an alert architecture: what to monitor, when to alert, who16to notify, and how to route each signal type to the right person at the right17time — all without alert fatigue.1819## When to Use2021- "Set up pipeline alerts"22- "Notify me when a deal stalls"23- "Alert the team on buying signals"24- "Build a deal risk monitoring system"25- "Set up Slack notifications for pipeline changes"26- "Create a signal-to-Slack pipeline"2728## Authoritative Foundations2930Alert design draws from UnifiedPipeline's deal risk scoring methodology31(transparent scores, daily briefings), SyncGTM's 15+ signal monitoring32system, and Alysio's pipeline risk detection layer (engagement, sentiment,33velocity, and qualification signals).3435## Prerequisites3637- CRM with webhook or API access (HubSpot, Salesforce)38- Slack or Teams for delivery39- Signal data sources (job boards, funding databases, tech stack monitors)4041## Step-by-Step Process4243### Phase 1: Alert Categories4445| Category | Examples | Urgency | Channel |46|---|---|---|---|47| **Pipeline Risk** | Deal stalled >7 days, close date pushed, amount decreased, stage moved backward, missing next steps, no activity | High — requires action today | Slack DM to rep + manager |48| **Buying Signals** | Funding raised, hiring surge, exec change, tech stack shift, job change, website visit spike | High — time-sensitive outreach | Slack channel + CRM task |49| **Positive Signals** | Deal revived, amount increased, close date pulled in, new large deal created | Medium — awareness | Daily briefing |50| **Operational** | Bounce rate spike, domain health alert, sequence completion, credit usage threshold | Medium — requires monitoring | Slack channel |51| **Forecast** | Commit deal at risk, large deal slipped, pipeline coverage below target | High — executive visibility | Slack to CRO + weekly report |5253### Phase 2: Alert Configuration by Role5455| Role | Alerts They Receive |56|---|---|57| **SDR** | New lead assigned, lead response overdue, sequence bounce alert |58| **AE** | Deal stalled, close date pushed, competitor detected, champion left company |59| **Manager** | Team pipeline coverage, rep activity gaps, deal inspection flags |60| **CRO** | Forecast changes >20%, large deal at risk, pipeline coverage drop |61| **RevOps** | CRM data quality flags, integration failures, enrichment gaps |6263### Phase 3: Routing and Delivery64651. **Real-time / Urgent** → Slack DM or dedicated #pipeline-alerts channel662. **Daily briefing** → Scheduled message at 7am with ranked risk list673. **Weekly digest** → Summary of all alerts, trends, and actions taken684. **Escalation** → If alert acknowledged but no action in 24 hours → manager notified6970### Phase 4: Alert Fatigue Prevention7172- Max 5 high-priority alerts per person per day73- Group related alerts into single messages74- Allow per-user alert configuration (mute categories, adjust thresholds)75- Track alert-to-action rate — if alerts aren't driving action, tune thresholds76- Monthly alert audit: remove or adjust alerts with <10% action rate7778## Output Format7980Alert architecture document with alert catalog, routing rules, delivery81templates, threshold configuration, and fatigue prevention rules.8283## Quality Check8485- [ ] Alert catalog covers pipeline risk, buying signals, positive signals, operational, and forecast86- [ ] Every alert has a defined owner and SLA for response87- [ ] Routing rules documented (who gets what, when)88- [ ] Alert fatigue thresholds set (max per person, per day, per channel)89- [ ] Daily briefing template created90- [ ] Monthly alert audit cadence established9192## Common Pitfalls93941. **Alerting on everything.** A Slack channel with 50 alerts/day becomes95 invisible. Curate ruthlessly. Only alerts that require action should fire.96972. **No owner.** An alert that goes to a channel with no named owner gets98 ignored. Every alert type has one person accountable.991003. **Alerting without context.** "Deal X stalled" without "it's been in Demo101 for 14 days, last contact was a bounce, and the champion changed jobs"102 doesn't help. Context drives action.1031044. **Same alert for everyone.** An SDR doesn't need CRO-level pipeline alerts.105 Tailor by role or risk burnout.1061075. **No alert audit.** Alerts that were urgent 6 months ago may be noise now.108 Audit monthly and remove or tune.109110## Execution Artifacts111112- `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions113- `templates/output-template.md` — copy-paste deliverable structure for the user114- `scripts/check-output.py` — local checklist validator for required sections115This skill includes lightweight artifacts the agent can load on demand:116Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.117118## Related Skills119120- **signal-scoring**: The signal detection that feeds buying signal alerts121- **pipeline-management**: Pipeline structure that enables risk detection122- **deliverability-monitoring**: Bounce and reputation alerts123- **gtm-metrics**: Dashboard metrics that complement alerts
LeadMagic