# Sla Tracking > Use to design measurement, alerting, and reporting for MQL\u2192SQL\ Use when this capability is needed. - Skill: `tomevault-io/sla-tracking` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/sla-tracking` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/sla-tracking/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/sla-tracking --- # SLA Tracking System Skill ## When to Use - Establishing or revisiting SLA metrics between marketing, SDR, and sales pods. - Building dashboards/alerts for pipeline speed and follow-up compliance. - Running retrospectives after SLA breaches or pipeline delays. ## Framework 1. **Definitions** – clarify timestamps (MQL, SAL, SQL), owner transitions, and acceptance criteria. 2. **Targets** – set response + acceptance SLAs per segment, region, or channel. 3. **Measurement** – configure data pipelines pulling MAP + CRM events, dedupe logic, and exclusions. 4. **Alerting** – thresholds, notification channels, severity levels, and on-call rotation. 5. **Review Cadence** – weekly dashboards, monthly retros, quarterly recalibration. ## Templates - SLA scorecard (segment → target → actual → variance → owner). - Alert playbook with trigger conditions and escalation steps. - Retro template capturing root cause, fixes, and follow-up experiments. ## Tips - Anchor SLAs to revenue impact (pipeline $) to drive accountability. - Include qualitative context (reason codes) to separate data gaps vs true SLA misses. - Pair with `routing-logic` updates when volume spikes create bottlenecks. --- --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/gtmagents) — claim your Tome and manage your conversions.