sla-tracking

v2026.09.25

Use to design measurement, alerting, and reporting for MQL→SQL SLAs.

GitHub
Install command
npx skhub add gtmagents/sla-tracking
Markdown
SKILL.md

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.

Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.25

Published

Sep 25, 2026

Category

Uncategorized

License

Apache-2.0

Source path

plugins/sales-handoff-orchestration/skills/sla-tracking

Default branch

main

Latest commit

78e0419

Tree SHA

9016d99