An SLA works when the handoff has a clear owner and everyone reads the clock the same way. An overdue-lead report can create an argument before it creates a next action.1 Faster response typically brings higher contact rates, better SAL rates, and more opportunities at lower cost per opportunity.2 Set the operating rules first, then use the clock to expose routing, capacity, and follow-up problems.
Define the handoff event
Write the handoff as an operating event. The receiving owner needs to know what changed, when, and what action proves the transfer is complete.
A marketing-to-sales SLA defines the handoff conditions, follow-up commitment, and evidence used to review both teams.3 Before you call a handoff overdue, define the qualifying event, start time, stop event, business-hours rule, exclusions, and escalation owner. Build the overdue view from those definitions, inspect the records behind it, and keep unknown timestamps in a separate exception group.4
Ask: "When? What counts as 'taking it'?".5 Move on when the handoff event can be identified from the record without asking either team to interpret it after the fact.
Assign ownership at the boundary
Ownership should change at a recorded boundary, and that boundary should tell people what to do next. Keep the transfer simple enough that a person can see who acts without checking several queues.
Assign one accountable owner to each opportunity.6 Record when the receiving owner accepts responsibility and what acceptance requires. Once Sales accepts a lead and it becomes a SAL, the lead is formally handed off and becomes the responsibility of the Sales team under the SLA.7
For a downstream customer handoff, specify which AE schedules and starts the external handover and which person in Customer Success receives it.8 This keeps the transfer from ending at an internal status change. The record should answer who owns the opportunity before acceptance, who owns it after acceptance, and who handles an escalation.
Set the response clock
A response target works only when everyone starts it from the same event. Write the clock into the agreement instead of leaving the start point to team convention.
Marketing may start the SLA clock at form submission while Sales may start it at assignment.9 Neither team can fairly interpret the result until the agreement defines the clock.10
Set the response target by lead type.11 Define a minimum sample for review and set acceptance guardrails from the way the operation runs.12 Keep every threshold visible and editable. Treat each threshold as an operating choice, and present none as a universal benchmark.13
Specify whether the target runs during business hours, what pauses it, and what event stops it. A person reviewing the record should be able to calculate elapsed time without guessing.
Capture the fields that explain delay
Elapsed time alone cannot tell you whether a delay came from routing, assignment, missing context, or follow-up. Capture enough context to separate those causes before changing the process.
Record the lead or contact identifier, email, company or domain, creation timestamp, and lifecycle-stage timestamps such as MQL and SAL or SQL.14 Keep the source or channel, campaign information, UTM parameters, form or landing-page details, and intent signal.15
Capture lead score and model version, ICP tier, persona, industry, and firmographics.16 Log the assignment timestamp, owner, queue history, reassignment history, region, and time zone.17 Store the SAL acceptance or rejection date, rejection reason, and any associated opportunity.18
Use these fields to trace the path from creation to acceptance. A missed target should be assignable to a specific point in that path.
Define what happens after the first response
The first response does not finish the handoff. The agreement needs a clear stopping point so an unworked lead does not disappear into an open status.
The Sales team commits to a response time and a follow-up cadence that exhausts and dispositions an inbound lead before returning it to the Marketing team as a Prospect.19 Write the required follow-up actions, the disposition options, and the condition for returning the record. Keep those actions attached to the owner who accepted the lead.
Measure how quickly Sales responds after lead creation or MQL handoff, then quantify the effect on acceptance, meeting setting, and pipeline creation.20 The SLA should show both whether the response happened and what the response produced.
Review misses as operating cases
Review the record behind each miss while the details are still available. The review should decide what happens next and repair the point where the process failed.
Review missed follow-up against an explicit operating definition.21 Separate a missed commitment from missing evidence, then identify the next action and the process failure.22 A missing timestamp should lead to a data repair decision, while a late assignment should lead to a routing decision.
Use the review to change the owner, clock, routing rule, or evidence requirement that caused the miss. Each case should have an assigned action and a clear reason for the failure.
What not to do
Use these checks before the SLA becomes a scoreboard that people argue about.
- An ownerless handoff between an SDR and an AE can lose context, produce cold meetings, and invite both sides to blame the other.23
- Review missed follow-up against an explicit operating definition.21
- Do not return an inbound lead before the agreed response and follow-up cadence has exhausted and dispositioned it.19