MQL to SQL Handoff Process: How Revenue Teams Move Leads Without Dropping the Ball

Revenue teams argue about a lot of things: pipeline coverage, MQL quality, attribution models, quota targets. But the most expensive problem in most marketing-sales relationships isn't any of those. It's what happens in the 24-48 hours between a lead qualifying as an MQL and a rep making first contact.

Leads get lost. Or they arrive at sales without context. Or reps don't log their outcomes, so marketing has no visibility into what happened. Or sales quietly ignores leads while still expecting marketing to fill the pipeline. Or marketing counts a lead as "handed off" the moment a CRM field flips, while sales considers it "received" only when a rep actively accepts it.

None of these are bad intentions. They're process gaps: places where ownership wasn't defined, where the handoff had no protocol, where accountability wasn't built in. The handoff is where those gaps become revenue problems.

A clean handoff is not a button click or a status change. It's a sequence of actions, responsibilities, and acknowledgments that both teams have agreed to in advance.

What a Handoff Actually Is

The word "handoff" implies a simple transfer, one party giving something to another. But in practice, a lead handoff is a multi-step process with at least five discrete actions, two parties with distinct responsibilities, and a definition of "done" that most teams never explicitly agree on.

Marketing's side of the handoff:

• Verifying that the lead meets the MQL threshold (score, intent signal, or qualification criteria)
• Enriching the lead record with complete contact data and company context
• Routing the lead to the correct rep or queue
• Logging the trigger that caused the MQL conversion (what action crossed the threshold)

Sales' side of acceptance:

• Acknowledging receipt of the lead within the agreed SLA
• Reviewing the activity trail and company context before first contact
• Making the first personalized outreach attempt
• Logging the outcome (accepted, contacted, rejected with reason) back into the CRM

What "done" looks like: The handoff is complete when the lead has been acknowledged by a rep, an outreach attempt has been logged, and the outcome has been recorded. A lead that was passed but never acknowledged is not a completed handoff. A lead that was accepted but never contacted is not a completed handoff. Both sides have to close their loop.

Most disputes about handoff quality stem from teams using different definitions of "done." Write down your definition. Agree to it. Refer back to it.

Key Facts: MQL Handoff Efficiency

• 25% of the average B2B marketing budget is spent generating leads that sales never follows up on, according to Forrester Research, and most of that waste occurs at the handoff boundary.
• Organizations with a defined lead handoff SLA see 36% higher MQL-to-opportunity conversion rates compared to those with informal or unwritten processes (Demand Gen Report).
• Black hole handoffs (where leads are passed but never acknowledged or rejected by sales) account for an estimated 40% of total MQL volume in misaligned organizations (SiriusDecisions).

The 5-Stage Handoff Process

The 5-Stage Handoff Process is a structured framework for moving qualified leads from marketing to sales without information loss, routing errors, or accountability gaps. The five stages are: (1) Trigger: MQL conversion event fires based on unambiguous criteria; (2) Enrichment Pass: marketing confirms data completeness before routing; (3) Routing: lead is assigned to the correct rep using deliberate territory logic; (4) Acceptance Window: rep explicitly acknowledges receipt within the agreed SLA; (5) First Contact: rep logs a personalized outreach attempt with channel, timestamp, and outcome. A handoff is only "complete" when all five stages have a logged action from the responsible party.

Stage 1: Trigger

The MQL conversion event fires. This happens when a lead crosses the agreed score threshold, submits a high-intent form (demo request, pricing inquiry), or is manually flagged by marketing as ready for sales outreach.

The trigger should be unambiguous. If the threshold is "score ≥ 65," then any lead at 65 or above triggers the handoff, not "approximately 65" or "65 unless the rep thinks the company is too small." Discretion at the trigger stage introduces inconsistency that makes it impossible to measure handoff performance accurately. For teams that haven't locked down what qualifies a lead, the MQL definition framework is the right starting point before you configure the trigger.

Stage 2: Enrichment Pass

Before the lead routes to sales, marketing or an automated enrichment step confirms that the contact record is complete. Required fields vary by team, but at minimum: first name, last name, business email, company name, company size band, and the trigger event that caused the MQL conversion.

A lead with missing data is not ready to hand off. A rep who receives a lead with only a first name and a Gmail address cannot do meaningful outreach. Marketing is responsible for data completeness before the clock starts on sales' SLA.

Stage 3: Routing

The lead matches to the correct rep or queue based on territory, segment, or ICP criteria. This is not a coin flip or a round-robin default. Routing should reflect deliberate logic: which rep owns this territory, which rep specializes in this company size or vertical, which queue handles overflow.

Routing errors (leads going to the wrong rep, leads going to an unmonitored queue, leads sitting in a queue nobody checks) are among the most common causes of handoff failure. Review your routing rules quarterly against your current territory and rep structure. Your lead distribution strategy should feed directly into the routing logic so every new lead lands with the most appropriate rep.

Stage 4: Acceptance Window

The assigned rep acknowledges receipt of the lead within the agreed SLA. This is a discrete action, not passive receipt. The rep should confirm: "I've reviewed this lead and I'm accepting it for outreach" or "I'm rejecting it with this documented reason."

The acceptance window is where accountability is established. If reps can receive leads without acknowledging them, you have no visibility into whether the lead was seen, reviewed, or intentionally ignored. Build the acknowledgment requirement into your CRM workflow. Don't rely on reps doing it voluntarily.

Stage 5: First Contact

The rep makes a personalized first outreach attempt within the agreed timeframe (see the five-minute response SLA for high-intent leads). The attempt is logged in the CRM with the channel used, the date and time, and the outcome (reached, left voicemail, no answer, auto-reply received).

Logging is not optional. If the first contact attempt isn't in the CRM, it didn't happen for the purposes of measurement and accountability. This is the data that feeds the closed-loop reporting that marketing needs to calibrate lead quality over time.

What Marketing Must Provide at Handoff

The lead record that arrives at sales should answer three questions a rep needs before making first contact: Why did this lead qualify? What do we know about the company? What has this person done with our content and channels?

Lead score breakdown (fit + intent + behavior). Don't pass a single score number. Pass the breakdown. A score of 72 that's mostly fit attributes (right company size, right industry, right title) means something different than a 72 that's mostly behavioral signals (high engagement, multiple page visits, downloaded the pricing guide). Sales needs to know the composition, not just the total. This breakdown also helps reps apply opportunity entry criteria correctly: a fit-heavy score may qualify for pipeline while a purely behavioral score needs more discovery first.

Activity trail. Pages visited, content downloaded, emails opened and clicked, events attended, chat conversations, trial activity. This is the context that transforms a cold call into a relevant conversation. "I saw you were looking at our enterprise pricing page last week, so I wanted to understand what you're evaluating" is a different opener than "I noticed your company is in our system."

Company context. Industry, company size, estimated revenue, known tech stack (from enrichment), any relevant news about the company (recent funding, headcount changes, new leadership). This is the firmographic picture the rep needs to know whether this lead fits the ICP and how to frame the outreach.

Any direct interactions. Chat conversations, demo requests, event attendance, any touchpoint where the lead and your team exchanged information directly. These are gold. The rep should reference them explicitly in first contact.

This context package can be assembled from MAP activity data and enrichment tools. It should arrive in the CRM record, not in a separate Slack message or email that gets lost.

What Sales Must Do After Acceptance

Accepting a lead is not the same as working a lead. Define the post-acceptance obligations explicitly.

Initial research (don't contact blind). Before the first outreach, the rep should spend 3-5 minutes on the company's website and LinkedIn profile. This isn't deep research. It's enough to understand what the company does, who they are, and whether the context provided by marketing is consistent with what the rep can see. A rep who calls a $5M e-commerce company and says "I know you're in enterprise" because the enrichment data was wrong destroys the first impression.

Personalized first touch within SLA. The first outreach should reference something specific: a content piece they downloaded, the problem they mentioned in a chat, the industry their company is in. Generic "just wanted to reach out" emails are not acceptable first touches on handoff leads. Marketing has provided the context. The rep is expected to use it.

Log the outcome: accepted, contacted, rejected with reason. Every lead needs a disposition within the SLA window. One of four outcomes should be logged: accepted and contacted, accepted and attempted (no answer), deferred with explanation (lead requested later contact), or rejected with documented reason (bad data, wrong person, competitor, out-of-territory). Silent ignoring is not a category.

The rejection reason is especially important. When marketing sees that 30% of rejections cite "wrong title," that's signal to recalibrate the ICP or scoring model. When sales logs rejections without reasons, that signal disappears.

Common Failure Modes

Most handoff breakdowns follow predictable patterns. Knowing them lets you build prevention into the process design.

Black hole handoffs. The lead is passed. Nobody acknowledges it. Nobody rejects it. It sits in a queue or sits on a rep's list and ages out without contact. This is the most expensive failure mode. It wastes the lead acquisition cost and destroys marketing's pipeline contribution metric silently. Fix: require explicit acknowledgment with a time-boxed SLA, automated escalation if acknowledgment doesn't happen within 2 hours.

Partial data at handoff. The rep receives a lead with a first name, a company name, and a score. No activity trail, no enrichment, no trigger context. They have no idea why this lead qualified. They call cold. The call doesn't go well. They reject the lead and blame marketing quality. Fix: build a pre-flight checklist (below) that prevents routing until data requirements are met.

Score gaming. Marketing inflates scores to hit MQL quota. A lead with minimal fit gets pushed over the threshold by counting low-signal behaviors (email opens, a single page visit) as high-intent. Sales discovers this pattern after a few weeks of poor conversion. They stop trusting MQL designation entirely. Fix: separate the measurement of MQL volume from the threshold logic. MQL quota should not be a marketing metric that creates incentive to game the model. Forrester's report on when good scoring models go bad names incentive misalignment as the top driver of scoring system collapse.

Silent rejection. The rep receives the lead. Reviews it. Decides it's not worth working. Doesn't log a rejection. Just does nothing. The lead sits. Marketing thinks it's in progress. It isn't. Fix: automate escalation for leads that reach 4+ hours without activity. A no-activity flag in the CRM surfaces silently rejected leads for inspection.

Tooling Requirements

The CRM is the system of record for handoff execution. The MAP is where the trigger fires and the score lives. These two systems need to stay synchronized.

CRM must capture:

• MQL conversion timestamp (when did the lead cross the threshold?)
• MQL trigger reason (score threshold hit, demo request, manual flag)
• Routing decision (which rep was assigned, which rule applied)
• Rep acceptance timestamp
• First contact attempt timestamp, channel, and outcome
• Rejection reason if applicable

MAP maintains:

• Score history and score breakdown by dimension
• Activity trail and behavioral timeline
• Lead source and campaign attribution

The handoff data gap happens when these systems aren't synchronized: the CRM shows a rep accepted a lead but the MAP still shows it as MQL status, or the MAP score updated but the CRM field didn't reflect the change. Audit the sync between systems when you implement a new handoff process. Most integration gaps aren't visible until you look for them.

Handoff Pre-Flight Checklist

Marketing should confirm these items before triggering the handoff to sales. If any are missing, the lead should go to a data-completion queue rather than routing to a rep.

• Business email address (no Gmail, Yahoo, or Hotmail)
• First and last name complete
• Company name populated
• Company size band populated (or enrichment attempted)
• MQL trigger event logged (which action crossed the threshold)
• Lead score breakdown available (not just total score)
• Activity trail includes at least one specific behavioral signal
• Routing rule identified (which rep or queue this routes to)
• Contact deduplication check run (no duplicate records)

This checklist takes less than a minute to complete for automated workflows. Build it into the MAP trigger logic so the routing step only fires when all fields are satisfied.

Metrics to Track Handoff Health

These five metrics tell you whether your handoff process is working. Review them weekly in the lead quality call.

MQL acceptance rate. Percentage of MQLs that sales accepts vs. rejects. Target: above 70%. Below 50% signals that the MQL definition is not aligned with what sales considers sales-ready.

Time-to-first-contact. Average time from MQL conversion to first logged outreach attempt. Target depends on lead type: demo requests should be under 5 minutes, standard MQL threshold leads under 1 hour. This metric reveals routing delays, rep queue monitoring gaps, and SLA adherence.

MQL-to-opportunity conversion rate. Percentage of accepted MQLs that become pipeline opportunities. This is the output metric. It tells you whether the overall handoff and qualification process is producing real pipeline, not just CRM activity.

Rejection rate by source. Which lead sources have the highest rejection rates? Content syndication leads being rejected at 60% while direct inbound converts at 30% tells you something important about which channels are worth the investment.

Black hole rate. Percentage of MQLs with no activity logged within 24 hours of assignment. A black hole rate above 10% indicates a systemic problem with rep queue monitoring or SLA enforcement.

How to Fix a Broken Handoff Process

If you inherit a broken handoff with high rejection rates, low acceptance, and frequent disputes, diagnose before prescribing.

Question 1: Is the quality problem in the scoring model or the handoff process?

Run the acceptance rate broken down by score band. If leads with scores over 80 are being rejected at 40%, the model may be decayed and not reflecting current ICP. If leads with scores over 80 are being accepted but not converting, the routing or follow-up process is the problem. These need different fixes.

Question 2: Where in the five stages is the breakdown occurring?

Is the stage 2 enrichment incomplete (data quality)? Is stage 3 routing sending leads to wrong reps (routing rule errors)? Is stage 4 acceptance not happening (SLA not enforced)? Is stage 5 first contact being logged but generic (rep training gap)? You can't fix the handoff without knowing which stage is failing.

Question 3: Do both teams agree on what "done" looks like?

Ask marketing: "When is a handoff complete?" Ask sales: "When do you consider a lead handed off to you?" If the answers are different, you've found the governance gap. Document the agreed definition. Review it together in the next lead quality call.

Rework Analysis: Based on the 5-Stage Handoff Process and industry benchmarks, teams that implement an explicit handoff SLA with automated acceptance tracking reduce their black hole rate from an industry average of ~40% to below 10% within two quarters. Leads passed but never acknowledged drop sharply once stage 4 accountability is in place: requiring explicit rep acceptance rather than passive receipt. Without it, black holes are invisible until a quarterly review surfaces the problem. Rework's pipeline management tools track MQL conversion timestamp, routing assignment, rep acceptance, and first-contact logging in a single record, giving both marketing and sales real-time visibility into whether the 5-Stage Handoff Process is executing correctly for every lead. See rework.com/pricing for current plan details.

A Process Both Teams Can Stand Behind

A clean handoff process isn't a marketing gift to sales, or a sales demand imposed on marketing. It's the infrastructure both teams need to know whether the revenue system is working.

Marketing needs the closed-loop data (acceptance rates, rejection reasons, conversion outcomes) to calibrate the lead scoring model and justify budget decisions. Sales needs the context, the routing accuracy, and the SLA structure to work leads efficiently instead of doing their own qualification from scratch.

When both teams have what they need from the handoff, the conversation shifts from "marketing sent us garbage" and "sales isn't working our leads" to "here's the conversion data, what's the threshold telling us, and where do we adjust?" That's the conversation revenue teams need to be having. McKinsey's research on B2B sales performance identifies sharper qualification discipline and tighter handoff alignment as among the highest-leverage changes a revenue team can make.

Start with the pre-flight checklist. Define your five stages. Set the SLA using the marketing-sales SLA template and document qualification criteria in the MQL-SQL agreement template. Measure the five metrics. The rest gets easier from there.

Frequently Asked Questions

What is a clean MQL-to-SQL handoff?

A clean handoff is the successful completion of all five stages in the 5-Stage Handoff Process: trigger (unambiguous MQL conversion event fires), enrichment pass (marketing confirms data completeness), routing (lead assigned to the correct rep), acceptance window (rep explicitly acknowledges receipt within the SLA), and first contact (personalized outreach attempt logged with timestamp and outcome). A lead that was passed but never acknowledged is not a clean handoff. A lead that was accepted but never contacted is not a clean handoff. Both sides have to close their loop.

What are the most common MQL handoff failure modes?

The four most common are: (1) black hole handoffs, where leads are passed but never acknowledged or rejected, accounting for ~40% of MQL volume in misaligned organizations; (2) partial data at handoff, where the rep receives a lead without activity context or enrichment, making meaningful first contact impossible; (3) score gaming, where marketing inflates scores to hit MQL quota, destroying sales trust in the MQL designation; (4) silent rejection, where the rep reviews the lead, decides it's not worth working, and does nothing without logging a rejection reason. Each has a specific process fix; they are not motivation problems.

What should marketing provide at handoff?

Marketing should provide three things before the clock starts on sales' SLA: (1) lead score breakdown (fit plus intent plus behavior composition, not just a total score), (2) activity trail (pages visited, content downloaded, emails engaged, chat conversations, trial activity: the context that turns a cold call into a relevant conversation), and (3) company context (industry, company size, estimated revenue, known tech stack, relevant company news). This context package should live in the CRM record, not in a separate Slack message.

How do you measure MQL handoff health?

Track five metrics on a weekly basis: MQL acceptance rate (target: above 70%), time-to-first-contact (target: under 5 minutes for demo requests, under 60 minutes for standard MQL leads), MQL-to-opportunity conversion rate (the output metric), rejection rate by lead source (reveals which channels are underperforming), and black hole rate (percentage of MQLs with no logged activity within 24 hours of assignment, target: below 10%).

What is a black hole handoff?

A black hole handoff is when a lead is routed to a rep and receives no response: no acceptance, no rejection, no contact attempt, no logged reason, and ages out of the queue without any record of what happened. SiriusDecisions research estimates that black hole handoffs account for approximately 40% of total MQL volume in misaligned revenue organizations. The fix is a two-part automation: an explicit acceptance requirement within a time-boxed SLA, and an automated escalation that fires when a lead has had no activity for 4+ hours.

What data should sales log after first contact?

Four fields: (1) first contact attempt timestamp and channel (phone, email, direct message), (2) first contact outcome (reached, voicemail, no answer, auto-reply received), (3) lead disposition (accepted and contacted, deferred with explanation, or rejected with documented reason), and (4) rejection reason if rejecting (wrong person, bad data, competitor, out-of-territory, timing). The rejection reason is especially important: it feeds back to marketing as signal for scoring model calibration. Silent rejections without logged reasons make the closed-loop feedback system blind.

Learn More

• MQL Definition Framework
• SQL Definition and Acceptance
• Handoff Documentation Checklist
• Five-Minute Response SLA
• Marketing Sales SLA Template
• MQL-SQL Agreement Template
• Marketing Sales Alignment Glossary