monitor-sla — Claude Code command: what it does, how to install
monitor-sla tracks MQL to SQL SLA compliance, highlights routing bottlenecks, and suggests corrective steps across marketing and sales pipelines.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/monitor-sla.mdWhat monitor-sla does
The command runs an orchestration pipeline: it pulls timestamps from MAP and CRM systems, calculates lead response and acceptance times, and checks them against the target threshold. When numbers dip, it diagnoses breakdowns across specific owners, campaigns, or territories.
Each run logs an audit plan into .claude/plans/plan-<timestamp>.json with dependencies, failure recovery, and success metrics. If compliance stays below the target for two consecutive intervals, it triggers an escalation ladder from RevOps to sales leadership. The default retry limit for failed data requests is set to 2.
What it helps with
- Calculate MQL to SQL SLA performance across custom timeframes
- Pinpoint segments and campaigns falling behind response benchmarks
- Generate actionable playbooks for routing rule adjustments
- Post compliance snapshots and at-risk cohorts to notification channels
Example prompts for the agent
- /sales-handoff-orchestration:monitor-sla --segment enterprise --window 7d --threshold 85
- /sales-handoff-orchestration:monitor-sla --segment smb --window 24h --threshold 90 --notify revops-alerts
- /sales-handoff-orchestration:monitor-sla --segment mid-market --window 30d --threshold 80 --dimensions owner
How to install monitor-sla
Manually: put the files in place
.claude/commands/monitor-sla.mdCall it with /monitor-sla. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/monitor-sla.mdCall it with /prompts:monitor-sla. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/monitor-sla.prompt.mdManually: put the files in place
.gemini/commands/monitor-sla.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about monitor-sla
How to install monitor-sla in Claude Code?
Save the command markdown definition to .claude/commands/monitor-sla.md in your project root.
What does the monitor-sla command do?
It audits lead handoff velocity between MQL and SQL, flags teams lagging behind targets, and suggests queue adjustments.
When does monitor-sla trigger an escalation?
An escalation to sales and marketing leadership initiates if SLA compliance stays below target for two consecutive monitoring windows.
Source text
monitor-sla.md · Apache-2.0
--- name: monitor-sla description: Tracks MQL→SQL SLA performance, raises alerts, and recommends corrective actions. usage: /sales-handoff-orchestration:monitor-sla --segment enterprise --window 7d --threshold 85 --- # Command: monitor-sla ## Inputs - **segment** – filter for program/team to analyze. - **window** – time period (24h, 7d, 30d) for metrics. - **threshold** – SLA compliance target percentage. - **notify** – optional channel or email for alert delivery. - **dimensions** – optional breakdowns (owner, geo, campaign). ### GTM Agents Pattern & Plan Checklist > Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: SLA monitoring usually follows a **pipeline** (aggregation → calculation → diagnostics → actions → alerts). If diagnostics + recommendations can run in parallel, log a **diamond** segment and merge gate. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, data sources, task IDs, dependencies (dashboards, alert channels), error handling, and success metrics (SLA %, response time, queue depth). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for CRM automation diffs, Context7 for MAP/CRM field docs, Sequential Thinking for retro cadence, Playwright for form QA when routing fixes require front-end checks. - **Guardrails**: Default retry limit = 2 for failed data pulls/alerts; escalation ladder = RevOps Director → Sales Manager → CRO. - **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm agents, dependencies, deliverables. ## Workflow 1. **Data Aggregation** – pull MAP/CRM timestamps (MQL created, accepted, touched) plus routing metadata. 2. **SLA Calculation** – compute response time, acceptance time, conversion rates vs targets. 3. **Drill-down Diagnostics** – highlight segments, owners, or campaigns below threshold. 4. **Action Recommendations** – prescribe playbooks (re-prioritize queues, add enablement, adjust routing rules). 5. **Alert Packaging** – send summary + deep dive dashboards to notify channels. ## Outputs - SLA dashboard snapshot with compliance %, aging pipeline, at-risk cohorts. - Recommendation list with owners and due dates. - Optional incident ticket for severe breaches. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `revops-director` – reviews systemic issues and approves remediation. - `sla-tracking` skill – ensures methodology + thresholds are standardized. - `routing-logic` skill – recommends rule adjustments causing delays. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., Sales Manager covering RevOps Director) when specialists unavailable. - **Escalation triggers**: if SLA compliance stays below threshold for two consecutive windows, trigger escalation to Sales + Marketing leadership and open an incident per GTM Agents rip-cord. - **Plan maintenance**: update plan JSON/change log whenever thresholds, alert channels, or remediation playbooks change. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents