Building a per-client positive-reply library for AE handoff
AEs do not fail handoffs because they are lazy. They fail them when the packet is a calendar invite and a shrug.
"They're interested" is not context. The AE needs the buyer's words, the trigger that earned the reply, and the next commitment — without reconstructing your sequence from scratch.
Agencies that run many clients need a per-client positive-reply library: reusable patterns and required packet fields that stay inside each workspace.
A library is not a swipe file of lies
Unify's outbound handoff template is blunt: pass the actual reply and thread, verified account context, the trigger and message that produced the response, unresolved questions, the next commitment, and a named AE acceptance. A positive reply is a conversation state, not proof of budget, authority, need, or timing.
Your library should store how to package that, not invented case studies.
Per client workspace, keep:
- Reply categories you actually use (book, nurture, disqualify, OOO, referral) with routing owners
- Safe summary phrases that do not upgrade a polite "send me more info" into a qualified opportunity
- Required packet fields and which seat fills them
- Examples of good packets (anonymized inside the client workspace) for new SDRs
- Client-specific do-not-say notes that belong in the handoff (pricing frames the AE must not invent)
ProspectingManual's SDR-to-AE handoff checklist still holds: verified prospect context, meeting on the AE's calendar, CRM deal notes. The library is how you make that checklist identical across seats without copy-pasting tribal knowledge in Slack.
Packet fields worth standardizing
Put decision-critical fields first:
| Field | Evidence | Owner |
|---|---|---|
| Buyer reply | Link to full thread + exact inbound text | SDR / shared-inbox owner |
| Why we contacted | ICP rule, signal, sequence + step | SDR |
| Account context | Verified CRM fields + sources | SDR |
| Open questions | What discovery still owes | SDR |
| Next commitment | Action, due date, channel | AE accepts |
| Brief / offer version | Which voice brief was live | Ops |
Dievio's handoff guidance adds the ops layer agencies forget: qualification threshold, timing SLA, and a feedback loop when AEs reject a packet. Log rejects into the library so weak summaries stop repeating.
Keep libraries client-isolated
Two clients can share an ICP and still need separate libraries. Tone, offer, legal landmines, and AE calendars differ. Cross-contaminating "how we phrase interest" is how you hand Client B's pricing story to Client A's AE.
GTM's model assumes client-isolated workspaces with shared-inbox reply ownership and CRM/calendar follow-through after sequences stop on reply. The positive-reply library sits on top of that: it turns inbox categories into AE-ready packets without mixing identities.
What "done" looks like
- Every book-intent reply produces a packet with the same field labels
- AEs can answer "what did they say?" without opening five tools
- New seats train on the library, not on tribal Slack lore
- Rejected packets feed a weekly ops review, not silent resentment
If you are building that handoff motion for agency outbound, join the waitlist.