Twilio

Connect FlowBookings to Twilio through Zapier and every booking on your Webflow site can fire off an SMS to the customer automatically: a confirmation the second they book, a reminder before they're due.

No email that sits unopened, no customer who forgets they booked. Just a text, from your number, the moment it matters.

Why connect FlowBookings to Twilio

Email is where booking confirmations go to be ignored. Roughly a fifth of them get opened. A text message, by contrast, gets read almost every time, almost immediately, which is exactly what you want for the two moments that actually reduce no-shows: the confirmation that reassures someone they booked correctly, and the reminder that stops them forgetting.

Twilio is how you send those texts programmatically, and wiring it to your bookings means it happens on its own. Someone books, their phone buzzes with a friendly confirmation.

The day before, it buzzes again with a reminder. For appointment-based businesses such as clinics, salons, trades, and consultants, that single channel does more to protect your calendar than any email ever will. Fewer missed appointments, less back-and-forth, customers who feel looked after.

Twilio is a developer tool

Worth being upfront before you build, because Twilio isn't a one-click consumer app like most on this list.

Twilio is a communications platform. To send a text, you need a Twilio account, a phone number you buy from them (usually a dollar or so a month), and two credentials: an Account SID and an Auth Token that Zapier uses to send on your behalf. Texts cost a small per-message fee. None of this is hard, but it's more setup than connecting, say, Slack, and it involves a little config in the Twilio console.

The payoff is that once it's connected, it's the most reliable, highest-open channel you have. If that setup sounds like more than you want, the WhatsApp route (also via Twilio) or a plain email Zap through Gmail might suit you better. But if SMS is what your customers respond to, it's worth the twenty minutes.

You need to be collecting phone numbers

One thing to check before anything else: SMS needs a phone number, and you have to be collecting one on your booking form.

FlowBookings' standard booking fields are name and email, and a phone number isn't captured by default. If you want to text customers, add a phone field to your booking form so the number comes through with each booking (it'll arrive in the booking's custom form data). No phone number on the booking, no text to send.

So step one, before Zapier, is making sure your form asks for it.

What you'll need

• A FlowBookings account, with a phone number field on your booking form
• A free Zapier account
• A Twilio account, a Twilio phone number, and your Account SID + Auth Token
• At least one service set up in FlowBookings, and one booking (with a phone number) to use as a test

The triggers you're working with

FlowBookings gives Twilio two things to react to:

Each message can draw on the customer's first and last name, the service name, the start and end time, the price, and any custom fields on your form, including the phone number you collect.

Zaps you can build

Send an SMS Confirmation on New Booking

New Booking → Send SMS
A booking comes in, and the customer gets an instant text: "You're booked for [service] on [date], see you then!" from your Twilio number. Immediate reassurance, near-guaranteed to be read. This is the Zap that makes customers feel confirmed the second they book.

Send an SMS Reminder Before the Appointment

New Booking → Delay → Send SMS
Using a Zapier Delay timed off the booking's start, this sends a reminder text the day before (or a few hours before) the appointment. The single most effective thing SMS does for an appointment business; a buzz in the pocket at the right moment turns forgotten bookings into kept ones.

Send an SMS on Cancellation

Booking Cancelled → Send SMS
When a booking is cancelled, a quick text can confirm it went through and invite a rebooking: "Your booking's cancelled. Want to find another time? [link]." Closes the loop instantly and gives an easy path back.

How to set up FlowBookings and Twilio integration

Here are the steps to build the integration:

1. Get your Twilio essentials ready

In the Twilio console: buy a phone number if you don't have one (Phone Numbers → Buy a Number, one with SMS capability), and copy your Account SID and Auth Token from the dashboard. You'll paste these into Zapier when you connect Twilio.

2. Grab your FlowBookings API key

In FlowBookings, go to Dashboard → Integrations → API Key and copy the key. Treat it like a password and don't paste it anywhere public.

3. Start a new Zap

In Zapier, hit Create → Zaps, search FlowBookings, and pick it as your trigger app.

4. Choose the New Booking trigger

Select New Booking. When Zapier asks you to sign in, paste your API key. It'll pull in a recent booking as sample data. Make sure your test booking includes a phone number, or you won't have the field to map in step 6. No bookings yet? Submit a test one through your Webflow site first.

5. Add Twilio

Add an action, choose Twilio → Send SMS, and connect your Twilio account using the Account SID and Auth Token from step 1.

6. Build the message

The To field is the one that trips people up. Numbers must be in full international format: +14155551234, with the country code and a leading +. If your form collects numbers without the country code, add a Zapier Formatter step to prepend it, or texts will silently fail to send.

7. Test it and switch it on

Run the test and check that the text actually arrives on a real phone. If it doesn't, the usual culprit is number formatting; see above. Keep the body short; a single SMS is 160 characters, and longer messages send as multiple segments (and cost more). Looks right? Publish.

8. Add the reminder (optional, high value)

Build a second Zap: trigger on New Booking, add a Delay by Zapier set to fire before the appointment (timed off startDate), then Twilio → Send SMS with a reminder. This is the one that saves you from no-shows. The delay step needs a paid Zapier plan.

9. Add a cancellation text (optional)

Build a third Zap: trigger on Booking Cancelled, action Twilio → Send SMS, confirming the cancellation and offering a rebooking link.

Here is detailed documentation on how to set up Zapier in FlowBookings.

What you need to know

A few honest edges before you build:

• You must collect phone numbers. SMS can't send without one, and FlowBookings doesn't collect phone numbers by default. Add a phone field to your booking form first
• Numbers need international format. + and country code, e.g. +14155551234. If your form collects them any other way, add a Formatter step to fix them, or texts fail silently
• Twilio costs a little money. A phone number is roughly a dollar a month, and each text is a small per-message fee. Cheap, but not free like the Zapier-side of things
• The reminder needs a Delay step. No separate pre-appointment trigger exists, so reminders are timed with a Zapier Delay — which needs a paid Zapier plan
• Keep messages short. One SMS is 160 characters. Longer texts split into segments and cost more per send
• Mind consent for texting. SMS rules are stricter than email in many places; customers should expect a text from you. A confirmation for a booking they just made is fine; make sure any reminders or offers are something they've agreed to
• It's fast, not instant. Zapier checks for new bookings every 1–5 minutes on paid plans, up to 15 on the free one, so the "instant" confirmation lands within a couple of minutes, not the same second
• Reschedules don't re-text. The trigger fires when a booking is made, not when it changes, a rescheduled booking won't send a fresh confirmation or shift a scheduled reminder

Frequently asked questions

Do I need to collect phone numbers for this to work?
Yes. FlowBookings collects name and email by default, not phone, so add a phone field to your booking form first. The number comes through with the booking, and you map it to the text.

Does this cost anything extra?
Zapier integration is available on all FlowBookings plans with no extra charges, but Twilio charges a small monthly fee for a phone number and a per-message cost per text. You'll also need a Zapier account, with a paid plan for the delayed reminder.

Why use Twilio instead of just emailing?
Texts get read almost immediately and almost always far higher than email. For confirmations and no-show reminders, that reliability is the whole point.

My texts aren't sending — what's wrong?
Nine times out of ten it's the phone number format. Twilio needs a full international format with a + and country code. Add a Zapier Formatter step to fix numbers that come in without it.

Can I send a reminder before the appointment?
Yes, with a Zapier Delay step timed off the booking's start date. It's the highest-value Zap here for cutting no-shows.

What happens if a customer reschedules?
No new text goes out, and any scheduled reminder isn't shifted — the trigger only fires on a fresh booking.

Do I need to know how to code?
No code, but Twilio needs a little more setup than most apps: an account, a phone number, and two credentials. The texts themselves are built by pointing and clicking in Zapier.