Building a booked-conversation packet from AI outbound to the client AE
AI booked the hold. The calendar invite is green. The AE still walks in cold.
That is the gap agencies get paid to close. A booked conversation without a handoff packet is just a time slot. The AE spends the first ten minutes reconstructing why the prospect said yes, which is how no-shows and awkward intros get born.
What the packet must answer
Unify's outbound handoff template puts it cleanly: the AE should answer four questions without rebuilding the sequence.
- What did the buyer actually say?
- Why was this person contacted?
- What is verified about the account?
- What commitment comes next?
If your packet cannot answer those in under a minute, it is a novel, not a handoff.
Required fields (keep them short)
| Field | What to put | What not to invent |
|---|---|---|
| Buyer reply | Link to the full thread plus the exact inbound text | A polished paraphrase that upgrades "send info" into "qualified opp" |
| Account context | Verified CRM fields and source links | Hypotheses dressed as facts |
| Trigger and outreach | Sequence, step, sender, signal or list source | "They saw our brand everywhere" |
| Open questions | Timing, budget, process unknowns | Fake BANT scores |
| Next commitment | Owner, action, date, channel | A meeting titled "Intro" with no agenda |
ProspectingManual's SDR-to-AE checklist adds the operational glue: calendar hold on the AE's calendar, CRM deal updated, and a direct ping with the deal link. Agencies running AI booking need the same four items before anyone calls it done.
Separate evidence from guesses
A positive reply proves openness to a next exchange. It does not prove budget, authority, need, or timing. Unify is explicit about this, and your packet should be too.
Label hypotheses. "Hiring spike may mean capacity pain" is fine. "They have budget because they are hiring" is not.
Agency-specific twists
When the AE sits at the client, not inside your agency:
- Write the packet in the client's CRM language and stages
- Include who on your team owns reply triage until the AE accepts
- Pause every automated touch the moment the hold is booked so the buyer does not get a Day-4 bump while the AE is preparing
- Attach the compliance artifacts the client cares about: unsubscribe path honored, last send timestamp, workspace id
If the client AE rejects the packet, require a reason code: missing source reply, ownership conflict, unclear next step, or compliance issue. Returned packets are how you improve the template without bloating it.
Acceptance is the boundary
The handoff is not complete when the calendar event exists. It is complete when the receiving AE confirms:
- The packet is visible
- Ownership is correct
- The next task is clear
- Overlapping sequences are paused
ExeSketch's SOP style works here: acknowledgment inside a stated window, then AE-owned follow-through. Pick a window your agency can keep (same business day for holds inside 48 hours is a common bar). Publish it in the client workspace rules so AI booking and human ops share one definition of "done."
Packet length test
Time one real handoff. If the AE needs more than two minutes to find the next action and the supporting reply, cut fields. Background research links go below the fold. The first screen is the buyer's words, the commitment, the owner, and the biggest open question.
Where GTM fits
GTM's motion ends in reply handling and calendar follow-through inside client-isolated workspaces. The booked-conversation packet is the ops artifact that turns that last mile into something a client AE can run without rebuilding the outbound story from scratch.
Build that packet once. Reuse it across clients. Join the waitlist if you want the workspace layer underneath it.
Sources
- https://www.unifygtm.com/explore/sdr-to-ae-outbound-handoff-template
- https://prospectingmanual.com/engagement-crm/workflows/sdr-to-ae-handoff/
- https://exesketch.com/templates/sales-handoff-sdr-ae
- https://dievio.com/blog/sdr-to-ae-handoff-workflows
- https://resources.rework.com/guides/sales-process/sdr-ae-handoff
- /workspace/trygtm/knowledge/product.md