Picture the usual handoff. Marketing passes an MQL to a rep, and nobody asks the rep to say yes. A sales accepted lead is that yes. The rep looks at the lead before the first call, confirms it meets the criteria both teams agreed on, and takes ownership. It should take no more than a few minutes. Skip it, and a bad lead and an ignored lead look exactly the same in your reports.
This post covers what the stage is, the few reasons a rep should be allowed to reject a lead, the follow-up clock that acceptance starts, how to give the stage a home in your CRM, and the three numbers worth reporting.
What a sales accepted lead is, and what it is not
SiriusDecisions, the research firm whose Demand Waterfall debuted in 2006 to define the stages and handoff points in lead management, described the stage in a 2012 post. It said the sales accepted lead (SAL) stage is where inside, field or channel sales formally accept the leads they receive. The acceptance rests on a service-level agreement that spells out what a sales-ready lead looks like and what sales must do next, and by when.
So the rep who accepts a lead is not saying the deal is real. They are saying the lead matches the definition. The same post is specific about timing: leads should be accepted or rejected “prior to attempting contact.” Disqualification, it said, comes later, only after the rep has contacted the lead and learned there is no interest, need or budget. That is the practical line between the SAL and the SQL. Acceptance happens before the conversation. Qualification happens after it.
Put the stages in order and the gap shows. An MQL is marketing’s claim that a lead is ready. In the way we use the terms, an SQL is sales’ verdict after talking to the buyer. The SAL sits between them and records the moment ownership changed hands. Without it, you cannot tell whether a lead that never became an SQL was a poor lead or a lead nobody called.
When a rep may reject a lead
Acceptance only works if rejection is rare and specific. SiriusDecisions allowed only “a handful of basic reasons,” and gave three examples.
Procedural. The lead went to the wrong person. Wrong territory, wrong segment, a partner account routed to a direct rep. This is a routing bug, and it belongs to whoever owns the routing rules, not to the rep.
Clerical. The record is incomplete or wrong. No company, a personal email, a phone number that belongs to a switchboard in another country. The fix sits in the form, the enrichment step or the import.
Definitional. The lead does not meet the agreed thresholds for target market, activity or lead level. A student who downloaded a guide, a company below your size floor. This one is feedback on the MQL definition itself, which is why it deserves its own reason code. If you are rewriting that definition, our post on the marketing qualified lead definition walks through who signs it and how to rewrite it in one meeting.
Notice what is missing from the list. “Not interested” is not a reject reason. Neither is “no budget.” SiriusDecisions drew that line clearly: rejection is different from disqualification, which should happen only after the rep has contacted the lead. A rep who rejects a lead for lack of interest before speaking to anyone is guessing, and the guess disappears from your data.
Rejected leads should not die in the rep’s queue either. The 2012 guidance was to route them back automatically to marketing or teleprospecting, so the record can be fixed, nurtured or resubmitted.
The clock starts at acceptance
Data table
| Measure | Value |
|---|---|
| best practice for the first follow-up | 24 hours |
| the advisable limit | 72 business hours |
Acceptance is also a promise. Once a rep accepts, they owe a first follow-up inside a set window. SiriusDecisions put numbers on it: no more than 72 business hours is advisable, and 24 hours is best practice.
Those numbers are more than a decade old, and your team may pick a tighter window, especially for demo requests. The point is that the window exists and is written down. Before acceptance, a lead waiting in a queue is marketing’s problem. After acceptance, it is the rep’s. The timestamp on the acceptance is what lets both sides see which side of that line a stalled lead is on.
The window only works if the check itself is fast. SiriusDecisions said acceptance “should take no more than a few minutes of sales time.” If your reps need twenty minutes of research to accept a lead, the criteria are too vague, and that is a definition problem, not a sales problem.
Where the SAL lives in your CRM
Before you can report on the stage, it needs a home in your CRM. HubSpot is a useful example. Its knowledge base lists the default lifecycle stages in order: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other. Marketing Qualified Lead comes directly before Sales Qualified Lead in that list.
HubSpot does give you a place for sub-stages. According to its documentation, the Sales Qualified Lead stage “includes sub-stages that are stored in the Lead Status property,” with default options such as New, Open, In Progress, Attempted to Contact, Connected, Unqualified, Bad Timing and Open Deal. HubSpot also lets you customize those defaults or create your own lifecycle stages.
That leaves two workable setups. You can add a custom lifecycle stage between MQL and SQL. Or you can keep the default stages and record acceptance in properties: an accepted date, an accepting rep and a reject reason with a short, fixed list of values. The second option is lighter and usually enough. Either way, the three things you need on the record are the same: who accepted, when, and if rejected, why.
Whatever you build, write the rules down where both teams can read them. The acceptance criteria and the follow-up window belong in the same agreement as the rest of your sales and marketing alignment work, next to the return path for rejected and disqualified leads.
What to report once the stage exists
Three numbers, reviewed together every month.
Acceptance rate. Accepted leads divided by leads delivered. SiriusDecisions told teams to strive for 90% or better, and said lower rates typically point to a breakdown between marketing and sales. A low rate is useful. It tells you where the definition and the reality disagree.
Data table
| Measure | Value |
|---|---|
| acceptance rate or better | 90% |
| example reject reasons it named | 3 |
Time to acceptance and time to first touch. Two timestamps, two gaps. A long wait before acceptance points at the queue or the routing. A long wait after it points at capacity or habit.
Reject reasons by source. Split the rejections by campaign, channel and form. A webinar that produces definitional rejects is buying the wrong audience. A form that produces clerical rejects needs a field fixed. This is the report that turns the stage into a feedback loop for demand generation instead of another box on the funnel chart.
In 2012, SiriusDecisions called the SAL “the most important (and most overlooked) step in the demand creation process,” and said it is typically overlooked because it is viewed as unnecessary and cumbersome. Try it for one quarter, and look at how many of your leads a rep actually opened.
FAQ: sales accepted leads
What is a sales accepted lead?
A sales accepted lead is an MQL that a sales rep has reviewed and accepted as meeting the agreed criteria, before making contact. Acceptance transfers ownership from marketing to sales and starts a follow-up clock.
What is the difference between an SAL and an SQL?
An SAL is accepted before the rep contacts the lead, based on the agreed definition. In the way we use the terms, an SQL comes after the rep has spoken to the buyer and found a real opportunity. SiriusDecisions likewise kept disqualification for after that first contact.
What is the difference between MQL, SAL and SQL?
The MQL is marketing’s judgment that a lead is ready. The SAL is sales’ acknowledgment that the lead fits the definition and is now theirs. The SQL is the rep’s verdict after a conversation. The three stages run in that order.
Why would sales reject a lead?
SiriusDecisions allowed only a handful of basic reasons, and gave procedural (routed to the wrong rep), clerical (the record is incomplete or wrong) and definitional (the lead misses the agreed thresholds) as examples. Lack of interest or budget is a disqualification, decided after contact, not a rejection.
How fast should sales follow up on an accepted lead?
SiriusDecisions advised no more than 72 business hours and called 24 hours best practice. Your team may choose a shorter window, for demo requests for example. What matters most is that the window is written down and measured.
What is a good lead acceptance rate?
SiriusDecisions told organizations to strive for 90% or better, and said lower rates typically indicate a breakdown between marketing and sales. Read the reject reasons before trying to raise the rate.
How do you track sales accepted leads in HubSpot?
HubSpot’s default lifecycle stages include Marketing Qualified Lead and Sales Qualified Lead, and HubSpot lets you create your own stages. You can add a custom lifecycle stage between the two, or record acceptance in properties such as an accepted date and a reject reason.
COSEOM Team
COSEOM is a multilingual B2B growth agency. Since 2008 the COSEOM team has run international SEO, generative engine optimization, paid media and demand generation programs for B2B software and technology companies across their target markets. We publish our research, playbooks and product guides here. More about COSEOM
