Sales acceptance and rejection

Treat every handoff as a decision with a recorded outcome. The reviewer decides whether the opportunity belongs in active pipeline, needs clarification, or should be rejected, then records a reason another person can inspect. Formal accept or reject decisions provide operational data on lead quality, response time, and demand generation performance.¹ Accepted pipeline is the sales team's downstream confirmation that an opportunity belongs in the funnel.²

Set the decision rule

The outcome

If meets the agreed standard

Use accept

If a material gap blocks

Use return

If opportunity fails the standard

Use reject

The outcome

• If meets the agreed standard, Use accept
• If a material gap blocks, Use return
• If opportunity fails the standard, Use reject

Before reviewing individual records, agree on what accept, reject, and return mean in your process. This prevents a routed opportunity from sitting in an undefined middle state.

A Sales Accepted Lead is the formal handoff point where sales acknowledges receipt of a lead and commits to working it under agreed service levels.³ Acceptance confirms that the lead has enough quality, timing, and fit to warrant sales resources.⁴ The Sales Accepted Lead stage sits between MQL and SQL, with SQL following a sales discovery conversation.⁵

Write the sales acceptance definition before reviewing records and make the outcome visible in the process.⁶ Use accept when the record meets the agreed standard and sales is prepared to pursue it. Use return when a material gap blocks a sound decision. Use reject when the opportunity fails the standard and needs a recorded reason.

Run the review

Review every handoff in the same order. Start with why the opportunity entered the workflow, then make the decision.

1. Open the handoff record in the CRM before deciding.⁷ Read the original reason for routing, the qualification notes, and the requested next action. Inspect the handoff last and ask, "Did sales accept the reply for the same reason the account entered the workflow?"⁸

2. Review the firmographic data, engagement history, and qualification notes attached to the record.⁹ Sales acceptance means sales has validated the lead against its engagement standards.¹⁰ Ask what makes the account fit, what shows active interest, which contact can be reached, and what the handoff promised.

   Make the decision when those answers are present in the record. The SQL acceptance rule calls for confirmed ICP fit, active interest, and a valid contact within the first-contact SLA.¹¹ If an answer is missing, decide whether the gap can be clarified or the record fails the standard.

3. Accept when active pursuit is clear. Acceptance moves the referral to the next stage and indicates a plan to actively engage with the customer to address the customer's need.¹² Treat the status as a commitment to work the opportunity, not just as a receipt marker. When acceptance creates a qualified opportunity, that opportunity is a new sales opportunity entered in the CRM and accepted into pipeline by the AE.¹³

4. Return the handoff when a Blocking or High-severity gap affects scope, technical feasibility, customer ownership, or the agreed timeline.¹⁴ Record the missing detail so the sender knows what to resolve. Ask for the smallest clarification that lets the reviewer make a clean accept or reject decision.

5. Every routed lead needs either an acceptance or a coded rejection reason in the lead record.¹⁵ Record the acceptance or rejection date, the rejection reason, and any associated opportunity.¹⁶ Choose a reason that tells the next reviewer what failed, such as fit, timing, contact validity, scope, technical feasibility, ownership, or timeline.

Close the record

The decision is incomplete until the record shows what happens next. Keep the status, reason, and next action together so another person can understand the decision without reconstructing the handoff.

Sales commitments can include accepting or rejecting a qualified lead, recording the reason, and making the agreed contact attempts.¹⁷ For an accepted record, write the agreed contact action and proceed with it. For a returned record, attach the clarification request to the handoff. For a rejected record, keep the coded reason specific enough to support later review.

Read the pattern after review

Individual decisions show what happened to one opportunity. Grouped results show whether the problem sits in qualification, response, routing, or follow-up.

The Sales Accepted Lead stage establishes measurable service expectations and clear ownership that can be optimized over time.¹⁸ It also enables tracking of sales response times and follow-up commitments against agreed service levels.¹⁹ Accepted leads provide data for measuring marketing's contribution to pipeline and revenue.²⁰ SAL to SQL conversion rates show the quality of marketing-qualified leads and sales effectiveness.²¹

Compare acceptance rate with response timing. A weak acceptance rate combined with on-time response points toward targeting, offer, or qualification.²² If SDR-created opportunities convert far worse than AE-created opportunities, track win rate by opportunity creator to expose a possible gap in the acceptance criteria between the roles.²³

What not to do

These failures make the status meaningless or hide why the process needs attention.

• Do not let a routed lead disappear into silent rejection. The Sales Accepted Lead stage exists to address sales representatives rejecting marketing leads without documenting why.²⁴
• Do not let marketing and sales hand ownership of the middle of the funnel to each other. Both teams should be involved.²⁵
• Do not pass leads that sales never touches and then expect clean attribution. That pattern creates friction and makes pipeline attribution impossible.²⁶
• Do not leave out the Sales Accepted Lead stage and force the team to rely on cold calling to reach prospects. Without a clear process for determining warm leads, sales teams tend to rely on time-consuming cold calling.²⁷