What is a sales accepted lead (SAL)?

The SAL process begins the moment marketing sends an MQL to sales. A rep — often a BDR or SDR — reviews the lead record against a shared acceptance checklist: does the company fit the ICP? Is the contact reachable? Is the job title or seniority in scope? Is there a valid reason to believe this person is worth a conversation?

If the answer is yes, the rep accepts the lead within the agreed SLA window (typically 24–48 hours) and SAL status is logged in the CRM. Acceptance triggers an obligation: the rep commits to following up within a second, tighter SLA — often same-day or within 24 hours for high-intent leads. If the answer is no, the rep rejects with a documented reason and the lead routes back to marketing for nurture, enrichment, or disqualification.

The entire exchange — acceptance, rejection, and reason code — should live in the CRM so both teams can see the data. That audit trail is what turns the SAL stage from a bureaucratic formality into a diagnostic instrument. Without it, you have noise. With it, you have a feedback loop.

The confusion is understandable because both terms describe leads that sales is actively working. The distinction is timing and depth of commitment. An SAL is sales saying "I accept this lead and will contact them." An SQL is sales saying "I have spoken with this lead, confirmed a genuine need, authority, and budget, and this is a real opportunity worth entering into the pipeline."

In practice, an SAL becomes an SQL after a first meaningful conversation — a discovery call, a qualification call, or an in-person meeting — in which the rep validates the BANT or MEDDIC criteria (Budget, Authority, Need, Timeline; or Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). High-performing B2B SaaS teams typically convert 40–50% of their SALs into SQLs.

Think of it this way: the SAL stage answers "should we call them?" The SQL stage answers "is there a real deal here?" Collapsing the two stages removes the intermediate accountability check and makes it impossible to measure where pipeline is falling out.

The SAL stage solves a specific, expensive problem: the blame loop. Marketing generates MQLs; sales ignores them or picks through them informally; nothing gets measured; each team blames the other. The SAL stage breaks that loop by requiring an explicit decision — accept or reject — with a documented reason. Acceptance creates accountability for follow-up. Rejection creates data that improves lead quality.

Forrester has called SAL "the most important and most overlooked step in the demand creation process." The data supports that: MarketingSherpa found 61% of B2B marketers send all leads directly to sales, yet only 27% of those leads are actually qualified. Without a formal acceptance step, the other 73% simply vanish into rep inboxes with no measurement and no feedback.

Teams skip it because it feels like friction. Adding a gate slows things down, and when sales is under quota pressure they'd rather dial than log a decision. The irony is that the gate is what makes the dialing productive — reps work better lists and marketing learns what good looks like. The SAL step typically takes less than five minutes per lead; the pipeline intelligence it generates is worth far more.

Forrester's research defined three valid categories for SAL rejection, and they are deliberately narrow. A procedural rejection means the lead was routed to the wrong rep or team — wrong territory, wrong segment, wrong product line. A clerical rejection means the contact record is incomplete or inaccurate — bounced email, missing phone number, duplicate record. A definitional rejection means the lead does not meet the agreed ICP criteria: wrong industry, wrong company size, wrong geography, or below the seniority threshold the teams agreed on.

Anything else — "they seemed cold," "bad timing," "didn't feel like a deal" — is not a valid rejection reason at the SAL stage. That determination comes later, after contact, and it is called disqualification (resulting in SQL-Not Qualified), not rejection. The distinction matters because it prevents reps from cherry-picking and ensures every rejected lead goes back to marketing with actionable feedback rather than into a black hole.

A SAL rejection rate above 30% is a signal to investigate: either marketing's scoring is miscalibrated, or the ICP criteria the teams aligned on are not reflected in what marketing is actually generating. The rejection data tells you which of the two is true — and that is exactly why you capture it.

The core metric is the MQL-to-SAL conversion rate: the number of SALs divided by the number of MQLs passed to sales, expressed as a percentage. A healthy rate is above 80% — Forrester benchmarks 85% or higher for well-aligned teams. Below 70% typically means the MQL definition is too loose or marketing and sales have never formally aligned on criteria. A rate near 100% may signal the bar is set too low.

Secondary metrics include SAL response time (time between lead receipt and acceptance or rejection decision), SAL-to-SQL conversion rate (benchmark: 40–50% for high-performing SaaS teams), and SAL rejection rate broken out by reason code. That last metric is the most diagnostic — a spike in "outside ICP" rejections tells you something different from a spike in "bad data" rejections, and both require different fixes.

All of this requires that the CRM captures SAL status as a discrete lead stage. Teams that collapse MQL and SQL into a single transition cannot measure any of this and typically have no visibility into where leads are going dark between marketing handoff and pipeline creation.

The SAL stage fails most often for one operational reason: reps don't have the information they need to make a fast, confident decision. They receive an MQL record with a name, email, and a lead score — and have to spend 15–30 minutes researching the company, finding a phone number, and drafting an outreach message before they can even decide whether to accept. That research friction is why 24-hour SLAs get missed and why leads go cold.

Komo automates that research and drafting step. When an MQL arrives, Komo monitors signals around the account, pulls sourced context — recent news, funding, leadership, hiring signals — and prepares a draft outreach that is ready for the rep to review. The rep sees enough to make an informed accept-or-reject decision in minutes, not hours.

The human stays on every send that matters. Komo handles the detection, research, and drafting — the repetitive work between the CRM and the inbox — while the rep stays in control of what goes out the door. The result is a faster, higher-quality SAL process without adding headcount or burning rep time on research that should be automated.