Text an appointment confirmation the moment someone books
A submitted appointment request triggers a text confirming the service, date and time before the client closes the tab.
New submission on your appointment request form
Send an SMS from your Twilio number confirming the date, time and location
One-directional. A submission triggers the action — nothing is written back into your form.
A clinic or a salon that takes bookings through a form has one gap: the request arrives, someone confirms it later by phone or email, and the client forgets. A text closes that gap in seconds.
This flow suits any small practice where the diary is the business — dental, physio, grooming, barbering. The confirmation reads back what the client asked for, so a wrong date gets caught the same day rather than at the door. Reception still approves the slot; the text only removes the silence in between.
Setting it up
- 1
Publish your appointment request form with Phone Number set as required — Twilio has nothing to send to when that field is empty.
- 2
In Zapier, set formformform as the trigger app, choose New Submission, and point it at the appointment request form specifically rather than a catch-all form.
- 3
Add Twilio as the action step, choose Send SMS, and connect the Twilio account that owns your outbound number.
- 4
Set the From number to the Twilio number already printed on your website, so replies land somewhere your reception desk watches.
- 5
Map Phone Number into the Twilio To field.
- 6
Build the message body from Full Name, Service Type, Preferred Date and Preferred Time of Day, then type your address in as plain text — the form does not collect it.
- 7
Add a Zapier Filter before the Twilio step if only certain values of Service Type should get an automatic confirmation.
- 8
Book a test appointment against your own mobile, read the text as a client would, then turn the Zap on.
What maps where
Using the Appointment Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Twilio |
|---|---|
| Phone Number | The Twilio To number the confirmation is sent to |
| Full Name | Opening line of the SMS body |
| Service Type | Named in the message so the client can check what was booked |
| Preferred Date | The date quoted back in the confirmation text |
| Preferred Time of Day | The time window quoted back in the confirmation text |
| Reason for Appointment | A second internal SMS to the practitioner, if you add one |
Variations worth knowing
Practices that run full often give the second choice rather than the first. Add Backup Date to the message body alongside Preferred Date, so the client sees both dates in writing and can ring back to say which one they were given.
Use a Zapier Paths step on Have you been here before? and give each branch its own Twilio action. New clients get arrival instructions, parking and what to bring; returning clients get the short version, which keeps the message to one segment.
If something isn't arriving
Twilio expects E.164 format — +447700900123 rather than 07700 900123. Add a Zapier Formatter step between the trigger and the Twilio action to strip spaces and prefix the country code, and keep Phone Number required so it is never blank.
Replies arrive at your Twilio number and stop there. The connection runs one way only, from submission to message, so nothing comes back into the form. Point the Twilio number's inbound webhook at a shared inbox, or forward it to the desk phone.
Frequently asked questions
Can the client reply STOP to cancel the appointment?
Twilio handles STOP itself and adds that number to its opt-out list, so they stop receiving your texts. It is not a cancellation in your diary. Watch opt-outs in the Twilio console, clear the slot by hand, and tell clients to phone if they need to cancel.
Does the text update if we move the appointment?
No. The Zap fires once, on submission, and nothing is written back into the form afterwards. To tell a client about a change, send a fresh message from Twilio or trigger a second Zap from whatever tool actually holds your diary.
What does it cost to text every booking?
One message per submitted request, unless you filter. Twilio bills per segment and anything over 160 characters splits into two, so a tight confirmation costs half as much as a chatty one. Responses are unlimited and free during early access, so Twilio is the only variable.
Related automations
- Call the on-call engineer when an urgent report comes in
A high-priority maintenance report rings the on-call engineer and reads out the location, category and issue.
- Text a ticket acknowledgement back to whoever reported the problem
Anyone who files a help desk ticket gets a text back with the subject they wrote and a reference to quote.
- Text registrants the venue details straight after they sign up
New registrants receive the door, start time and check-in link by text within seconds of submitting the form.
- Text the assigned rep the moment a demo request lands
Every demo request buzzes the assigned rep's phone with the lead's name, company and the problem they described.
- Text the buyer and the packing bench when an order comes in
One submission sends the buyer a confirmation text and the packing bench a separate message with the picking details.
- Alert a recruiter to every new application
The recruiter gets a nudge for every applicant, with enough to decide who to call first.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free