Awesome-omni-skill sla-management-framework

SLAs for rev ops: response times, escalation, enforcement. Use when defining or managing sales and marketing SLAs.

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/sla-management-framework" ~/.claude/skills/diegosouzapw-awesome-omni-skill-sla-management-framework-b180d1 && rm -rf "$T"
manifest: skills/development/sla-management-framework/SKILL.md
source content

SLA Management — Framework

Service Level Agreements for revenue operations: response times, escalation processes, and enforcement mechanisms.


Why SLAs Matter

78% of deals go to the vendor that responds first. Response speed is the single biggest controllable factor in conversion.

The reality:

  • Average B2B lead response time: 42-47 hours
  • 63% of businesses never respond to inbound leads
  • Only 17% respond instantly

The impact:

  • Sub-5-minute response = 21x more likely to qualify
  • Sub-1-minute response = 391% higher conversion (Velocify)
  • Within 1 hour = 53% conversion vs 17% after 24 hours

SLA Types

Response SLAs

Time between a lead action and the first sales contact attempt.

Lead TypeRecommended SLARationale
Demo Request< 5 minutesHigh-intent; buyers are actively evaluating
Pricing Inquiry< 5 minutesClear buying signal
Inbound CallImmediateLive prospect on the line
Free Trial Signup< 10 minutesActive evaluation mode
Content Download2-24 hoursAllow time to consume content
Webinar RegistrationPost-event or 24hContact relative to attendance
Newsletter Signup24-48 hoursLow-intent, nurture appropriate

Follow-Up SLAs

Cadence and timing for subsequent contact attempts.

AttemptTimingChannelPurpose
1stWithin SLACall + EmailInitial connection
2nd+1 dayEmail with social proofValue reinforcement
3rd+3 daysCallPersistence
4th-7thOver 2 weeksMulti-channel mixSustained outreach
8th+Weekly or nurtureEmail cadenceLong-term nurture

Benchmark: 8-12 total attempts is optimal. 7+ touches typically required before buying decision.

Handoff SLAs (Marketing to Sales)

StageSLAOwner
MQL to Sales Assignment< 15 minutesAutomation
Sales Review/Accept< 2 hoursSDR/AE
First Contact Attempt< 5 minutes after acceptanceSDR/AE
SQL Disposition/FeedbackWithin 7 daysSDR/AE

Meeting SLAs

ActionSLAOwner
Calendar invite sentWithin 1 hour of bookingSDR
Pre-meeting research complete24 hours before meetingAE
Meeting reminder sent24 hours + 1 hour beforeAutomation
Post-meeting notes loggedWithin 2 hoursAE

SLA by Lead Tier

Enterprise Leads (1,000+ employees / $1B+ revenue)

SLA TypeTarget
Response time (all high-intent)< 5 minutes
Support availability24/7
Dedicated account managementRequired
Escalation response1-4 hours

Mid-Market Leads (100-999 employees / $50M-$1B revenue)

SLA TypeTarget
Response time (demos)< 5 minutes
Response time (other)< 1 hour
Support availabilityBusiness hours + extended
Account managementPooled or dedicated
Escalation response4-8 hours

SMB Leads (<100 employees / <$50M revenue)

SLA TypeTarget
Response time (demos)< 15 minutes
Response time (other)< 4 hours
Support availabilityBusiness hours
Account managementSelf-serve + CSM support
Escalation response24 hours

SLA by Lead Source

Lead SourceIntent LevelResponse SLAFollow-Up Cadence
Demo RequestHigh< 5 min6 touches in 48h
Pricing InquiryHigh< 5 min6 touches in 48h
Free TrialHigh< 10 minDaily for 7 days
G2/Capterra IntentHigh< 15 min5 touches in 72h
Webinar AttendeeMedium< 2 hours post-event4 touches in week
Content DownloadMedium2-24 hours3 touches in week
Newsletter SignupLow24-48 hoursNurture sequence
Outbound ReplyMedium-High< 30 min5 touches in 72h

Escalation Matrix

Escalation Levels

LevelTimeframeEscalated ToAction Required
L1SLA at 50%Assigned RepReminder notification
L2SLA at 75%Rep + ManagerWarning + priority flag
L3SLA BreachedManagerImmediate reassignment or assist
L42x SLADirector/VPReview + root cause analysis
L5Pattern/RepeatExecutiveProcess/resource intervention

Escalation Triggers by SLA Type

Response SLA Breach:

50% elapsed  → Slack/email reminder to rep
75% elapsed  → Manager cc'd, lead flagged urgent
100% elapsed → Auto-reassign to backup rep or round-robin
200% elapsed → VP notified, incident logged

Follow-Up SLA Breach:

Missed attempt     → Task auto-created for next business hour
2 missed attempts  → Manager alerted
3+ missed attempts → Lead recycled with disposition required

Meeting SLA Breach:

No-prep 12h before → Manager notified
No-show without reschedule → Auto-escalate + SDR re-engagement

Escalation Path by Severity

SeverityCriteriaEscalation Path
Warning50-74% SLA elapsedSDR/AE (self-correct)
At-Risk75-99% SLA elapsedSDR Manager (intervene)
Breach100% SLA elapsedSales Director (reassign)
Critical150%+ SLA elapsedVP Sales (process review)

HubSpot SLA Configuration

Workflow: Response SLA Tracking

Trigger: Contact Property "Lead Source" is any of [Demo Request, Pricing Inquiry]

Actions:
1. Set property "SLA Start Time" = Current timestamp
2. Set property "SLA Deadline" = SLA Start Time + 5 minutes
3. Set property "SLA Status" = "Active"

Branch: If (Current time - SLA Start Time) > 2.5 minutes
  → Send internal notification "SLA Warning - 50% elapsed"

Branch: If (Current time - SLA Start Time) > 4 minutes
  → Send internal notification "SLA At Risk - 75% elapsed"
  → Set property "SLA Status" = "At Risk"
  → Add to list "SLA Escalation Review"

Workflow: SLA Breach Response

Trigger: Contact Property "SLA Status" = "Breached"

Actions:
1. Reassign to backup owner (round-robin)
2. Send notification to original owner
3. Send notification to manager
4. Log activity "SLA Breach - Auto-reassigned"
5. Add to list "SLA Breach Review"
6. Create task for manager "Review SLA breach - [Contact Name]"

Workflow: Speed-to-Lead Automation

Trigger: Form Submission (Demo Request form)

Actions:
1. Assign owner based on territory/round-robin
2. Create task "Call lead" due in 5 minutes
3. Send internal SMS notification via Twilio
4. Start SLA timer (set SLA Start Time)
5. Delay 5 minutes
6. Branch: If no activity logged
   → Escalate to manager
   → Reassign via round-robin

SLA Dashboard Metrics

MetricCalculationTarget
% Leads contacted within SLAContacts within SLA / Total contacts>95%
Average response time by repAvg (First contact time - Lead create time)< SLA target
SLA breach count by periodCount of breached leads per week/month< 5%
Escalation frequency by levelCount per level per periodDeclining trend
Response time trendWeekly average response timeImproving

Consequences for SLA Breach

Immediate Consequences

ConsequenceImplementation
Lead ReassignmentAuto-transfer to available rep or manager
Notification CascadeRep, manager, director notified
Priority OverrideLead flagged as urgent in queue
Activity LoggingBreach recorded in contact timeline

Performance Management Consequences

Breach FrequencyConsequence
1 breach/weekVerbal coaching
2-3 breaches/weekWritten warning + training
4+ breaches/weekPerformance improvement plan
Chronic patternRole reassessment

Business Consequences

  • Revenue Loss: 78% of deals go to first responder
  • Pipeline Leakage: Slower response = lower conversion
  • Customer Experience: Negative first impression
  • Competitive Disadvantage: Competitors win on speed

Compensation Implications

Performance LevelImpact
SLA compliance >95%Full commission eligible
SLA compliance 80-95%Commission reduction warning
SLA compliance <80%Commission reduction (5-10%)
Chronic non-complianceAccelerator disqualification

Common SLA Mistakes

MistakeImpactFix
Vague targets"Respond quickly" is unmeasurableDefine specific timeframes
Unrealistic targets1-minute SLA without resourcesAudit capacity, then set targets
One-size-fits-allSame SLA for demos and contentTier by source and intent
No escalation processBreaches with no correctionAutomated escalation matrix
Insufficient monitoringMonthly review instead of real-timeLive dashboards, automated alerts
Poor communicationMarketing doesn't know dispositionShared CRM, mandatory disposition
Static SLAsSet once, never revisitedQuarterly review based on data
No consequencesSLAs exist on paper onlyTie to comp, recognition, career
Missing feedback loopNo lead quality reportsRequired disposition within 7 days
Manual trackingHuman error, delaysAutomated triggers and workflows

Implementation Checklist

Phase 1: Baseline (Week 1)

  • Audit current response times by lead source
  • Document current (informal) SLAs
  • Identify biggest gaps vs. benchmarks
  • Gather input from sales and marketing

Phase 2: Design (Week 2)

  • Define SLA targets by tier and source
  • Design escalation matrix with clear owners
  • Define consequence framework
  • Get leadership alignment on enforcement

Phase 3: Automation (Week 3-4)

  • Configure HubSpot/CRM workflows for tracking
  • Set up automated escalation triggers
  • Build real-time dashboard for monitoring
  • Test with sample leads

Phase 4: Rollout (Week 5-6)

  • Train team on SLA importance and process
  • Communicate expectations clearly
  • Monitor closely during first 2 weeks
  • Adjust based on early feedback

Phase 5: Optimization (Ongoing)

  • Weekly SLA performance review
  • Monthly analysis of breach patterns
  • Quarterly SLA target adjustments
  • Continuous feedback loop improvement

Cross-References

  • Lead Routing: See
    lead-management/lead-routing-framework.md
  • Escalation Playbooks: See
    sla-management-escalation.md
  • HubSpot Automation: See
    sla-management-automation.md
  • Territory Planning: See
    territory-planning-framework.md

Built by ColdIQ & Ivan Falco. For questions on implementation or anything not covered here, reach out to Ivan directly on LinkedIn.