Responding to a lead within five minutes lifts your contact rate by 900 percent, and a call after thirty minutes cuts the chance of closing by around 80 percent. Those figures come from the lead response research aggregated by Marketing LTB, and they sit on top of what Harvard Business Review found in its study of online sales leads. Most companies respond far too slowly, and qualification outcomes deteriorate sharply as response time grows.
The mql to sql handoff is where that clock starts. Marketing scores a lead, decides it is ready for sales, and then somebody has to notice, pick it up and assign an owner. In most teams that somebody is a person doing it by hand, so the pipeline goes quiet between the score and the first call. Sales teams ignore 48 percent of the leads they receive from marketing, according to the same aggregated research, usually because the handoff never happens.
Gartner's work on the B2B buying journey explains why the rep still matters. 75 percent of B2B buyers prefer a rep-free sales experience, yet buyers are 1.8 times more likely to complete a high-quality deal when they use supplier-provided digital tools together with a rep. The fix keeps the rep in the loop and makes sure the lead reaches them while it is still hot.
This post walks through the same handoff on Pipedrive, Zapier and Slack, so a scored MQL reaches the right salesperson within seconds.
Why the mql to sql handoff goes cold
HubSpot's 2026 State of Marketing report, based on more than 3,400 marketers, ranks lead-to-customer conversion as the second most important KPI across businesses of all sizes. The handoff sits between those two words, and it is where that metric gets won or lost. Three things usually go wrong.
Nobody owns the moment between score and first touch. Marketing's job ends at the label, sales' job starts at the phone call, and the space in between belongs to no one. The lead often arrives with no context, a name and an email rather than a reason to call, and there is no feedback loop, so marketing keeps passing over leads that sales quietly ignores.
What you'll need
- A Pipedrive account with the Leads Inbox switched on. The inbox keeps unqualified leads separate from deals, which gives the handoff a clean boundary.
- A Zapier account. The free plan includes 100 tasks a month, and routing a lead consumes 5 tasks as of June 2026, so most teams end up on a paid plan.
- A Slack workspace with a channel for sales leads.
- The list of sales reps who take routed leads, plus their Pipedrive owner fields.
Step 1: Score the MQL in Pipedrive
Scoring decides who crosses the line. Companies using lead scoring improve close rates by 30 to 70 percent, per the aggregated research, and the improvement only shows up if the score drives the handoff. The score can be a Pipedrive lead label such as SQL-ready or a numeric field, and the threshold means this lead is now sales' job.
Define what qualifies
Set the criteria in plain terms before you build anything. Company size, industry, budget signal, a demo request, two engaged touches in the last fortnight. The Zapier filter in the next step uses the exact same criteria.
Mark the boundary with a lead label
Lead labels classify leads in Pipedrive's Leads Inbox. Create a label called SQL-ready, or reuse one you already have, and apply it when a lead meets the criteria. That label is the trigger the automation listens for. If you want the scoring itself automated, our guide to AI lead scoring that keeps prospects warm shows the same boundary built with a reasoning step.
Step 2: Route the handoff to Slack with Zapier
Two Zaps cover the handoff. The first watches for a lead that crosses the threshold, the second tells the team.
Watch for the qualifying lead
Create a Zap with the New Lead trigger in Pipedrive, then add a filter so it only continues when the lead label equals SQL-ready or the score sits above your threshold. That stops the workflow firing on every inbound lead.
Assign an owner with Lead Router
Zapier's Lead Router evaluates the lead against your rules and assigns it to a rep. Strict round robin spreads leads evenly, and weighted round robin sends more leads to experienced reps and fewer to those still ramping up, per Zapier's distribution documentation. Add a fallback rep for leads that match no rule, so nothing falls through. AI lead routing for sales and marketing digs into why ownership matters more than alert speed.
Post the alert to Slack
Add a Slack action that sends a channel message carrying the lead summary, including name, company, score, source and the intent signal that qualified them. Pipedrive's walkthrough for Slack notifications shows the flow with Zapier's new-deal template, the fastest way to see the pieces working before you customise them.
One practical note on cost. Routing consumes 5 Zapier tasks per lead as of 1 June 2026, so at 50 routed leads a month that is 250 tasks. Check your plan before you build.
Step 3: Track the handoff in the CRM
The Slack message gets attention, but the CRM record is the source of truth. When a lead qualifies, convert it to a deal in Pipedrive, set the owner to the assigned rep, and add a note with the score, source and intent signal. The Leads Inbox is built for this conversion.
Then put the handoff on a stage. A deal stage called First contact gives you a number you can manage, the median time from SQL to first call. If that number sits in hours, the workflow is only doing half the job.
The table below shows what sales receives at the handoff, with and without routing.
| Manual handoff | Routed handoff |
|---|---|
| Sales hears about the lead hours or days later | The alert lands within seconds of the label change |
| A name and an email arrive, with luck a note | Score, source, intent signal and owner come with the lead |
| Leads nobody claims sit in the inbox | A fallback rep catches anything that matches no rule |
| Marketing rarely hears what happened next | Stage history in the deal record closes the loop |
What the numbers look like when it works
Response time drops from hours to seconds, the variable Harvard Business Review identified as the main driver of qualification outcomes. The dropped-lead rate goes to near zero, because every lead has an owner and a fallback. And the rep gets context, which makes the 1.8 times deal-completion advantage from Gartner reachable.
The workflow does not sell for you. It makes sure the lead arrives hot, with the information the rep needs to sound like they already know the story.
Frequently asked questions
What is an mql to sql handoff?
An MQL, or marketing qualified lead, is a lead marketing has scored as ready for sales. An SQL, or sales qualified lead, is one sales has accepted and started working. The handoff is the moment between the two states, covering the score, the assignment and the first touch.
How long does it take to set up?
A few hours. The label, the Zap and the Slack channel cover the core, and Pipedrive's own walkthrough takes about twenty minutes.
How many Zapier tasks does routing use?
Routing a lead consumes 5 tasks as of 1 June 2026, per Zapier's Lead Router documentation. A free plan's 100 monthly tasks covers roughly 20 routed leads, so teams routing more than that move to a paid plan.
What if a lead is not sales-ready yet?
Keep it in the nurture flow. Pipedrive Sequences build repeatable email and task workflows for exactly this, and our lifecycle email framework walks through the same idea with Mailchimp and Salesforce. Let the handoff fire when the score says ready.
Should the alert go to Slack or straight into the CRM?
Both. The CRM record is the source of truth, and the Slack message is the attention grabber. If a prospect asks for a demo on a Tuesday afternoon, they are probably asking your competitor too, and the team that helps first usually wins.
Can this work with a different CRM?
Yes, the pattern ports anywhere with a Zapier integration. The trigger changes and the logic stays the same.
Make the handoff the fastest part of your pipeline
If your median time from score to first touch is still measured in hours, that is the number to move this quarter. Start with the trigger, add the owner, put the message in front of the rep. Every handoff ends up visible in the CRM instead of living in someone's head.
This is the kind of workflow we wire up at Supernodes in a two-week pilot, auditing the handoff, connecting the routing and measuring first-touch time before and after.