Every appointment Aiva Chat books, over the phone, in website chat, or on your booking page, sets off the same sequence: a confirmation the moment it's made, reminders before the visit, and a link the customer can use to confirm, move, or cancel without calling.
That's the part most booking software also does in some form. The useful questions are about the edges. What happens when the customer replies "C"? What happens when they reply "can we make it 5 instead?" Where does the change actually get made, and who sees it?
Those edges matter because plans change between the moment someone books and the moment they're due to arrive. A reminder that goes out for the wrong time, or a reply that lands in an inbox nobody connects to the booking, is how a customer who did tell you turns into a no-show anyway.
If you run the front desk, this piece follows one booking from the call to the visit, including what Aiva Chat leaves to your team: answering the free-form text replies it isn't set up to handle.
What is a booking confirmation and reminder flow?
It's the set of messages a customer gets between booking and showing up. In Aiva Chat there are four kinds:
- Confirmation, sent immediately, with the date, time, service, and the customer's own manage link. By email it also carries a calendar file.
- Reminders, sent automatically before the appointment by text and email.
- Change notices, sent when a booking is moved or cancelled.
- An optional no-show text, "Sorry we missed you", with a link to book again.
Two things are important to be clear about:
- Confirmations and reminders are automatic. Nobody on your team triggers them.
- Conversations by text depend on one setting. With Booking by text on, a customer can reply to move or cancel, or ask when their appointment is, and Aiva Chat handles it by text on its own. With it off, or for texts that aren't about appointments, a person reads the message and sends the answer, clicking Suggest a reply if they want Aiva Chat to draft one.
Calls, website chats, and texts all sit in one inbox, so the call where the booking was made and the text thread that followed are both easy to find. The wider booking system is covered on the bookings page.
How the flow works
Step 1: A booking is made
A customer books on a call, in website chat, on your booking page, or in the "Book online" section of your Aiva Chat website. Every channel uses the same rules: the time must be inside your hours, not clash with another booking, and not be busy on your connected Google Calendar. The booking is saved and written to your calendar.
Step 2: The confirmation goes out immediately
As part of the same step, Aiva Chat texts the customer with the date, time, and service, plus their manage link. If it has their email, an email goes too. A short confirmation is allowed even during quiet hours, so there's never a gap where the booking exists but the customer has nothing in writing.
Step 3: Reminders go out before the visit
By default, a reminder goes 24 hours before and another 2 hours before. You can pick up to two of 24 hours, 2 hours, or 1 hour, and choose text, email, or both, per assistant. Reminder texts respect 8 AM to 9 PM quiet hours, so nobody gets a 6 AM buzz about a 9 AM appointment.
Step 4: The customer confirms, moves, or cancels
A reply of "C" marks the appointment as confirmed. The manage link lets them move it to another free time or cancel it, up to 2 hours before by default. With Booking by text on, they can also reply to the text to move or cancel, and Aiva Chat makes the change. Either way, the change lands in Aiva Chat's appointment book and on your calendar, and the freed time is open for someone else.
Step 5: Anything else reaches a person
Replies Aiva Chat isn't handling, like "can I bring my sister?", land in the Conversations inbox in the same thread as the reminder. Someone clicks Suggest a reply, Aiva Chat drafts an answer from the thread and your business information, and the person edits it if needed and sends it.
Benefits of automatic confirmations and reminders
Customers have the details in writing
A booking made by voice is easy to misremember. A text with the date, time, and service is something the customer can check later without calling. It reaches any phone, including basic handsets, which is why SMS still reaches customers chat can't.
Fewer people simply forget
The most common no-show is someone who forgot. A reminder the day before and a couple of hours before catches most of them, and nobody on your team has to work through tomorrow's list by phone.
You know who's coming
"C" replies show up as confirmed on the calendar. On a busy morning, the front desk can see at a glance which customers have said yes and which haven't answered, and decide whether a quick call is worth it.
Cancellations come in early enough to rebook
Moving or cancelling from a link takes seconds, so customers who can't make it tend to say so instead of not turning up. If you've switched on the waitlist, a freed time can be offered to the next people waiting for it.
A person still owns the judgment calls
Apart from appointment texts, which Aiva Chat answers only if you turn on Booking by text, free-form replies wait for your team by default, so the judgment calls go to a customer from someone who has read them. The routine messages are automatic; the judgment calls stay with a person.
Booking reminder use cases
Here are four situations front desks see every week, using made-up businesses.
The forgotten appointment
Problem: A salon customer booked by phone ten days ago and has lost track of it. How Aiva Chat handles it: The 24-hour reminder arrives the afternoon before. She replies "C", and the booking shows as confirmed. Outcome: She turns up on time, and the stylist knew she was coming.
The reschedule from the link
Problem: A clinic patient realises the night before that Thursday at 3 won't work. How Aiva Chat handles it: He taps the link in his reminder, picks 5 PM on Friday from the free times, and the booking moves. A change notice confirms the new time. Outcome: The 3 PM slot is open again before the clinic even opens, with no phone call.
The reply that isn't a command
Problem: A customer replies to a reminder: "running 10 min late, is that ok?" How Aiva Chat handles it: The message lands in the inbox. Staff click Suggest a reply, check the draft against your late-arrival policy, and send it. Outcome: The customer gets a real answer from a person, quickly.
The no-show
Problem: A repair customer doesn't answer the door and doesn't reply. How Aiva Chat handles it: Staff mark the booking as a no-show. If you've switched on the no-show text, the customer gets a short "Sorry we missed you" with a link to book again. Outcome: Some of those customers rebook instead of disappearing, and the no-show feeds your show-up rate report.
Aiva Chat vs. one-way texts vs. a separate reminder tool
| One-way notification | Separate reminder tool | Aiva Chat | |
|---|---|---|---|
| Sent automatically on booking | Yes | Yes | Yes, on every booking channel |
| Automatic reminders before visit | Sometimes | Yes | Yes, up to two, by text and email |
| Confirm by reply | No | Usually | Yes, reply C |
| Customer can move or cancel themselves | No | Sometimes | Yes, from their own link |
| Free-form replies | Go nowhere | Usually keyword-only | Changes and cancellations handled by the AI with Booking by text on; others AI-drafted, sent by a person |
| Connected to the booking | No | Only if synced | Same system that took the booking |
| Cost model | Per-message | Monthly fee plus messages | Included in plan; Twilio bills texts |
A one-way notification is the cheapest option, but it leaves the customer with no easy way to tell you their plans changed.
A separate reminder tool can work well, but it has to stay in sync with wherever bookings are made. If a phone booking or a move doesn't reach it, the reminder goes out for the wrong time or not at all.
Aiva Chat's reminders come from the same system that took the booking, so a move made on a call, on the booking page, or from the customer's link updates the reminder too. If you already pay for a reminder tool only to cover bookings Aiva Chat takes, you can usually drop it.
How to set up confirmations and reminders in Aiva Chat
Step 1: Name your services clearly
Confirmations and reminders include the service name, so "Haircut and colour" reads better than "Service 2."
Step 2: Connect a Twilio number that can text
Connect your Twilio account and a number with SMS enabled. For US and Canadian numbers, you also need an approved A2P 10DLC registration, the carrier standard for business texting on local numbers. Aiva Chat's registration guide walks through it.
Step 3: Check the reminder settings
Reminders are on by default. Open the assistant's reminder settings and choose the times (up to two of 24 hours, 2 hours, and 1 hour) and the channels. Decide whether you want the no-show text, and how close to the appointment customers may still move or cancel.
Step 4: Turn on booking
Teach your assistant your services and hours, and connect Google Calendar so phone bookings are offered and every booking is written there. Website text chat and your booking page can take bookings too.
Step 5: Test it end to end
Book a test appointment for later today by calling your number. Check the confirmation arrives, wait for the reminder, reply "C", and check the booking shows as confirmed. Then use the link to move it and confirm the change notice arrives.
Step 6: Decide who reads the inbox
Free-form replies the AI isn't handling still need a person. Decide who checks Conversations, and how often, especially the evening before busy days.
Common mistakes with confirmation and reminder texts
Moving bookings only in Google Calendar
Every Aiva Chat booking appears in Google Calendar, so it's tempting to drag a moved appointment there. But reminders and the customer's link work from Aiva Chat's own appointment book, so the reminder still goes out for the old time. Move appointments in the Aiva Chat dashboard, or let the customer use their link.
Skipping A2P registration
Unregistered US and Canadian numbers can have texts filtered or blocked by carriers, which silently breaks reminders. Register before relying on them.
Assuming every reply is a "C"
Some replies are questions, some are late notices, some are opt-outs. Only "C" or "CONFIRM" confirms automatically. Make sure someone reads the rest that Aiva Chat isn't handling, and remember that "please stop texting me" isn't the STOP keyword, so add the number to your do-not-contact list by hand if needed.
Setting reminders too close to the visit
A single 1-hour reminder is often too late for someone to rearrange their day, and past the default 2-hour cutoff for moving a booking themselves. Keep a reminder far enough ahead for a cancellation to be useful.
Best practices for booking reminder texts
- Keep the default 24-hour and 2-hour pair unless you have a reason to change it.
- Name services clearly so messages make sense at a glance.
- Check confirmed versus unconfirmed bookings each morning.
- Use Suggest a reply for free-form texts, but read every draft before sending.
- Make changes in Aiva Chat, never only in Google Calendar.
- Mark no-shows so the show-up rate report stays honest.
- Respect opt-outs and keep your do-not-contact list current.
Conclusion
The confirmation is the easy part; the reminders and the replies are where no-shows are won or lost. Aiva Chat now handles the routine end of that on its own: reminders go out on time, "C" marks a booking confirmed, and the customer's link, or with Booking by text on a reply, moves or cancels it without anyone picking up a phone.
What's left for your team is the conversation: the "running late" and "can I bring someone?" texts that deserve a real answer. If someone can own the inbox at least twice a day, the flow works end to end. Register your number for A2P first, then test the loop with a booking of your own. For more on the SMS side of the product, see inside Aiva Chat's SMS engine.
Ready to cut no-shows without a separate reminder tool?
The quickest proof is a test booking on your own number. Phone the assistant, book a time later today, wait for the confirmation and the reminder, then reply "C" and see it show up as confirmed.
Confirmations and reminders work on every plan, with Twilio charging the texts to your own account. The SMS channel page covers registration and opt-outs in more detail.
Start a 14-day free trial, no card needed, or book a demo if you'd like us to walk your front desk through the reminder settings.
Posts from the people building Aiva Chat in Rajkot — how the product works, what we have learned building it, and guides for getting the most out of an AI receptionist.