Sales Accepted Lead (SAL)

Sales Accepted Lead (SAL) is a marketing qualified lead that sales has formally reviewed and agreed is worth active follow-up.

Also known as: SAL, sales-accepted lead, accepted lead

Sales Accepted Lead (SAL) is a lifecycle stage that confirms sales has reviewed a marketing qualified lead and committed to working it. It marks the formal handoff point between marketing and sales rather than the assumption that an MQL has been picked up. The stage exists to make the handoff visible and accountable rather than implicit, and to surface the moments when marketing and sales disagree on what a good lead looks like.

What Sales Accepted Lead Means

A Sales Accepted Lead is an MQL that a sales rep has reviewed, judged to meet the agreed acceptance criteria, and committed to working within the SLA window. The acceptance criteria are defined in the marketing-sales service level agreement and typically combine fit and engagement signals with practical rep judgment. The SAL stage sits between MQL and SQL or opportunity in the lifecycle, and the rate of MQL-to-SAL conversion is one of the cleanest indicators of marketing-sales alignment available. The stage applies in motions where the volume and stakes of MQLs warrant a formal acceptance step, which is most B2B programs operating at meaningful scale.

How Sales Accepted Lead Works

Sales Accepted Lead works as an accountability checkpoint. When a rep accepts a lead as a SAL, they agree it meets the criteria in the service level agreement and accept responsibility for follow-up within a set time. If they reject it, the reason is logged so marketing can improve targeting. The mechanics include defined acceptance criteria in the SLA, structured rejection reasons in the CRM, automated routing rules that direct rejected leads back to nurture, and reporting that surfaces both the acceptance rate and the rejection-reason mix. Strong programs review the rejection data regularly with both marketing and sales present, so the feedback loop is closed deliberately rather than gathering dust in a dashboard.

Common Pitfalls and Misconceptions

The Sales Accepted Lead stage matters because it surfaces handoff problems that an MQL count hides. A high MQL-to-SAL rejection rate is a clear signal that marketing and sales disagree on what a good lead looks like, which is a conversation worth having before more budget is spent. The mistake is to focus on acceptance rate as a target in itself, which incentivizes acceptance regardless of fit and erodes the value of the stage. The rejection reasons are the more useful output: they reveal exactly which sources, campaigns, or audiences are producing leads sales does not want.

Sales Accepted Lead in Practice

The teams that get the most from a Sales Accepted Lead stage treat the rejection reasons as the primary output, not the acceptance rate. When sales consistently rejects MQLs from a particular source for the same reason, that pattern is actionable intelligence for marketing’s targeting and message decisions upstream. A SAL stage that captures rich, standardized rejection data and feeds it back into demand planning produces better MQLs over time. A SAL stage that only tracks acceptance rate produces friction without insight, which is why mature programs design the rejection capture deliberately rather than treating it as optional metadata.

Back to the Glossary

Common questions.

What is the difference between an MQL and a SAL?

An MQL is a lead marketing considers ready for sales. A SAL is an MQL that sales has reviewed and formally agreed to work. The SAL stage confirms the two teams agree on lead quality and turns the handoff into a real commitment rather than an assumption.

What happens when sales rejects an MQL?

The lead does not become a SAL and the rejection reason is recorded. Tracking these reasons helps marketing refine scoring and targeting so future leads are more likely to be accepted, which is one of the most valuable feedback loops in the revenue motion.

Why track a SAL stage at all?

It exposes alignment gaps. A high rejection rate between MQL and SAL shows marketing and sales disagree on lead quality, which is easier to fix once it is measured. Without the stage, the disagreement plays out as quiet frustration rather than visible data.

What is a healthy MQL-to-SAL acceptance rate?

There is no universal number, but a consistently low acceptance rate signals that marketing and sales disagree on lead quality or the MQL criteria are too loose. Track the rate over time and treat a sharp drop as a prompt to revisit the shared definition rather than chasing a benchmark.

How do you set up a sales accepted lead stage?

Agree jointly with sales what acceptance and rejection mean, build the stage into the CRM with required rejection reasons, and set a service level for how quickly sales must review each MQL. Enforcement through the CRM keeps the stage meaningful rather than a formality.

How should rejection reasons be used?

Aggregate them by source, campaign, and segment, and feed the patterns back into marketing program design. If a source consistently produces leads rejected for the same reason, the issue is upstream targeting or messaging, not downstream lead handling. The loop only works if marketing actually reviews and acts on the data.

Does every team need a SAL stage?

Not always. Teams with tight marketing-sales alignment and a small, high-quality MQL flow may operate effectively without a formal SAL stage. The stage adds the most value when MQL volume is high enough that loose handoff creates measurable friction, or when marketing and sales have historically disagreed on lead quality.

Related Terms

Let’s talk about what your next quarter could look like.

Tell us what you’re working on. A senior practitioner reads it, not an SDR queue, and replies, usually within one business day.

Reviewed personally, not routed through a queue.
A conversation about what you’re actually working on, not a generic pitch.
No pressure, just a chance to talk it through.