Skip to main content
command CX Codex

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

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/monitor-sla.md
Open on GitHub

What 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.md

Call it with /monitor-sla. For all projects use ~/.claude/commands/

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
design-referral design-referral is a Claude Code command that designs referral programs with incentives, rules, and governance, producing a charter, stakeholder deck, and risk log. CX Codex +1 ★ 450repo stars design-nurture design-nurture builds multi-stage nurture journey blueprints with audience segmentation, triggers, and a content plan. Useful for planning lifecycle marketing and RevOps campaigns. CX Codex +1 ★ 450repo stars run-launch The run-launch command builds a launch execution plan with a timeline, communications, monitoring, and go/no-go gates. Use it to coordinate channel work and launch-day operations. CX Codex +1 ★ 450repo stars build-model The build-model command builds a data modeling plan: transforms, tests, deployment schedule and dependencies for analytics use cases. CX Codex +1 ★ 450repo stars ship-dashboards ship-dashboards builds a dashboard launch plan covering visualization, publishing, user enablement, and monitoring. Use it to coordinate the rollout and define what to track afterward. CX Codex +1 ★ 450repo stars launch-program launch-program takes a referral program from task checklist through tooling, launch comms and training to a monitored go-live day. CX Codex +1 ★ 450repo stars plan-pillar plan-pillar builds a content pillar plan with hero assets, derivative pieces, and a distribution schedule. Saves task dependencies and KPIs directly to JSON. CX Codex +1 ★ 450repo stars forecast-discipline forecast-discipline — a Claude Code skill that builds forecast-call methodology: commit/best case/pipeline tiers, inspection checklists, and accuracy thresholds. Runs when you prepare weekly or monthly sales forecasts. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open