Marketing hits its MQL target, sales calls the leads junk, and both teams point fingers across the same pipeline. The fix is a stage most funnels skip: the sales accepted lead. A sales accepted lead (SAL) is the formal checkpoint where sales agrees that a marketing lead is worth a rep’s time and commits to working it. SiriusDecisions, now part of Forrester, found that sales accepts only 42% of the leads marketing sources, yet companies with a formal SAL stage close more than twice as many deals from the same top-of-funnel volume. This guide explains what a SAL is, the criteria sales should use to accept one, and how the MQL → SAL → SQL handoff works in practice.
Key Takeaways
- A sales accepted lead (SAL) is an MQL that sales has formally reviewed and agreed to work, under a shared definition and a service-level agreement (SLA).
- The SAL sits between the MQL (marketing’s “interested”) and the SQL (sales’ “qualified after contact”). It is a commitment to act, not a verdict on whether the deal closes.
- Healthy acceptance rates run 70% to 90%. Forrester recommends 85% or higher once teams align on the lead definition; near-100% acceptance means the bar is too low.
- Accept on five criteria, not gut feel: data validity, ICP fit, lead score, intent and timing, and a reachable decision-maker.
- Speed decides outcomes. Leads contacted within 5 minutes are 21x likelier to qualify than those contacted after 30 minutes.
What Is a Sales Accepted Lead (SAL)?
A sales accepted lead (SAL) is a marketing-qualified lead that the sales team has formally reviewed and accepted as worth direct follow-up, because it meets a pre-agreed definition of a sales-ready lead. Acceptance is a commitment to contact the lead within a set timeframe, not a judgment on whether it will eventually close.
The term comes from the SiriusDecisions Demand Waterfall, the lead-management model Forrester now maintains. In that model, the SAL stage marks a “change in control”: the lead moves from marketing or teleservices to the quota-bearing rep who will actually carry it. When a rep accepts a lead, they are acknowledging that it matches the criteria both teams wrote into their Demand Waterfall SLA, then starting the clock on follow-up.
That distinction matters. A SAL is a procedural agreement, not a quality grade. Sales is not promising the lead is good; sales is promising to work it. The quality verdict comes later, once a rep has made contact and can judge fit, need, and timing for themselves. This is also where the SAL differs from the stages on either side of it, the difference at the heart of every MQL versus SQL handoff that runs smoothly.
Leads reach this point from the top of your funnel, where demand generation creates interest and lead generation captures it. Marketing scores and qualifies that raw interest into MQLs. The SAL is what happens next, when sales decides whether each MQL is worth its attention.
Why the SAL stage matters
Skipping the SAL stage looks efficient until you count what it costs. A formal acceptance step pays off in five ways:
- Sales and marketing alignment. A shared definition ends the “these leads are junk” argument, because both teams agreed on the bar.
- Less wasted selling time. Reps stop chasing leads that were never a fit and spend their hours on leads that cleared the gate.
- Faster follow-up. The acceptance SLA forces a response clock, and speed is the biggest lever on whether a lead converts.
- Cleaner forecasting. An accepted-lead count predicts pipeline far better than a raw MQL count sales may quietly ignore.
- A scoring feedback loop. Coded rejections tell marketing which leads to stop sending, so the model sharpens every quarter.
SAL vs MQL vs SQL: The Lead Stages Compared
MQL, SAL, and SQL are three sequential checkpoints a lead passes through, each owned by a different team and answering a different question. The MQL is marketing’s call, the SQL is sales’ call, and the SAL is the formal handshake between them.
| Stage | What it means | Owned by | The question it answers | Advances when |
|---|---|---|---|---|
| MQL — Marketing Qualified Lead | A lead whose behavior and profile cross marketing’s scoring threshold | Marketing | “Is this lead interested enough to pass to sales?” | Lead score and ICP fit clear the agreed bar |
| SAL — Sales Accepted Lead | An MQL that sales has formally accepted as worth working, under a shared SLA | Marketing → Sales handoff | “Will sales agree to work this lead?” | Sales confirms it meets the agreed definition |
| SQL — Sales Qualified Lead | A SAL a rep has contacted and verified as a real opportunity | Sales | “Is this a genuine, qualified opportunity?” | Need, budget, authority, and timing are confirmed |
So SAL vs MQL is the gap between marketing saying “this looks ready” and sales agreeing “yes, I’ll take it.” And SAL vs SQL is the gap between accepting a lead and qualifying it: the SAL is the handshake at handoff, while the SQL is the verdict after a rep has actually spoken to the buyer. These three checkpoints sit inside your wider B2B sales funnel, and skipping the SAL loses the audit trail that tells you whether marketing’s “qualified” and sales’ “qualified” mean the same thing.
Product-led teams sometimes add a fourth stage, the PQL (Product Qualified Lead), for users who hit an in-product value milestone on a free trial. A PQL can be routed straight to a SAL when a rep accepts it, so it slots into the same acceptance logic rather than replacing it.
Sales Accepted Lead Criteria: The Acceptance Gate
Sales accepted lead criteria are the specific tests a marketing lead must pass before a rep agrees to work it. Rather than leaving acceptance to a rep’s mood on a Monday morning, the strongest teams run every MQL through a fixed checklist. Call it the SAL Acceptance Gate: five criteria, each with a pass threshold both teams signed off on.
| # | Acceptance criterion | What sales checks | Pass threshold |
|---|---|---|---|
| 1 | Data validity & reachability | Real person, working business email or phone, deduped record | Verified, contactable record |
| 2 | ICP fit | Industry, company size, region, and role match the ideal customer profile | Meets ICP profile (fit score at or above target) |
| 3 | Lead score | Combined behavioral and firmographic score crosses the handoff bar | At or above the MQL-to-SAL threshold |
| 4 | Intent & timing | Recent high-intent actions: pricing views, demo requests, repeat visits | At least one buying-intent signal in the last 30 days |
| 5 | Authority / buying role | Contact sits in, or can reach, the buying committee | Decision-maker or named influencer identified |
Reading the five criteria
The first criterion is non-negotiable, and it is the one teams most often skip: a lead that is not real or not reachable can never become revenue, no matter how high it scores. Running every record through data-validation checks before fit and intent stops sales from burning hours on typo’d emails and fake form fills.
Criteria three and four lean on your scoring model. If the firmographic and behavioral signals you assign points to are well calibrated, the lead score does most of the acceptance work for you and the gate becomes a quick confirmation rather than a debate. That is the whole point of a threshold: it turns “does this feel ready?” into “did it cross the line we agreed on?”
PRO TIP
Never accept on lead score alone. A lead can score 100 points on content downloads and still have no budget authority. The score earns the lead a look; criteria 1, 2, and 5 decide whether sales should actually spend a call on it.
The MQL → SAL → SQL Handoff, Step by Step
The MQL-to-SAL-to-SQL handoff is the repeatable loop that moves a lead from marketing’s threshold to a rep’s pipeline and back again when it does not fit. Written as a workflow, it looks like this.
Workflow · within 24 hr
How to run the MQL-to-SAL-to-SQL handoff
Move every marketing-qualified lead through a single accept-or-reject loop so sales works the right leads fast and scoring keeps improving.
Confirm the MQL clears the gate
Before routing, check the lead’s score and data validity against the agreed threshold. Hold back records that fail validation so sales never sees them.
Route with context
Push the lead to the right rep or queue with the signals that triggered it: the pages viewed, the form filled, the score. Context is what makes the first call land.
Review against the SLA
Sales reviews the lead against the five acceptance criteria and makes an accept-or-reject call within the SLA window, usually 24 hours.
Accept and start the clock
On acceptance, mark the lead a SAL and make first contact fast. Speed is the single biggest lever on whether the SAL becomes an SQL.
Reject with a coded reason
Send out-of-criteria leads back with a standardized reason code (wrong ICP, no authority, bad data). Those codes are what retune marketing’s scoring next quarter.
Close the loop with rejection codes
Step five is the part most teams drop, and dropping it is expensive. Without coded rejection reasons, marketing never learns why sales bounced a lead, so the same low-fit leads keep arriving and the scoring model never gets the feedback it needs to improve. A closed loop, where every rejection teaches the model something, is what separates a handoff that gets sharper over time from one that stays broken.
Acceptance SLAs and Response Windows
A SAL means nothing without an SLA attached to it. The service-level agreement is the contract that defines what a sales-ready lead is, how fast sales must accept or reject it, and how fast a rep must make first contact once they do. Strip out the timing and “acceptance” is just a relabeled MQL sitting in a queue.
How fast should sales respond?
Two clocks run on every SAL. The first is the accept-or-reject window: best-in-class teams review within 24 hours, while 48 hours is common and 72 hours is the outer limit before a lead goes cold. The second is first-contact speed, and the data here is brutal. A 2026 benchmark of 939 B2B companies found the average lead response time is 47 hours, with only 23% of companies reaching a lead within 5 minutes and 42% taking longer than a day.
Leads contacted within 5 minutes close at 32%, versus 12% for leads contacted after 24 hours, and they are 21x likelier to qualify than leads reached after just 30 minutes.
That gap is why the SAL clock exists. The acceptance decision can wait a few hours, but the first touch cannot wait a few days, because the lead’s intent decays by the hour.
Scaling the SLA by company size
One SLA does not fit every deal. For high-velocity SMB motions, push for sub-hour first contact and a same-day acceptance window, since those buyers shop several vendors at once. For enterprise deals routed through a buying committee, a 24-hour acceptance window is realistic because the rep needs time to research the account before a credible first call. Set the windows to the deal, then hold both teams to them.
IMPORTANT
If your funnel has an “accepted” stage but no response-time SLA behind it, you do not have a real SAL stage. You have a renamed MQL that lets sales look responsive without committing to anything. The SLA is the part that creates accountability.
SAL Benchmarks: Acceptance and Conversion Rates
SAL benchmarks fall into two groups: the acceptance rate, which measures alignment, and the downstream conversion rate, which measures lead quality. Track both, because a high acceptance rate with weak conversion usually means the bar is too low.
Acceptance rate benchmarks
The acceptance rate is the share of marketing-sourced leads that sales agrees to work. Forrester’s research puts the healthy range at 70% to 90%, and recommends targeting 85% or higher once teams align on the lead definition. The same research found the typical company only hits 42%, a sign of how often marketing and sales are still working from different definitions. The goal is not 100%: if sales accepts everything, the gate is doing no work, and a meaningful share of MQLs should be rejected with a coded reason.
Organizations with a formal SAL stage close 9.3 deals per 1,000 inquiries, versus 4.6 for those that skip it, more than double the yield from the same top-of-funnel volume. Yet only 72% of companies run a formal SAL stage at all.
SAL-to-SQL conversion benchmarks
Once a SAL is worked, conversion to SQL depends heavily on how strict your gate is, so benchmarks vary widely. A 2026 dataset of 939 B2B companies reports an average MQL-to-SQL conversion of 40%, rising to 45% for SaaS and 60% or more for best-in-class teams. Broad-pool funnels that accept loosely report rates closer to 13%, while tightly gated, ICP-filtered funnels report the higher numbers. The lesson is to compare yourself only against teams that define a qualified lead the way you do.
Common SAL Handoff Mistakes (and How to Fix Them)
Most broken handoffs fail for the same handful of reasons. Here are the ones worth auditing first, with the fix for each.
- Accepting on lead score alone. A high score with no ICP or authority check sends sales chasing engaged students and job-seekers. Fix: require all five gate criteria, not just the score.
- No coded rejection reasons. If sales rejects leads silently, marketing never learns and keeps sending the same misfits. Fix: make a reason code mandatory on every rejection.
- No response-time SLA. Acceptance without a clock is theater. Fix: attach an accept-or-reject window and a first-contact window to every SAL.
- A marketing-only definition. If sales never signed off on what “qualified” means, they will reject on principle. Fix: write the acceptance criteria together and revisit them quarterly.
- Treating the SAL as a quality verdict. Reps who think accepting a lead means vouching for it will accept almost nothing. Fix: frame acceptance as a commitment to work the lead, with quality judged at the SQL stage.
Fix these five and your acceptance rate climbs toward that 85% target on its own, because the gate finally measures the thing both teams actually agreed on.
Frequently Asked Questions
A sales accepted lead (SAL) is a marketing-qualified lead that sales has formally reviewed and agreed to work, because it meets a shared definition of a sales-ready lead. Accepting a SAL is a commitment to follow up within an agreed window, not a judgment on whether the deal will close.
A sales accepted lead is one sales has agreed to work; a sales qualified lead is one sales has already contacted and confirmed as a real opportunity. The SAL is the handshake at handoff. The SQL comes after a rep verifies need, budget, authority, and timing through direct conversation.
An MQL (marketing qualified lead) is interested enough for marketing to pass on. A SAL (sales accepted lead) is one sales agrees to work. An SQL (sales qualified lead) is one a rep has verified as a genuine opportunity. The order is MQL, then SAL, then SQL.
The 3-3-3 rule is a prospecting habit, not a lead stage. The common version is 3 seconds to earn attention, 3 minutes of research per prospect, and 3 days between follow-ups. Some coaches use 3 outcomes, 3 questions, and 3 next steps instead. It governs outreach speed, not SAL acceptance.
A healthy sales accepted lead rate runs 70% to 90%, and Forrester recommends 85% or higher once marketing and sales align on the lead definition. If sales accepts close to 100%, the bar is too low. A meaningful share of MQLs should be rejected with a coded reason.
