WhatsApp Appointment and FAQ Chatbot with Twilio Flex: the automation that stops customers forgetting you exist
Every no-show has the same cause: a person meant to come and forgot. That is a solvable problem, and it is solvable once rather than every week.
- Mon 09:00Booking created in your diary. Nothing else to do.
- Wed 16:00Reminder sent, 48 hours ahead, in your business name.
- Wed 16:04Reply: “C” to confirm.
- Wed 16:04Diary updated. Confirmed.
- Thu 07:30Second booking replies “R”. Reschedule link sent.
- Thu 07:31Slot released to the waitlist and refilled.
What it actually does
A scheduler reads the booking source, works out who needs contacting and when, sends on the right channel, and records the reply against the booking.
WhatsApp business messaging, group conversations, chatbots and session handling on the channel your customers already use. In practice, WhatsApp Appointment and FAQ Chatbot with Twilio Flex is the version of that we deploy when a business needs the result rather than a project. The foundation is contributed by a developer in the community, which usually means it solves a real problem someone actually had. That matters more than it sounds: the failure modes have already been found by someone else, in public.
Why businesses ask for this
For customers who live in WhatsApp, an SMS is an interruption and a phone call is worse. Meeting them on the channel they chose lifts response rates without extra effort from your team.
The people who get the most out of it: businesses with international, hospitality or community-based customers.
- Conversations that keep their history instead of restarting each time
- Common questions answered instantly, the rest handed to a human
- One business identity across chat, SMS and voice
How we build it, step by step
The sequence below is the one we follow on every scheduled outreach build. It is deliberately boring, because the interesting version is the one that breaks in month three.
- Connect the calendar or booking system as the single source of truth
- Decide the send window and quiet hours, in local time
- Handle the reply: confirm, reschedule, cancel, or escalate
- Reconcile so a cancelled booking never gets a reminder
What we change before it goes live
A reference implementation is a starting line, not a product. Every one we deploy gets the same treatment:
- Your numbers, your sender identity and your wording, so nothing reads as generic
- Secrets moved out of the code and into managed configuration
- Retries, rate limits and idempotency, so a hiccup never sends twice
- Structured logging and alerting, so a failure is noticed by us and not by a customer
- Consent, opt-out and record-keeping built in rather than bolted on
- Source control, a staging environment and a rollback that takes a minute
Compliance and risk
WhatsApp enforces a 24-hour customer service window and pre-approved templates outside it. We handle template submission and design the flow so you rarely need one.
The technical foundation
Twilio's WhatsApp Business API access, a conversation state store, and template management we maintain for you.
- python — Python, a good fit when the work sits next to data, scheduling or machine learning.
The open-source starting point sits here, and it stays public whether you work with us or not:
What it costs
Three ways to buy this, and the honest recommendation is usually the middle one:
- Starter build, from $2,500 — we build it, hand it over and warrant it for 30 days. Suits a business with someone technical in-house.
- Managed, from $390/mo — we build it and then own it: monitoring, changes, compliance upkeep and a monthly report. Suits everyone else.
- Platform, from $2,400/mo — when this is one of several systems and you want them designed as one layer instead of five.
Platform usage is billed at cost on top and itemised on the invoice. There is no margin on it and no minimum spend.
Common questions
How long does WhatsApp Appointment and FAQ Chatbot with Twilio Flex take to build?
For a standard configuration, about a week from kick-off to a staging number you can test on, then a few days of live monitoring before we call it done. Anything involving a port of an existing phone number adds one to two weeks of carrier time that nobody controls.
What does it cost to run each month?
Two lines: our managed plan from from $390/mo, and platform usage billed at cost. Usage for this kind of system usually lands between $30 and $300 a month depending on volume. You see both itemised, and the platform account stays in your name.
Do we own it, or are we locked in?
You own it. The account, the numbers, the phone history and the source code are yours, and the foundation is open source. If you take it in-house, we hand over the repository and the runbook and that is the end of the conversation.
What if it breaks at 6pm on a Friday?
It is monitored. Failures raise an alert, the system degrades to something safe rather than silent, and hello@betr.agency is the inbox that answers. That is what the managed plan buys.
Can it work with the systems we already use?
Usually yes. Twilio's WhatsApp Business API access, a conversation state store, and template management we maintain for you. Where a system has no API, we look at whether an export, a shared inbox or a scheduled sync gets you 90 percent of the value for 10 percent of the cost.
Where to next
The product page for this build lists the specification, the timeline and what is included: WhatsApp Appointment and FAQ Chatbot with Twilio Flex. If you want to talk it through against your actual process, a scoping call is 30 minutes and costs nothing.