Automatic booking confirmation and reminder texts are the cheapest no-show fix there is. The customer books, and a text lands on their phone. The day before, another one. Nobody on your staff types anything. This guide covers how to set that up with whatever booking platform you already use, what the carriers require before you can send a single message, and the mistakes that cost us time on real builds.
Why text, when the platform already sends email
Most booking tools send a confirmation email. Almost nobody reads it when it matters. The customer who needs the door code, the suite number, or the "park in the back" note is standing in a parking lot looking at their phone. A text gets read. An email gets searched for, maybe.
The second reason is that a reminder that arrives at the right moment does the work of a phone call. For appointment businesses that means fewer no-shows. For self-service businesses it means fewer "how do I get in?" calls to the owner.
What you need
- A booking platform that can tell you when something happens. Look for "webhooks" or "integrations" in its settings or developer docs. If it has neither, you can usually poll its API every few minutes instead.
- A business texting number registered with the carriers for automated messaging. Your personal cell won't do.
- A small service in the middle that receives the booking event, decides what to send and when, and sends it. This can be a no-code automation tool for simple cases, or a small hosted app for anything involving door codes or lookups.
- A record of what was sent. A database table, ideally. You'll need it the first time a customer says "I never got a text."
Step 1: Find the trigger and check what it carries
Turn on the webhook and make a test booking. Then look at what actually arrives. You need the customer's phone number, the appointment time, and enough detail to write a useful message (service, location, bay, room, whatever applies).
Check this carefully, because platforms are inconsistent. On one booking platform we built against, two different events fire when a booking is made, and only one of them carries the customer's name and phone. The other is useful as a cancellation signal and nothing else. You won't find that in the documentation. You'll find it by reading the test payload.
Also check timestamps. Many platforms send times in UTC. Convert to your venue's time zone before you schedule anything, and remember that Arizona doesn't observe daylight saving time.
Step 2: Decide the message plan
Keep it to two texts, or one if bookings tend to be same-day.
- Confirmation the moment they book: date, time, location or bay, and a one-line "what to expect."
- Reminder at a set time before: the day before for appointments, an hour before for self-service bookings. This one carries the practical details, like a door code or a "press any key to wake the screen" note.
A third text is almost always too many. If you have house rules, put them in the email. People skim texts.
Step 3: Get the number and the registration right
This is the step that sets your timeline. In the US, a business can't send automated texts from a number until it's registered under A2P 10DLC. You register the business (legal name, EIN, address) and describe the campaign. Until it's approved, messages are blocked or filtered.
- Approval typically takes 2 to 5 business days and can run longer. Start it on day one.
- It costs about $20 one time plus a small monthly campaign fee.
- Reviewers now expect a live privacy policy and an SMS terms page on your website, linked to each other, with real dates. They click the links.
- Your booking checkout needs a consent line near the phone field. Something like: "By providing your phone number, you agree to receive booking-related text messages. Reply STOP to opt out."
If you want texts to come from the number customers already know, that number has to be ported to a provider that supports automated messaging. Ports take one to two weeks, and the old service keeps working until the port lands. Between registration and porting, plan on 2 to 4 weeks from start to first live text, even though the build itself takes days.
Step 4: Write the texts
- The first text to any customer must carry the compliance line: "Msg frequency varies, msg & data rates may apply. Reply STOP to opt out, HELP for help." Once is enough.
- No emoji, no curly quotes. One fancy character drops the per-segment limit from 160 characters to 70 and doubles the cost of every message.
- Say when things are valid. If a door code only works 15 minutes before the session, the text has to say so or the phone rings.
- Include your phone number so replies and problems have somewhere to go.
A reasonable text runs about two segments, which is roughly 2 to 4 cents per booking.
Step 5: Handle changes and cancellations
A cancellation must stop the reminder. Build it two ways. The cancel event marks any pending message as skipped, and every send re-checks the booking right before it goes out. That second check is the one that saves you when the cancel event never arrives.
Many platforms can't edit a booking. A change is a cancel plus a new booking. Your system should handle that without the customer getting a reminder for the old time.
Step 6: Send exactly once
Automation tools and job queues deliver "at least once," which means a message can be attempted twice. Give every message a row that moves from pending to sent, and make the send check that row first. A duplicate attempt finds it already sent and does nothing. Customers should never get the same text twice.
Step 7: Run it dry for a week
Before the first real text, run the whole system in a mode where it logs what it would have sent instead of sending it. Read the log against real bookings for a few days. You'll catch the wrong time zone, the missing phone numbers on bookings staff created by hand, and the $0 member bookings you weren't sure would trigger. Then flip it on.
What it costs
| Item | Typical cost |
|---|---|
| Business texting number | About $15 per user per month |
| Messaging | About a penny per segment, so 2 to 4 cents per booking |
| Carrier registration (A2P 10DLC) | About $20 one time plus a small monthly fee |
| Hosting for the service | A few dollars per month |
| Build and launch | Depends on lookups. A plain confirm-and-remind is a small project. |
A business doing 15 bookings a day sends roughly 450 confirmations a month for under $20 in messaging.
Where we've done this
We built exactly this for indoor golf simulator facilities in two states, including door-code lookup from their access control system. The full write-up, with every gotcha we hit, is in how to automate booking text notifications for Trackman simulator bays. The same pattern fits salons, clinics, rental studios, pickleball courts, and anywhere a customer books online and then has to show up.
If you'd like help mapping it to your platform, that's part of what a free automation audit covers. Bring your booking tool and your phone number situation, and we'll tell you the timeline.