The sequence
Every touch. Every channel.
On one page.
Four? Fourteen? The number of times a stranger’s phone lights up because of you is the thing you are actually being asked to trust. So it goes on a page, not into a call.
Book a callUpdated
The sequence is every message and every call one registrant can receive from us: in order, with the trigger for each, the channel it arrives on, and the conditions under which it does not fire at all. It runs across four phases, from the moment someone registers for your webinar to the moment your offer closes.
Three channels are involved — text, voice and email. You run a webinar; we work on your show-up rate and your post-webinar sales with an AI voice and SMS system, and this is the part of it you can audit before you buy.
How many touches? Four? Fourteen? Nobody names the number, and the number IS the risk.
That is the correct instinct, and it is why this page exists. An operator who cannot say how many times a registrant will hear from them has not designed a sequence, they have configured a tool and hoped — and the person absorbing that is the one whose name is on the webinar.
So, the honest state of it: the four phases below are settled and published, the touch-by-touch schedule underneath them is not signed off yet, and this page will not carry a number that has not been. A plausible seven-row table would take ten minutes to write, and it is the exact thing this page exists to refuse.
When it is signed off it appears here — every touch numbered across the whole sequence, with its channel, its timing, what it is for and the conditions that stop it firing, and the total above the table counted from the rows, so the headline and the evidence cannot drift apart.
Phase 1 · Instant opt-in
Trigger: the registration is submitted. A two-way text thread opens and asks why they registered, in their own words rather than from a dropdown. The objective is that answer. It is the thing no email sequence produces, and it is worth having even in a month where the show-up rate disappoints.
Phase 2 · Pre-webinar
Trigger: between fifteen minutes and two hours before the session. An outbound call plus a text carrying the join link, referring back to what they said in Phase 1. The objective is a micro-commitment: the registrant states, in their own words, when they will join and what they will be doing right before.
Phase 3 · Mid-session exit
Trigger: an attendee leaves before the pitch. This is the phase we do not sell, and the reason is immediately below. It stays in the product as a capability and out of the pitch as a claim.
Phase 4 · Deadline blitz
Trigger: the session has ended and your offer has a deadline. Text, call and email while the offer is still live. No performance number is attached to this phase, because no traceable benchmark exists for no-show or replay conversion to attach one to.
Phase 3 is the one we will not sell you
What’s the actual message cap? Because that’s how you turn a warm lead into a hater.
The cap and the total are different numbers, and the cap is the one that protects your list. A total describes the plan going perfectly; a cap describes the worst day — the registrant who replies at length, re-registers for the next session, and gets caught by two phases at once.
To mean anything, a cap has to be counted per person rather than per campaign, across all three channels rather than per channel, and it has to include the touches a reply triggers. Ask for it in that form or the number you are quoted is decorative.
| The question | The answer to refuse | What to require instead |
|---|---|---|
| How many touches in total? | “It depends on the campaign.” | A number, and the cap it sits under, both in the agreement |
| Which channels, and can I drop one? | “We run a coordinated multi-channel push.” | The channel of every touch, listed, and the ability to switch one off |
| What stops a touch firing? | Silence on the subject | The skip conditions written down: replied, attended, bought, opted out |
| Whose number is it? | “We handle the numbers.” | A number per client, in your name, and what happens to it if you leave |
| What happens on stop? | “We honour opt-outs.” | Stop on any channel stops every channel, for that person, everywhere |
| Who is awake at 11pm? | “Support will pick it up.” | A name and a mobile number |
None of those six is a technology question. They are all contract questions, which is why the useful version of this page is the table rather than a diagram. The shape of the deal is where the rest of them get settled.
Whose phone number do the calls and texts come from? Who owns it if I leave?
Two questions in one, and the second decides whether the first answer was any good. A shared pool means your registrants share a caller reputation with strangers; a number you cannot take with you means the thread history, and the trust built in it, belongs to a vendor.
The shape that survives scrutiny — and the one agency buyers hold vendors to — is a number per client, in the client’s own name, with per-client sender identity and the suppression list travelling with the client on exit. If it is not in the agreement, it is not true.
If someone says “stop” on a text, do the calls stop too — same second?
The behaviour matters more than the stopwatch, and the behaviour is that a stop on any channel stops every channel for that person. An opt-out honoured on text while the calls continue is not an opt-out, it is a filing system — and it is the single easiest way to convert a warm registrant into someone who talks about you publicly.
Federal rules set the outside limit: a revocation must be honoured within a reasonable time not to exceed ten business days from receipt[1]. That is a legal ceiling, not a design target. A system that needs ten days to stop calling somebody who said stop is a system keeping a separate list per channel, and you should ask to see the one list instead.
Who answers when someone replies at 11pm, or calls the number back?
There are two questions stacked here. Outbound is the easy half: no call goes out before 8 a.m. or after 9 p.m., measured in the recipient’s local time rather than the operator’s, and that is a rule rather than a preference. Inbound is the hard half, because a real person replying to a text at 11pm is not constrained by anybody’s schedule.
The answer to demand — from us or from anyone else — is a name and a mobile number, not a support queue and not a Slack channel. Get it before you sign, alongside the script and the guardrails, because a hand-off with no named destination is a dead end with better manners.
“Your business does not have the privilege of reaching into my phone whenever you want” — how do you not be that?
You do not answer that with a policy paragraph. You answer it with the count, the cap, the hours and the stop, published where the person on the other end could read them too. Everything above is written to survive being read by your registrant, not only by you.
The deeper answer is that the mechanism here is not volume. It is the micro-commitment — the registrant saying, in their own words, when they will join and what they will be doing right before — and that is something you get once, from a conversation, not something you accumulate by asking again.
Frequently asked questions
The four phases and the three channels are published above. The touch-by-touch schedule under them is not signed off yet, and this page will not carry a number that has not been — an invented count, on the one page whose job is naming the number honestly, would be worse than no count. When it is signed off it appears here as a numbered table with the total counted from the rows.
The shape to require is a number per client, in the client's own name, with per-client sender identity and the suppression list travelling with the client on exit. Both halves belong in the agreement rather than in an email.
A stop on any channel has to stop every channel for that person. An opt-out honoured on one channel while another keeps running is not an opt-out. Federal rules require a revocation to be honoured within a reasonable time not to exceed ten business days from receipt — that is a legal ceiling, not a design target.
No call before 8 a.m. or after 9 p.m., measured in the recipient's local time rather than yours. It is a rule, not a setting, and if a vendor treats it as a setting that tells you something.
It is in the product and it is not in the pitch. A mid-session exit only works as a trigger if the platform reports it reliably, and platforms do not: the leave event can fail silently and can arrive long after the person has gone. There is no external evidence base for the tactic either.
That is one of the six things to settle in writing before the first message goes out, alongside the total, the cap, the skip conditions, the number and the out-of-hours contact. The table above is the list to walk through.
The other half of this question is not how often the assistant speaks but what it says when it does, which is on the script page. If you would rather test the whole argument than read it, split your registrant list down the middle and measure it on your own list, or book a call and take the six questions above straight off this page.
Founder & Operator, CallHush
Founder and operator of CallHush. The offer is one sentence: you run a webinar, and we increase your show-up rate and your post-webinar sales with an AI voice and SMS system. CallHush has no closed clients yet — the first engagement is a pilot run as a split of the client’s own registrant list, and nothing on this site is presented as a client result.
View all articles