A sales acceptance decision controls the handoff. It tells sales whether a routed opportunity belongs in active pipeline, needs clarification, or should be declined, and leaves a reason someone can inspect later. Rejection is useful only when the team can learn from it. An unrecorded decision leaves the funnel with no explanation and gives the next person no clear action. A Sales Accepted Lead is a marketing-qualified lead that sales has formally agreed to pursue as active pipeline.1
Define the acceptance rule
Set the rule before the first record arrives. Everyone involved should be able to review the same handoff and reach the same decision.
Each organization defines a Sales Accepted Lead using its own criteria.2 Write those criteria as observable checks, then agree what sales must confirm before accepting. The SAL stage sits between MQL and SQL after a sales discovery conversation.3 Sales acceptance confirms that the lead meets both marketing qualification criteria and sales readiness standards.4 Keep marketing and sales involved in defining this middle stage because responsibility often defaults from one team to the other.5
Use this sequence for each routed record:
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Queue | Whether the record met the handoff trigger and entered the handoff queue. Marketing places a lead in the queue after it meets criteria based on behavioral scoring, demographic data, or engagement thresholds6 | What caused this record to enter the queue? |
| Review | Whether the handoff record has been opened and reviewed in CRM.7 Sales usually has 24 to 48 hours to review firmographic data, engagement history, and qualification notes8 | Which facts support the acceptance rule? |
| Decision | Whether the record should be accepted or rejected against the agreed definition. Sales commitments can include accepting or rejecting the qualified lead and recording a reason9 | Does this record meet the acceptance rule? |
| Clarify | Whether a missing answer blocks a responsible decision | Which answer would let us decide? |
| Record | Whether the outcome can be inspected later. Capture the acceptance or rejection date, rejection reason, and any associated opportunity10 | Could another person understand this decision later? |
Review the record
Review the handoff against the rule and separate a qualification failure from an information gap. That distinction tells you whether to reject the record or return it for clarification.
Compare the reason the account entered the workflow with the reason sales would accept the reply: "Did sales accept the reply for the same reason the account entered the workflow?"11 A practical acceptance rule can require confirmed ICP fit, active interest, and a valid contact within the first-contact SLA.12 Use the agreed criteria and make each one easy to verify from the record.
Look for evidence that the opportunity has sufficient quality, timing, and fit to warrant sales resources.13 Check whether the contact is valid, the interest is current, and the handoff describes a need the receiving team can address. Move to the decision when the record gives you a clear answer against each required criterion.
Accept the opportunity
Acceptance commits sales to work the record. Make it when the criteria are satisfied and the next action is clear.
Accepted pipeline is the sales team's downstream confirmation that the opportunity belongs in the funnel.14 Acceptance moves the record to the next stage and indicates a plan to actively engage with the customer to address the customer's need.15 Record who owns the next action and what contact attempt follows, using the service expectation your teams agreed.
If your funnel uses SQL, apply that status only after the agreed criteria are met and sales has accepted the lead. Keep the status change close to the decision so the pipeline reflects sales intent instead of simple record creation.
Reject the opportunity
Reject a record when it fails the acceptance rule. Give the decision a reason that points to the failed condition, so the team can change the source, qualification rule, or routing logic when the same pattern repeats.
Use the rejection reason to distinguish a poor fit from a timing problem or a missing qualification signal when those distinctions exist in your agreed taxonomy. Add the reason before moving on. A vague rejection creates work for the next review and prevents a useful conversation with marketing.
When the record is rejected, keep the decision visible in the same system as the original handoff. That gives the team a clear point for reviewing whether the problem sits in targeting, the offer, qualification, or the review itself.
Return for clarification
Return a handoff when the record may qualify but the available information cannot support a decision. State what is missing and send the record back to the person responsible for supplying it.
Return the handoff when a Blocking or High-severity gap affects scope, technical feasibility, customer ownership, or the agreed timeline.16 Ask for the missing answer in the return note, then reopen the review when it arrives. Keep this outcome distinct from rejection so an information gap does not become a false quality signal.
Ask: what specific answer would change the decision? If no answer would change the outcome, reject the record and record the applicable reason. If one answer could change it, return the handoff with that request attached.
Make the decision inspectable
Record enough for someone to trace what happened and why. The team should be able to check ownership, timing, follow-up, and pipeline impact without reconstructing the handoff from memory.
The SAL stage establishes clear ownership and service-level expectations that can be measured and improved over time.17 It also enables tracking of sales response times and follow-up commitments against agreed service levels.18 Accepted leads provide data for measuring marketing's contribution to pipeline and revenue.19
Review the decision log with the same discipline as the pipeline. Look for missing dates, empty reasons, and accepted records with no associated opportunity. When a record is returned, keep the return reason visible until the gap is resolved or the record is rejected.
Read the patterns
Use acceptance and rejection patterns to improve the handoff rule, then check whether the changes affect downstream movement.
A weak acceptance rate combined with an on-time response points toward targeting, the offer, or qualification.20 Inspect those areas before assuming the review team is the problem. SAL-to-SQL conversion rates show both the quality of marketing-qualified leads and sales effectiveness.21
Read the results by rejection reason and by source of the handoff. A repeated reason gives you a concrete place to change the rule or the upstream qualification work. A rising acceptance rate with weak movement after acceptance points toward what happens after the decision.
What not to do
- Do not let sales ignore an MQL without leaving a trace. That removes the qualification system's ability to explain what happened.22
- Do not call a lead accepted until sales has reviewed it and agreed that it is worthy of active pursuit.23
- Do not allow an uncoded rejection to stand in for a decision. Every routed lead should have an acceptance or a coded rejection reason.24