Quick answer
A written SDR to AE handoff SLA should name four things: how long the AE has to accept or reject a meeting, what counts as a valid rejection reason, what happens to the SDR's commission clawback clock while a meeting is disputed, and who breaks the tie when the two sides disagree. Most teams write the first two and skip the last two, which is exactly where the disputes happen.
What should an SDR to AE handoff SLA actually say?
I run appointment setting through email and LinkedIn for B2B clients, and the handoff to whoever closes the meeting is where I've watched more good campaigns quietly lose trust than any copy problem. A real SLA names four things: the response window, the valid rejection reasons, what happens to the clawback clock during a dispute, and the tiebreaker. Most teams stop at the first two, often because they already have a written definition of a qualified meeting, the checklist I cover in how to structure an SDR commission plan, and assume the process around that checklist will sort itself out. It doesn't.
Why a verbal "I'll let you know" handoff breaks down
Without a written SLA, an AE who's busy or skeptical of a meeting just doesn't respond, and the SDR has no clock to point to and no record of what happened. The Bridge Group's 2025 SDR report (351 B2B companies) puts the average SDR ramp at 3.0 months, the fastest on record but still a real stretch where an SDR and the AE they're handing off to haven't built the kind of trust that makes an informal process survive its first disagreement. Across the more than 2000 meetings I've booked for B2B clients, the campaigns that kept momentum were the ones where both sides knew exactly what counted as a win before the first disputed meeting came up, not after.
The four parts a real SLA needs
- A response window. How long the AE has to mark a meeting accepted or rejected.
- A closed list of rejection reasons. Not "didn't feel right," a named, checkable reason.
- A rule for the clawback clock. What happens to the SDR's commission timeline while a meeting's status is unresolved.
- A named tiebreaker. Who decides when the SDR disputes a rejection, agreed before anyone needs it.
The response window: how long an AE has to decide
I'd start with 2 business days and adjust from there. Shorter than that and an actually busy AE ends up rejecting meetings reflexively just to stay inside the window; longer than that and the SDR is sitting on an unresolved result while the next sequence is already running. Whatever number you pick, write it down as the committed window, not an informal expectation, because an unwritten window is the first thing that slips once either side is busy.
A rejection needs a reason, not just a no
A rejection without a stated reason teaches the SDR nothing and gives them nothing to dispute. Apollo's own guide to structuring an SDR commission plan frames a qualified meeting against "a documented qualification framework" the AE checks the meeting against before accepting it, which only works if the rejection side of that same framework is just as documented. A short, closed list works better than an open text field: wrong company size or industry, no real decision influence from the contact, or no identifiable pain or trigger behind the meeting. Three or four reasons, agreed in advance, cover almost every real rejection without turning into a debate about wording.
Tip. Track which reason gets used most. A pattern of "wrong company size" rejections points at the ICP definition, not at the SDR's judgment.
The clawback clock: pause it, don't restart it
This is the part almost every commission plan I've seen skips. A plan will define when a clawback applies, a no-show, a meeting that gets cancelled before it happens, but not what happens to the clock while the meeting's qualification status itself is being argued over. If the clock keeps running during a dispute, the SDR can lose the payout on a technicality before the disagreement is even resolved. If it resets to zero once resolved, a slow AE response effectively extends the SDR's risk window for no reason connected to the SDR's own performance. The fix is to pause the clock the moment a meeting enters disputed status and resume it, from where it left off, the moment the dispute resolves. Neither side is penalized for the time the disagreement itself takes.
Who breaks the tie when SDR and AE disagree?
Name this person before the first dispute, not during it. A sales manager or whoever manages both the SDR and the AE is the usual choice, with a short response window of their own, a business day or two, so a tie doesn't become a second open-ended wait. The point of naming the tiebreaker in advance is that neither side picks the referee after they already know which way they want the call to go.
Where to track this, without buying new software
Most CRMs already have a field built for exactly this. HubSpot's own documentation describes a default Lead Status property with options including Open, In Progress, Connected, and Unqualified, sitting inside the broader Sales Qualified Lead stage, which is enough to represent accepted, pending, and rejected without adding a custom object. The SLA is a written agreement about how that field gets used and how fast, not a reason to build new infrastructure around it.
A sample SLA, written out
A starting version, meant to be edited to fit your own team rather than copied as-is:
| Part | Starting rule |
|---|---|
| Response window | AE marks the meeting Accepted or Rejected within 2 business days |
| Rejection reasons | Wrong company size or industry, no real decision influence, no identifiable pain or trigger |
| Clawback clock | Paused while status is Pending or Disputed, resumes from where it stopped once resolved |
| Tiebreaker | Shared manager decides within 1 business day of a disputed rejection |
Rolling this out without it feeling like a courtroom
Introduce it as protection for both sides, because it is. An SDR gets a clock they can point to instead of a vague "I'll check with the AE," and an AE gets a closed list of reasons instead of being asked to justify every rejection from scratch in a thread. The same framing applies whether the person booking the meeting is a dedicated SDR or an appointment setter working the role under a different title, the distinction I cover in appointment setter vs SDR. Review the rejection-reason breakdown monthly for the first quarter, since that's usually when a pattern in the data tells you to fix the targeting rather than the process.
Key takeaways
- A real SDR to AE handoff SLA names four things: the response window, the valid rejection reasons, the clawback-clock rule, and the tiebreaker.
- Most commission plans already define a qualified meeting; the SLA is the process wrapped around that definition, not a second version of it.
- Pausing the clawback clock during a dispute, rather than letting it run or resetting it, keeps neither side penalized for how long the disagreement itself takes.
- A closed, short list of rejection reasons gives the SDR something to learn from and dispute, which an open-ended "didn't feel right" never does.
- Most CRMs, HubSpot's default Lead Status field among them, already have what you need to track this without new software.
FAQ
What should an SDR to AE handoff SLA say?
It should name the response window for the AE to accept or reject a meeting, a closed list of valid rejection reasons, what happens to the SDR's clawback clock while a meeting is disputed, and who breaks the tie when the two sides disagree.
How long should an AE have to accept or reject a meeting?
2 business days is a reasonable starting point. Shorter windows push AEs toward reflexive rejections to stay inside the deadline; longer ones leave the SDR with an unresolved result while the next sequence is already running.
What happens to an SDR's commission clawback if a meeting is disputed?
The clock should pause the moment a meeting's status becomes disputed and resume from where it stopped once the dispute resolves, rather than continuing to run or resetting to zero. That keeps neither side penalized for how long the disagreement takes.
Who should resolve a disagreement between an SDR and an AE?
A shared manager, named in advance rather than picked after the dispute starts, with a short response window of their own so the tie doesn't turn into a second open-ended wait.
Do we need new software to track this, or can we use our CRM?
Most CRMs already have what you need. HubSpot's own default Lead Status field, for example, includes Open, In Progress, Connected and Unqualified options inside its Sales Qualified Lead stage, enough to represent accepted, pending and rejected without building anything new.