Seminar Reminder Text Templates: The Cadence and Copy That Protect Your Show Rate
Text messages are the workhorse of seminar attendance: they get read within minutes, they collect replies, and they are the cheapest insurance you can buy on marketing spend you have already committed. Below is the five-send cadence I run for my own dinner seminars, with a copy template for each send, the rules for handling replies, and one technical detail about characters that quietly triples some advisors' texting costs.
These templates pair with the strategy piece on the confirmation sequence, which explains why each send exists. This article is the copy.
The rules before the templates
Send from a number that can receive replies. The entire point of a confirmation ask is the reply. A one-way blast number turns your best send into a flyer.
Identify yourself every time. They registered weeks ago through a mailer. Assume they have forgotten who you are, because they have.
Every message carries the essentials. Date, time, venue name. Nobody should have to scroll up.
One message, one job. The confirmation ask asks for confirmation. The day-before message gives logistics. Mixing jobs lowers the response to both.
Honor STOP instantly and permanently. Not just because carriers require it. A household that opted out of texts is telling you which channel they want, and there is an email and a phone number on the same registration.
The five sends
1. Instantly at registration
Hi [First Name], this is [Advisor] at [Firm]. Your seats are reserved for [Event] on [Day, Date] at [Time], [Venue]. We'll text you closer to the date. Reply STOP to opt out.
Job: prove the registration worked and establish this number as the channel. A failed send here is free intelligence: it flags junk contact info while there is still time to fix it.
2. Seven days out: the confirmation ask
Hi [First Name], it's [Advisor] at [Firm]. We're finalizing dinner counts for [Event] on [Day, Date] at [Time], [Venue]. Can you reply C to confirm you'll be joining us? If plans changed, no problem, just reply and let us know.
Job: the pivotal ask. The single-letter reply matters: C is a lower-friction commitment than composing a sentence, and the dinner-count framing gives a polite, concrete reason for asking. The off-ramp sentence is deliberate. A household that tells you they are out a week early is doing you a favor, and making that easy recovers seats.
3. Three to four days out: the second ask, unconfirmed only
Hi [First Name], [Advisor] here at [Firm]. Just making sure my earlier text reached you. We have you down for [Event] this [Day] at [Time], [Venue], and the restaurant needs our final count. Reply C to confirm, or let me know if you can't make it.
Job: recover the silent. The confirmed households never see this message. For high-value registrations that stay silent after this send, a two-minute phone call outperforms any third text.
4. Day before: logistics for the confirmed
Hi [First Name], looking forward to seeing you tomorrow at [Event], [Time] at [Venue], [Address]. Parking is [detail]. Ask for the [Firm] event when you arrive. See you there!
Job: remove friction. No ask, no selling. The households reading this are coming; your only goal is that nothing between their driveway and your room gives them a reason not to.
5. Day of: the short one
See you tonight at [Time]! [Venue], [Address]. Ask for the [Firm] table. Safe travels, [First Name].
Job: presence. Sent late morning or early afternoon, never an hour before doors.
Handling the replies
The sequence generates three kinds of responses, and each needs a lane:
- Confirmations flip the household to confirmed, which changes every downstream message they receive. This bookkeeping is exactly the thing spreadsheets fumble at volume.
- Cancellations and reschedules free a seat and, handled warmly, keep the household alive for the next event. A gracious reply to a cancellation is future pipeline.
- Questions arrive constantly: menu, guests, directions, what to bring. Someone has to be watching the inbox, because a question texted to a void reads as an excuse not to come.
What happens after the event is a different discipline entirely, covered in the follow-up process.
The character rule that triples your bill
One technical detail worth knowing. Standard texts use an encoding called GSM-7, which allows 160 characters per message segment. But certain characters silently break it: smart quotes, curly apostrophes, and long dashes, the exact characters word processors insert automatically. One of them anywhere in your message switches the entire text to a different encoding, and the segment limit drops from 160 characters to 70.
The result: a 150-character reminder that should cost one segment ships as three. Multiply across a five-send sequence and a hundred registrants, and you are paying triple to send the same words. Write your templates with straight apostrophes, straight quotes, and plain hyphens, and if you paste copy from a document, check what came along for the ride.
The one-line summary
Five sends, each with one job, from a number that can hear the answer. The copy above is a starting point; the cadence and the reply handling are the system. Adapt the words, keep the discipline.
Full disclosure: in my practice this sequence runs automatically on SeminarEV, which I built, including the confirmed and unconfirmed branching, two-way replies, and the encoding check. The templates work by hand too. The reason to automate is not that the sends are hard, it is that the fourth event of the quarter is when hand-run sequences quietly stop happening.