A WhatsApp booking bot that only wakes when a guest writes
Webhooks from the WhatsApp Cloud API wake the bot, it replies and goes back to sleep. There is no always-on server, no duplicate bookings and no token in the repo.
Illustrative scenario based on patterns we see across teams building on Faable.

The team
A small group of restaurants that takes most of its bookings over WhatsApp. A freelance developer built them a Node.js bot that answers, offers times and records the booking.
The challenge
A bot on a server that runs all day costs money even when nobody writes at 4 a.m. Libraries that pair a personal WhatsApp drop off on every restart and break Meta's rules. WhatsApp retries every delivery that doesn't get a fast 200, which turns into duplicate bookings. And the access token must never end up in the repository.
How they built it
- 1
Webhooks, not pairing
The bot uses the WhatsApp Cloud API: WhatsApp calls the bot over HTTPS when a message arrives.
- 2
Asleep between conversations
With no requests for 30 minutes on Free, or 2 hours on Hobby and Pro, the app scales to zero. The next message wakes it.
- 3
Answer fast, work after
The bot verifies the signature on the raw body, answers 200 at once and does the slow work (the booking system, an LLM reply) outside the request.
- 4
No duplicate bookings
Handled message ids are stored in a database, not in memory, so a retried delivery is recognised even after the app slept or redeployed.
- 5
Secrets out of the code
The access token and the app secret live in the project's secrets. Every git push deploys, in the EU.
The result
Bookings answered in seconds, with no server running between conversations, no duplicate bookings and no credentials in the code.
