Handling a Reply and Booking the Call
What it does: turns a reply into a meeting. Everything before this was automation; from here it is a conversation.
Run it when: the moment a reply lands. The clock starts immediately.
Time: minutes per thread, every day.
Depends on: a live campaign. Nothing else.
Before you start
A booking link that works and has real availability behind it
A decision on which motion this campaign uses, from step 3 below
Someone who owns the inbox daily, by name
The steps
1. Reply fast. This is the whole SOP in three words.
Within hours, same day at the worst. A thread answered in an hour books; a thread answered in three days usually dies. Once campaigns are running, the inbox is the job, not the campaign settings.
2. Drop the template voice completely.
Replies are written for one person. No merge tags, no sequence copy, no reused lines. The same voice rules apply, short and human, but this is now correspondence, not a campaign.
3. Pick the motion for this campaign.
Push to book: propose a call in the first reply, link included. Fast, converts interest at its peak, needs real availability, can feel abrupt on a cool thread.
Qualify first: one or two short questions, then the booking ask. Protects the calendar, filters tire-kickers, and loses some warm leads to the extra step.
Value nurture: give something useful before asking for anything. Slower and more attention per thread, but it earns the booking rather than requesting it.
The best version, when you can manage it, gives value and proposes the call in the same reply.
4. Now the link is allowed.
This is the only place in the whole system where a link belongs. It was banned in the cold sequence for a reason (see SOP 09); once someone replies positively, sending the calendar is helpful rather than spammy.
5. Answer what they actually said first.
Before advancing your own agenda, respond to the thing they wrote. Skipping this is the tell that a human is running a script, and people can feel it instantly.
6. Keep replies to one to three sentences and one ask.
Mirror their energy and formality. Two questions in one reply splits their attention and usually gets neither answered.
7. Handle objections in three moves.
Concede the part that is true, offer one honest counterpoint or proof, then re-offer a smaller step. A smaller step is a 15-minute call instead of a demo, or a resource instead of a call.
8. Take "not interested" at face value.
Thank them, leave the door open, stop. No arguing, no "just checking you saw this". The door stays open only if you close it politely.
9. If the volume genuinely outruns the humans, cap the automation.
There is an AI reply agent with its own daily cap. It is a stopgap for a drowning inbox, not the recommendation. Manual replies book more meetings.
Do this / Not this
Do this | Not this |
|---|---|
Reply within hours | Batch the inbox on Fridays |
Written for this one person | A templated response |
One clear next step | Two asks in one message |
Calendar link after a positive reply | Calendar link in the cold sequence |
Concede, counter, smaller step | Rebut point by point |
"Thanks, I'll leave it there" | "Just checking if you saw my last note" |
Someone owns the inbox by name | Everyone assumes someone else is on it |
Done when
Every reply from today is answered
The motion for this campaign is chosen and consistent
Booking link tested and availability real
Objection handling is three moves, not a debate
Nobody is waiting more than 24 hours for an answer
