Two people arrive here with the same complaint from opposite ends: an SDR whose meetings keep coming back marked unqualified, and an AE who keeps inheriting a calendar invite with four lines of notes attached.
This page owns the handoff artefact, the rejection, and the argument about it. The surrounding ground belongs elsewhere: AI prompts for SDRs owns the prospecting day, lead qualification owns inbound, onboarding sales reps owns ramping, and MEDDPICC owns the framework itself.
The handoff does not fail for want of a template, it fails because you are measured on different things
Search this problem and you will be sold an artefact: a template, a checklist, a form field, an agent. Teams adopt them and the meetings keep bouncing. The reason is in the comp plan. An SDR is paid for the meeting held; an AE is paid for whether it was real. A shared document does not reconcile those — it moves the disagreement into a form.
What helps is narrower: a brief that survives a hostile read, and a way for the AE to push back in evidence rather than in tone. Everything below is one of those two.
Prompts for the brief the AE cannot reject
The brief's job is not to sell the meeting. It is to state what is known, what is not, and where each came from, so an AE reading it in ninety seconds can tell the difference.
From these notes, write a handoff brief in four sections: what the prospect said in their own words, what I inferred, what I do not know, and why this meeting is worth an AE hour. Quote directly where possible. Never move anything from the second section into the first.
That last sentence is the whole prompt. Left alone, a model promotes your inference into the prospect's mouth, and that move is what an AE smells on a thin brief.
Review this brief as a sceptical AE with a full calendar. List every claim with no source in the notes, and for each write the question I should have asked.
Run it on your own brief before sending. The questions it produces are the ones you still have time to ask.
What belongs in the brief, and the three things everyone leaves out
Most briefs carry the easy fields: company, role, pain, next step. Three things are routinely missing and each costs the AE a call.
First, how the prospect came to be on the call — cold sequence, inbound form, referral, event badge scan. The AE's opening changes entirely depending on which, and it is almost never recorded.
Second, what you promised. If you said twenty minutes, or that someone technical would join, or that pricing would arrive beforehand, the AE inherits that promise without knowing it exists.
Third, the thing that nearly stopped the meeting happening. Every booked meeting has one hesitation in it, and writing it down is worth more than any qualification score.
From these notes, extract the channel and trigger that started this conversation, every commitment I made about the next call, and the strongest hesitation the prospect expressed. Quote each. Where one is missing, write ABSENT rather than guessing.
Prompts for the AE reading a brief critically before the call
From the other side, the skill is reading a brief fast for what it does not say.
Separate this handoff brief into facts attributed to the prospect and assertions with no stated source, then list the three questions I must ask in the first ten minutes to make the meeting worth holding.
Draft a short opening that acknowledges what the prospect already told my colleague, so I do not re-ask questions they have answered.
The second prompt prevents the commonest buyer complaint about a handoff: being asked the same questions twice by the same company. Prompts for discovery calls cover the rest of that conversation and call notes into a deal update covers afterwards.
Prompts for the disagreement: when the AE says it was not qualified
This is where the relationship is won or lost, and where most teams argue about tone instead of evidence.
Given this brief and what happened on the call, write a factual account of the gap: what was claimed, what turned out true, and which claim was unsupported. No blame language and no adjectives about either person.
I am the SDR and this meeting was rejected. On this evidence, is the rejection fair? If yes, name the one thing I should have verified. If no, write two sentences I can send that argue in evidence rather than tone.
Asking a model to judge against you is the useful move. A prompt framed as help me argue my side produces an argument; one framed as is this fair produces something you can act on.
Prompts for the handoff call itself, when you get one
Where a live handoff happens, fifteen minutes is enough, and it should not be the brief read aloud.
Build a 15-minute handoff agenda for this opportunity. Three items only: the one thing the AE must know that is not in the brief, the one open question we both need answered, and who does what before the first call. No recap of the brief.
The ban on recapping is what keeps the meeting short enough to keep happening.
Prompts that find the pattern across a quarter of bounced meetings
One rejected meeting is an incident; fifteen is a system problem, and that is a manager's work. Leadership, Coaching & People Management covers that layer.
Given the briefs and outcomes for every meeting rejected last quarter, group the rejections by underlying cause rather than stated reason. Say which are a sourcing problem, which a brief-quality problem, and which a definition problem where the roles disagree about what qualified means. Rank by frequency.
The third is usually the biggest and the only one coaching cannot fix. Sales Operations, CRM & Productivity is where that definition work lives.
Why a model handed a thin CRM record will write you a confident brief anyway
This is the failure the AE is already complaining about, and automation makes it worse. Give a model three lines of notes and ask for a handoff brief and it returns a fluent, structured, fully qualified-sounding document. Every field populated, nothing flagged. It reads better than a careful brief from a careful call, because fluency is what it optimises and uncertainty is what it smooths away.
The defence is in every prompt above: require quotes, require sources, require the word ABSENT. A brief with three ABSENT fields beats one with none, and an AE learns quickly whose briefs contain the word.
AI prompts for sales, by role and stage is the map, and AI prompts for account executives picks up where this page ends. The closest categories are Prospecting & Pipeline Creation and Meeting Prep & Discovery; the full taxonomy lists them all and Browse the library → is the front door.
Take one prompt free, no account needed, at Take one prompt free. Pro is $12 per month or $89 per year, and lifetime access is $149 — See pricing.
Frequently asked questions
What should an SDR to AE handoff brief include?
The prospect's own words separated from your inferences, the channel and trigger that started the conversation, every commitment made about the next call, the strongest hesitation the prospect expressed, and an explicit list of what is not known. The last two are the ones most briefs leave out, and they are the ones an AE values most.
What are good AI prompts for a sales handoff?
Prompts that separate quoted fact from inference and refuse to merge them, prompts that review your own brief as a sceptical AE would and list every unsourced claim, and prompts that mark missing information as absent instead of guessing. Drafting prompts are less useful here than auditing ones.
Why do AEs reject SDR meetings?
Usually for one of three reasons: the prospect was never going to buy, the brief claimed more than the call supported, or the two roles disagree about what qualified means. Only the first two can be coached. The third is a definition problem and needs a manager to settle it, not better notes.
Should the SDR join the first AE call?
It helps where the SDR built real rapport or made promises the AE must honour, and hurts where it turns a discovery call into an audience. A short handoff conversation beforehand usually achieves more than attendance, at fifteen minutes rather than an hour.
How do I write a handoff brief when the CRM record is thin?
Write it thin and say so. Mark the unknown fields absent rather than letting a model fill them, and name the single question that would most change the AE's approach. A short honest brief earns trust; a complete-looking one built from three lines of notes destroys it the first time it is tested.