A sales accepted lead (SAL) is a marketing qualified lead that a sales rep has reviewed and formally accepted as worth working, based on agreed acceptance criteria. SAL marks the formal handoff between marketing qualification and sales pursuit, and is the contractual midpoint in the demand waterfall.
The status exists because not every MQL passes the sales bar. SAL adds a deliberate accept-or-reject gate so that the program tracks whether sales endorses the leads marketing is producing, separate from whether those leads later qualify into opportunities.
A new MQL routes to a sales development rep. The rep checks a short list of acceptance criteria, often firmographic fit, role title, and engagement quality, and either accepts the lead as SAL or rejects it back to marketing with a reason. The acceptance ratio (SAL divided by MQL) measures whether marketing and sales agree on what qualified looks like.
Three reasons. First, SAL exposes alignment problems quickly. A low SAL rate means marketing and sales disagree on the qualification bar, and the gap is concrete enough to fix. Second, SAL protects sales capacity. By rejecting unfit leads at the gate, sales avoids burning cycles on noise. Third, SAL creates a feedback loop. Rejection reasons feed back into scoring and acquisition, so the next cohort of MQLs is closer to what sales will accept.
The first pitfall is no rejection reason capture. Without structured rejection codes, marketing cannot improve scoring or targeting. The second pitfall is auto-acceptance. If every MQL becomes a SAL by default, the gate adds no information and the metric is theater. The third pitfall is acceptance criteria drift. If the SAL bar quietly tightens during slow periods, the rate can drop without any change in lead quality.
MQL, SQL, sales qualified opportunity, demand waterfall, lead acceptance.
SAL is sales acceptance based on lead attributes such as fit and engagement. SQL is sales qualification based on a discovery conversation that confirms fit, need, authority, and timing. SAL precedes SQL in most demand waterfalls.
Typically the sales development rep or the routing automation, applying acceptance criteria agreed jointly with marketing. Some programs use automated SAL acceptance for high-confidence segments and manual review for the rest.
Yes for most rejection reasons. Permanent disqualification should be reserved for clear ICP mismatches. A cooldown nurture flow with a recheck after 60 to 90 days preserves future opportunity at maturing accounts.
Want a tighter MQL-to-SAL gate fed by account-level intent? Book a demo of Abmatic AI.