MQL to SQL Handoff: 7 Written Rules That Stop Good Leads Getting Lost

Why do good leads go cold between marketing and sales? Usually because nobody wrote down the rules. A working MQL to SQL handoff needs seven of them: one definition, required fields, routing, response times, an accept or reject window, reason codes, and a recycle path. This guide gives you each rule, ready to copy.

Definition: The MQL to SQL handoff is the point where marketing passes a qualified lead to sales, and sales either accepts it as a sales-qualified lead or sends it back with a reason.

Updated November 2026

Why Leads Get Lost Between Marketing and Sales

Most lost leads do not fail on quality. Instead, they fail in the gap between two teams. Here are the five most common breaks and what each one costs.

Where it breaks	What happens	What it costs
No shared definition	Marketing sends what it counts; sales wants something else.	Reps stop trusting the queue.
Missing context	The rep gets a name and a download, nothing more.	A generic first call that goes nowhere
No owner	The lead sits in a shared queue.	Days pass before anyone calls.
No time limit	Sales follows up “when there is time.”	Interest fades before contact
Silent rejections	Bad leads are ignored, not marked.	Marketing keeps sending the same kind.

Each of these is a process problem, not a people problem. So the fix for a broken MQL to SQL handoff is a short written agreement that both teams sign.

Pass the Account, Not Just the Contact

Before the rules, one change in thinking. B2B purchases are group decisions. Forrester’s State of Business Buying 2024 found that 13 people take part in an average buying decision. In addition, 89% of purchases involve two or more departments.

That means one engaged contact rarely tells the full story. If a marketing manager and an IT lead from the same company both read your content this month, sales should see them together. As a result, the rep calls with a clear picture of who is involved and what they care about.

So match every lead to its company record before it reaches sales. Then show all engaged contacts from that account on the same record. To rank accounts by how many people are active, score engagement at the account level as well as per person.

The MQL to SQL Handoff Agreement: Seven Rules to Write Down

Put these seven rules in one shared document. Each rule has an owner and, where it matters, a time limit.

Rule 1: One Shared MQL Definition

First, write the MQL definition in one or two sentences that sales signs. Include fit (industry, company size, region, job level) and the activity that counts. For example: “A director or above at a software company with 200 to 5,000 staff in the US or UK who has requested a demo or read two buying-stage assets in 30 days. ” If your team needs a refresher, here is what counts as an MQL.

Rule 2: The Fields Every Lead Must Carry

No lead goes to sales without these fields filled in: name, job title, work email, phone number where consent was given, company, company size, country, the activity that qualified it, and the date of consent. If a field is empty, the lead stays with marketing until it is complete.

Rule 3: Route by Account Owner

Send each lead to the rep who owns that account. If no one owns it, use territory rules instead. Avoid shared queues, because a lead that belongs to everyone belongs to no one.

Rule 4: Response Times by Signal

Of course, not every lead needs the same speed. Match the response to the strength of the signal.

Lead signal	First contact target	Escalate to the sales manager after
Demo or pricing request	Within 1 business hour	4 business hours
Three or more people active from one account	Same business day	1 business day
Buying-stage content from a good-fit contact	Within 2 business days	3 business days
Early-stage content download only	Stays in marketing nurture	Not sent to sales

Rule 5: Accept or Reject Within Two Business Days

After first contact, the rep has two business days to accept the lead or send it back. Accepting turns it into a sales-qualified lead. If your teams still disagree on where one stage ends, review MQL vs SQL together and agree on the line in writing.

Rule 6: Reject With a Reason Code

A rejection without a reason teaches nobody anything. Therefore, every rejection needs one code from a short, fixed list.

Reason code	What it means	What marketing changes
Wrong person	Right company, wrong role	Tighten job title rules; find the right role in the account.
No project	Interest, but no active need	Move to nurture; review the qualifying activity.
Poor fit	Company outside the ideal customer profile	Fix targeting and form filters.
Already in a deal	The account is already in active sales talks.	Check CRM matching before routing.
Bad data	Wrong email, wrong phone, or unreachable	Review data checks and the source.
No response	Five contact attempts with no reply	Recycle with a date to try again.

Rule 7: Recycle, Do Not Delete

Rejected leads go back to marketing with their reason code and a date. Then, after 90 days, re-score them. Many “not now” leads become ready later, so deleting them throws away the pipeline you have already paid for.

What Sales Should Receive: A Lead Record Template

In practice, a name and a download are not enough for a useful first call. Instead, every lead should arrive with this record. The example below is for illustration only.

Field	Example
Contact	Head of IT Operations
Company	Logistics company, 900 staff, United States
Other people active from this account	Finance Director, Operations Manager
What they engaged with	A guide on warehouse system costs; a comparison page
Signal that qualified it	Three people active within 14 days
Likely buying stage	Comparing options
Gaps	No contact yet from procurement
Consent	Opt-in recorded, with date and source
Suggested first step	Offer a cost comparison call with the IT and finance leads together.

With this record, the rep can open the call with the problem the account is researching. That is what turns a lead into a conversation. For the full checklist sales uses next, see what makes a lead sales-qualified.

How Fast Should Sales Respond After the MQL to SQL Handoff?

Speed still matters. For example, a well-known Harvard Business Review study found that companies contacting online leads within an hour were nearly seven times as likely to qualify them as companies that waited longer. The study is from 2011 and covered online leads, so treat it as a direction rather than a rule.

Buyer behavior also points the same way. Today, buyers usually make the first contact themselves, after most of their research is done. They expect a fast and informed reply. That is why Rule 4 sets the tightest target for demo and pricing requests, where the buyer has asked to talk.

What to Measure in the MQL to SQL Handoff

Track five numbers every month. Taken together, they show whether the rules work.

Metric	How to calculate it	What a healthy trend looks like.
Acceptance rate	Leads accepted by sales ÷ leads sent	Rising, or steady at a level both teams agree
Time to first contact.	Average hours from routing to first call or email, by signal	Within the Rule 4 targets
Rejection rate by reason	Rejections per reason code ÷ all rejections	No single code grows month after month
SQL to opportunity rate	Opportunities created ÷ accepted leads	Rising as definitions tighten
Recycled leads that return	Recycled leads that later become SQLs	Steady flow back into the pipeline

The 30-Minute Monthly Review

Finally, hold one short meeting each month with a marketing lead, a sales manager, and someone from marketing ops. Keep the same agenda:

1. Review the five metrics against last month.
2. Look at the top two rejection reasons and agree on one fix for each.
3. Read three accepted leads that became opportunities and three that did not.
4. Update the MQL definition or the fields if the evidence calls for it.
5. Write down what changed, with an owner and a date.

Over a few months, this meeting does more for your MQL to SQL handoff than any new scoring tool.

How ColedaB2B Delivers Leads Sales Can Act On

As a partner, we deliver sales-qualified leads built on the criteria your sales team signs off on. Every lead goes through a three-step check that combines automated validation with human review. Each client has a dedicated Center of Excellence, and our team works in shifts for 24/5 coverage. Our 98.3% rate of acceptance reflects this process. We also never qualify a lead without an opt-in.

Want to see what sales we receive? We will share a sample lead record built on your target profile, with the fields and context described in this guide.

Request a sample lead record

FAQs: