You probably do not need it
Short version, and it is not the answer you expected: you probably do not need Twilio with Bookafy. SMS text reminders are built into Bookafy and included — no Twilio account, no phone number to buy, no per-message metering. This page explains what the built-in SMS does, and the narrow cases where wiring up Twilio yourself still makes sense.
Text reminders are the single most effective no-show fix there is. Which is exactly why a lot of scheduling tools meter them: you will find SMS listed as “extra charge” on every tier of some competitors, or as a credit pack you top up. Once reminders cost money per message, people ration them, and the no-shows come back.
In Bookafy, SMS reminders are part of the product. That is a deliberate choice and it is worth saying plainly.
You write the message text. You choose the timing. Nothing is per-message billed to a balance you have to remember to top up.
Three real cases:
| Case | Why Twilio |
|---|---|
| You already run all customer messaging through Twilio | You want one number, one message log, one compliance record. Fair. |
| You need SMS logic Bookafy does not do | Two-way conversational replies, WhatsApp, a bespoke escalation flow. |
| You are building on Bookafy as a platform | White-label and reseller builds where the messaging has to carry your brand and your rules. |
In all three, the wiring is the same: Bookafy is a published Zapier app, so New Appointment or New Customer triggers a Zap that fires a Twilio “Send SMS” action. Bookafy’s Zapier triggers are New Appointment, New Customer, New Appointment Type and New User; its actions are Create Appointment and Create Customer.
Zapier polls. On the free Zapier plan it checks Bookafy every 15 minutes. A confirmation text that arrives up to a quarter of an hour after booking looks broken to a customer, and that is a bad first impression. If you are sending confirmation SMS through Twilio, use Bookafy’s webhooks and open API instead — they fire in real time. This is the one case where the Zapier path is genuinely the wrong tool.
Also: there is no cancellation trigger in Zapier, so a cancellation text has to come from the API or from Bookafy’s own built-in messaging.
And the obvious one — Twilio charges per message and per phone number. If your only goal is appointment reminders, you are re-buying something you already have.
No. Text reminders are included in the product, not metered as credits.
No. Bookafy sends them itself.
Yes — through Zapier or Make, or through Bookafy’s open API and webhooks. Use the API if timing matters.
Bookafy’s built-in SMS is outbound appointment messaging. Conversational two-way threads are where Twilio genuinely adds something.
Bookafy also connects to 3,000+ apps through Zapier and Make, and offers an open API and webhooks for anything custom.
If you’re weighing up appointment scheduling software, these go deeper:
