Starting at the booking
The confirmation fires immediately — not in the next batch, not in ten minutes. It is the receipt for a decision the person has just made, and a gap there reads as a system that did not register it.
Six complete emails covering the distance between a booking and a conversation — the confirmation, the prep ask, the day-before and hour-before reminders, the same-day no-show recovery and the follow-through note. Subject lines included, ready to copy, with the timing reason for each and variants for discovery, demo and onboarding calls. Works in any email tool.

A webinar sequence runs against a fixed date everyone shares. A call sequence does not: every booking starts its own clock, and the distance between the booking and the call is different for every person in it.
The confirmation fires immediately — not in the next batch, not in ten minutes. It is the receipt for a decision the person has just made, and a gap there reads as a system that did not register it.
The prep ask, both reminders and both after-messages are timed against the call itself. Someone who books for tomorrow morning should receive the confirmation and the hour-before reminder, and nothing else.
When the booking lands inside forty-eight hours, collapse the sequence rather than compressing it. Fold the prep question into the confirmation, keep the hour-before reminder, and drop the rest. Four emails in thirty-six hours reads as a system talking to itself, and it is the fastest way to make a warm booking feel like a lead in somebody’s pipeline.
Everything in [brackets] is yours to replace, including the parts that read as instructions — they are there because a template that writes your agenda for you produces six emails that say nothing. Swap them for your tool’s merge fields where one exists; field names differ by platform, so these are written in plain brackets rather than any product’s syntax.
Six messages, four before and two after. The two after are not optional extras — the recovery message is the only one in the pack that recovers anything, and the follow-through is the only one that turns a good conversation into a next step with a date attached.
| When | |
|---|---|
| On booking | The instant confirmationLogistics, the frame, the calendar file and the reschedule link. |
| T−48h | The prep askOne question. Raises call quality and flags a silent booking. |
| T−1d | The day-before reminderRemoves friction, and makes moving it easier than skipping it. |
| T−1h | The hour-before reminderFour lines. Join, or reschedule. |
| T+10m | The no-show recoverySame day, blame-free, one click to rebook. |
| T+2h | The follow-through noteThe written record of what was agreed, and by when. |
Most sequences treat everything before the reminders as admin. These two do more work than either reminder: the first confirms the frame the booking page set, and the second changes the conversation you are about to have.
Both belong to the same idea — the call has already started. What the person expects when they arrive was decided by what they read while they were waiting, and the thirty minutes go much further when the first ten are not spent establishing things a sentence could have handled on Tuesday.
[First name] — You are booked. The details: What: [Call name], [length] minutes When: [Day, Date] at [Time] [Timezone] Where: [Join link] — nothing to install With: [Your name], [one clause on who you are] Add it: [Calendar file attached, plus a calendar link] What happens in the [length] minutes: 1. [Beat one — what you will ask] 2. [Beat two — what you will look at together] 3. [Beat three — what you will tell them, including whether [the offer] is a fit] You will leave with [the thing they get whether or not they buy]. If [Day] stops working, move it here: [Reschedule link]. One click, no explanation needed — it is genuinely easier for me than an empty slot. [Your name]
The most-opened message in the pack, because it is the one people go back to find the link in. It has two jobs and most confirmations only do the first: carry the logistics, and confirm the frame the booking page set. The reschedule link belongs here rather than at the end of the sequence — somebody who cannot make Tuesday works that out on Sunday, and the easier moving it is, the fewer empty slots you sit through.
[First name] — We speak on [Day] at [Time] [Timezone]. [Join link] One question first, so the time goes somewhere useful: [The single question — the one whose answer changes how you run the call. For example: “what have you already tried for [the problem]?” or “what would have to be different by [timeframe] for this to have been worth doing?”] A sentence is plenty. Reply here and I will read it before we start. [If there is something to have ready, one line naming it.] [Your name]
The email that raises call quality more than any script does, and the only one in the pack that asks for something. One question, not four — a form on a page can carry four, an email asking for a reply gets one answer or none. The timing is the whole point: far enough out that answering is easy, close enough that the call feels real. It doubles as an early warning, because a booking that goes silent on a one-line question at T−48h is a booking worth confirming.
A booking is a decision people make once and then quietly reconsider every day until the call. These two exist to make the second decision easy — and to make moving the call easier than skipping it.
That last part is the piece most sequences get backwards. Leaving the reschedule link out of a reminder does not protect the booking; it removes the only option somebody has other than not turning up. A moved call keeps the relationship, the context and the intent. An empty slot keeps none of them.
[First name] — [Call name] is tomorrow. When: [Day, Date] at [Time] [Timezone] Join: [Join link] Bring: [what to have open, or “nothing — just yourself”] We will cover [beat one], [beat two] and [beat three], and you will leave with [the thing they get either way]. [If they answered the prep question: “Thanks for the note about [their thing] — that is where we will start.” If they did not: “If you get a minute, [the prep question] — a sentence is plenty.”] If tomorrow has stopped working, move it here: [Reschedule link]. No explanation needed. [Your name]
Not a nudge — a friction remover and a permission slip. Every unanswered logistical question is a reason to skip, and the reschedule line placed here rather than buried at the bottom turns a would-be no-show into a moved call, which is worth several times more. Send it the day before rather than on the morning: people need enough notice to move it while moving it is still easy for both of you.
[First name] — We speak in one hour, at [Time] [Timezone]. Join here: [Join link] If something has come up, [Reschedule link] — no explanation needed. [Your name]
Four lines and two links. Anything else in this email is a reason to set it aside and come back to it, which is the exact behaviour costing you the call. Keep the reschedule link even this late: an hour out, the honest alternative to a reschedule is not attendance, it is a no-show, and one click is the difference between a moved call and an empty room.
The reminders have to stop when a call is rescheduled, and the last two branch on whether it was held at all. When the scheduler, the email tool and the customer record are three systems, that branch is a person checking a calendar at the end of the day. Agorix keeps booking, conversation and follow-up on one customer record, with no-show recovery as part of the meeting flow — see how meetings work.
At the end of the slot the call either happened or it did not, and the two outcomes need entirely different messages. Writing both in advance is what makes either one arrive on time.
The no-show message is the one people postpone, because sending it feels like chasing. It is not: it is the only message in the pack that recovers something already paid for, and its conversion is almost entirely a function of how quickly it arrives and how completely it avoids making anybody feel bad.

[First name] — I was on for [Day] at [Time] and we did not connect. No problem at all — [Days] are what they are. Grab whatever time suits: [Reschedule link] If it is easier, reply with two or three windows and I will send an invitation. [One line that stands on its own whether or not they rebook: the resource, the answer to the question they left on the booking form, or the short version of what the call would have covered.] [Your name]
Same day, within minutes rather than tomorrow, while the slot is still a thing that just happened rather than a thing they now feel bad about. Blame-free is not politeness, it is arithmetic: the person who missed already feels the awkwardness, and any sentence that adds to it converts a rebook into a silence. One link, no guilt, and one genuinely useful line so the message is worth opening even from somebody who never rebooks.
[First name] — Good to talk. Writing it down so neither of us has to remember it: What matters most to you: [their words, not yours] What I suggested: [the recommendation, in one line] What happens next: [the specific step, and who owns it] By when: [the date] [If there is an offer: what it is, what it costs, what is included and the link — stated the same way you stated it on the call. If there is a deadline, put the exact date and time here, and then hold it.] [If they are deciding: “Take the time you need. If it would help, reply with the thing you are weighing and I will answer it straight.”] [Your name]
Sent while both of you still remember the conversation the same way, which stops being true faster than anyone expects. Its real job is not the pitch — it is the written record of what was agreed, and that record is what lets the next step happen without a second call to re-establish the first. The line quoting their own words back is the one that gets replied to, and it costs nothing except paying attention during the call.
The copy is the visible part. These are the settings around it, and a sequence with good copy and wrong mechanics performs worse than the reverse.
Six is the full sequence, not the minimum. Three cover the moments that decide most outcomes, and running three properly beats running six badly.
The time with the timezone written out, the join link, one line on what happens in the call, one line on what the person leaves with, and a reschedule link. That is the whole job. These messages work because they read like somebody confirming a meeting rather than like marketing, which means a real from-name, a reply-to a human reads, plain formatting and one action.
Four between booking and call: the instant confirmation, a prep ask around forty-eight hours out, a day-before reminder and a short hour-before reminder. If the call was booked inside that window, collapse the sequence rather than compressing it — send the confirmation with the prep question folded in, then the hour-before reminder, and nothing else. Where the bookings come from in the first place is the webinar to strategy call funnel.
The same day, within about ten minutes of the slot rather than the next morning — while it is still a thing that just happened rather than a thing they feel bad about. Blame-free, one-click rebook, and one line of value that stands on its own whether or not they take it. How long to keep going, how many times, and when a rebook stops being worth chasing is the no-show follow-up playbook.
Yes, in every message — including the confirmation and the hour-before reminder, where most sequences leave it out for fear of inviting a cancellation. The fear is backwards. An hour out, the alternative to a reschedule is not attendance, it is a no-show, and a moved call is worth several times an empty slot. This is the cheapest change available to a booked-to-held rate.
One question, around forty-eight hours out, whose answer changes how you run the call. Usually that is what they have already tried — which tells you whether you are the first attempt or the third — or what would have to be different by a given date for the work to have been worth doing. Ask for a sentence rather than a form. One question gets an answer; four get silence, and silence at T−48h is itself information.
The structure holds; the specifics do not. A discovery reminder carries the agenda, because the prospect is deciding whether the conversation is structured. A demo reminder names who else should be there and asks which workflow to build the session around. An onboarding reminder lists the access and accounts needed in advance — the client onboarding call guide covers what that call has to produce. Every template below carries all three variants.
Branded booking, the reminders timed against the call, browser-based meetings, a no-show recovery path and the outcome written back to the customer record — so the follow-up already knows whether the conversation happened.
14 days · $0 due today · Payment method required · Cancel before first charge and pay nothing