Short answer: For most independent restaurants and hotels, the best fit is an SMB messaging platform such as Wati, Respond.io, SleekFlow or Trengo. They give you a shared inbox and no-code booking flows on top of the official API. Restaurant groups that need custom builds go through infrastructure providers like Twilio, 360dialog, Vonage or Infobip. Small venues can often stay on the free WhatsApp Business App. None of these options answer phone calls, so most restaurants run WhatsApp automation alongside something that does.
Key points
- The WhatsApp Business API is Meta’s official route for automated, multi-user WhatsApp messaging. You access it through a Business Solution Provider (BSP).
- Since 1 July 2025, Meta charges per delivered template message instead of per 24-hour conversation.
- From 1 October 2026, Meta also charges for service replies and for utility messages sent inside the 24-hour customer service window. Until then, those were free.
- The right provider depends on your size, whether you want an inbox or hands-off automation, and how deeply it must connect to your reservation system.
- WhatsApp only reaches guests who message you. Phone bookings need a separate solution.
This guide walks through the real options and how to pick between them. It also covers the one channel none of them touch: the phone. That is where Bonnie comes in. Bonnie is not a WhatsApp platform. It is an AI phone assistant for restaurants that answers your calls, books the reservation, and sends the guest a WhatsApp or SMS confirmation afterwards. It sits next to your WhatsApp setup, not in place of it.
What the WhatsApp Business API is
The WhatsApp Business API, officially the WhatsApp Business Platform, is Meta’s interface for businesses that want to automate and scale their WhatsApp messaging. You don’t connect to it directly. You go through a Business Solution Provider (BSP), which gives you:
- a dashboard,
- automation and a chatbot builder,
- a shared inbox for several staff members,
- a verified business number.
Hospitality keeps coming back to it because of reach and preference:
- WhatsApp has more than 3 billion monthly users, according to Meta CEO Mark Zuckerberg on Meta’s Q1 2025 earnings call.
- In a Meta-commissioned Kantar survey of 11,056 adults across 22 markets, 73.3 percent said they prefer messaging when contacting a business.
- WhatsApp reports a 98 percent open rate for business messages, against about 20 percent for email. That figure comes from WhatsApp itself without a published methodology, so treat it as directional. Even so, a message in a chat thread gets read far more reliably than an email.
For a restaurant that runs on confirmations and quick back-and-forth, that is hard to ignore.
WhatsApp Business App vs WhatsApp Business API
| WhatsApp Business App | WhatsApp Business API | |
|---|---|---|
| Cost | Free | Meta per-message fees plus provider fee |
| Access | Download from the app store | Through a Business Solution Provider |
| Users | One phone plus a few linked devices | Many staff on one shared inbox |
| Automation | Basic quick replies and away messages | Chatbots, booking flows, automated reminders |
| Integrations | None | Reservation systems, POS, CRM, Zapier |
| Best for | A small team replying by hand | Venues that want hands-off automation |
How to get the WhatsApp Business API for your restaurant or hotel
- Set up a Meta Business portfolio (formerly Business Manager) and complete business verification with your company details.
- Choose a Business Solution Provider. The next section explains how to choose.
- Register a phone number. It can be your existing number, but a number used on the WhatsApp Business API can’t also run on the regular WhatsApp app at the same time.
- Get your display name approved. This is the name guests see, and it should match your venue’s name.
- Create and submit message templates for booking confirmations, reminders and review requests. Meta reviews each template and assigns it a category: marketing, utility or authentication.
- Collect opt-in. Guests must agree to receive messages from you, for example via a checkbox in your booking form.
- Connect your reservation system so bookings and confirmations flow automatically instead of being retyped.
With an SMB platform, steps 2 to 7 usually take days rather than weeks, and your provider guides you through most of them.
How to choose one for a restaurant or hotel
Start with what you actually need it to do. The gap between tools is mostly about depth:
- A café that just wants to answer messages barely needs the API.
- The moment you want automated reminders, a chatbot taking bookings overnight, or three staff on one inbox, a paid provider earns its place.
After that, check these five criteria:
- Reservation and POS integration. A WhatsApp booking shouldn’t become a second thing to retype.
- No-code vs developer-only. Can a manager build a flow, or do you need a developer?
- Pricing model. You pay Meta per message plus a provider fee, and both grow with volume.
- Languages. Does it handle the languages your guests write in?
- GDPR and data location. This matters more in Europe than most vendor pages admit.
The main options, by type
| Type | Examples | Best for | Watch out for |
|---|---|---|---|
| Free WhatsApp Business App | Meta | Small teams replying by hand | No automation, no real shared inbox |
| Infrastructure BSPs | Twilio, 360dialog, Vonage, Infobip | Scale and custom builds | More setup, often needs a developer |
| SMB inbox and automation | Wati, Respond.io, SleekFlow, Trengo | No-code flows and a shared inbox | Per-message costs add up at volume |
| Hospitality chatbots on the API | Various restaurant chatbot tools | Reservations, orders, reminders | Still doesn’t answer the phone |
Most independent restaurants land in the third row. Trengo is worth a look if you’re in the Netherlands or elsewhere in Europe, since it is a Dutch company. The first row is a perfectly good starting point if you’re not ready to spend. Plenty of small places run for years on the free app alone.
Providers at a glance
| Provider | Type | Headquarters | No-code flows | Good fit for |
|---|---|---|---|---|
| Trengo | SMB inbox | Netherlands | Yes | European restaurants and hotels wanting one inbox for all channels |
| Wati | SMB inbox | Singapore | Yes | Small venues that want quick setup |
| Respond.io | SMB inbox | Malaysia | Yes | Multi-location groups with several channels |
| SleekFlow | SMB inbox | Hong Kong | Yes | Venues combining messaging with sales flows |
| 360dialog | Infrastructure | Germany | Limited | Teams with a developer, EU-based setup |
| Twilio | Infrastructure | United States | No, developer-led | Custom builds at scale |
Check current pricing and integrations on each provider’s site. Both change often.
What the WhatsApp Business API costs in 2026
There is no flat price. You pay Meta per message, and your provider adds its own fee on top. Meta’s rules changed twice in a short period.
Since 1 July 2025:
- Meta charges per delivered template message, not per 24-hour conversation.
- Templates are billed by category: marketing, utility or authentication.
- Twilio’s help center explains the old conversation-based model and what replaced it.
From 1 October 2026, according to Meta’s developer documentation:
- Meta charges per message for service messages, meaning the free-form replies your staff or a third-party AI send when a guest messages you. These have been free since November 2024.
- Meta also charges for utility messages sent within the open 24-hour customer service window. These have been free since July 2025.
- Service messages cost the same per-message rate as utility and authentication messages in each market.
- There are no volume discounts on service messages.
What stays free: messages sent in the 72-hour window after a guest reaches you through a Click to WhatsApp ad or a Facebook call-to-action button.
What this means for a restaurant: from October, every reply in a busy WhatsApp inbox counts. A confirmation, a reminder and three answers to “can we bring the dog?” become five charges instead of one or none. Check with your provider how it passes these costs on, and keep an eye on which messages you actually need to send.
What WhatsApp automation is genuinely good at in hospitality
This is the part that earns the setup:
- Booking confirmations that land instantly.
- Reminders the day before and a couple of hours out. This is the biggest single lever on no-shows. Operator and vendor data puts the reduction from automated confirmations and reminders at roughly 27 to 38 percent, and in the same data, 36 percent of guests who missed a booking said a reminder would have brought them in. Most no-shows are forgotten bookings, not deliberate ones.
- Pre-arrival details for hotel guests.
- Quick answers to the questions you get twenty times a week.
- Review requests after a good visit.
- Win-back broadcasts to guests who haven’t been in for a while.
On all of that, a well-built WhatsApp flow quietly does the work of an extra pair of hands.
The channel WhatsApp automation can’t cover
WhatsApp automation only works with guests who message you, and a lot of guests still call. They tend to call for the bookings that matter most:
- a table for a large group,
- a last-minute change,
- a question they’d rather ask out loud.
A WhatsApp bot doesn’t answer the phone, however good it is.
The staffing picture makes this worse. In the Netherlands, CBS reported that open vacancies in hospitality rose to 27,000 in the first quarter of 2026, even as vacancies fell across the wider economy. According to CBS business survey data cited by ABN AMRO, almost 40 percent of hospitality businesses reported staffing constraints. Nearly one in five restaurants and cafés limited what they offered to match the staff they had. When the team is short, the phone is the first thing that goes unanswered during service.
That’s not a knock on WhatsApp. Your busiest booking channel and your most automated one are often two different things, and the phone is the one that quietly leaks. A call that rings out leaves no message, no chat log and no trace in any dashboard. You only find out you lost it when the table stays empty.
Where Bonnie fits next to your WhatsApp setup
Bonnie covers the side WhatsApp can’t:
- It answers every call, in more than 20 languages.
- It puts the reservation straight into the system you already use, such as Formitable or Zenchef.
- It sends the guest a confirmation over WhatsApp or SMS, so both channels tell the same story.
- Every Bonnie plan includes a bundle of WhatsApp and SMS messages, and Bonnie also connects to Zapier.
Bonnie doesn’t run your marketing broadcasts or your WhatsApp inbox, and it isn’t trying to. It makes sure the phone stops being the hole in an otherwise automated operation. WhatsApp for the guests who type, Bonnie for the ones who call, and the same confirmation either way.
A scenario from practice
A guest sees your Click to WhatsApp ad and asks whether you’re open on Sunday. Your WhatsApp flow answers in seconds and sends a booking link. That is the channel doing exactly what it’s built for.
An hour later, a different guest calls to book a table for ten for a birthday. No chatbot is involved. If nobody gets to the phone, that party of ten books somewhere else and you never hear about it.
With Bonnie, that call is answered on the first ring. The booking goes into your reservation system, and the guest gets the same WhatsApp confirmation as the first one. Two front doors, one tidy booking book. That’s usually what hospitality automation looks like once you stop treating it as a single tool and start treating it as coverage.
FAQ
What’s the difference between the WhatsApp Business App and the API?
The app is free, runs on one phone and a few linked devices, and someone replies by hand. It suits a small venue. The API is the official, paid version you access through a provider. It lets you automate replies, run chatbots and put several staff on one inbox. If you want anything hands-off, you need the API.
How much does the WhatsApp Business API cost?
There is no fixed price. Meta charges per delivered message, based on the message category and the guest’s country, and your provider adds its own fee. From 1 October 2026, replies within the 24-hour customer service window are also charged, so busy inboxes will cost more than before. See Meta’s pricing page for current rates per country.
Can WhatsApp automatically take restaurant reservations?
Yes, if you use the API with a chatbot that supports bookings. The free app can’t do this. The bot shows availability, collects the details and pushes the booking to your reservation system. It only works for guests who message, though. For guests who call, Bonnie takes the reservation on the phone, enters it into Formitable or Zenchef, and sends a WhatsApp or SMS confirmation afterwards.
Does WhatsApp automation replace answering the phone?
No. WhatsApp only reaches guests who message you. Callers are a separate group, and often the ones booking the biggest tables. That’s the gap Bonnie fills: it answers calls in more than 20 languages, books them in, and sends the WhatsApp confirmation after.
Do I need a developer to set up the WhatsApp Business API?
Usually not with SMB platforms such as Wati, Respond.io or Trengo. They’re built so a manager can create flows without code. Infrastructure providers such as Twilio give you more control but expect technical setup.
Is the WhatsApp Business API GDPR-compliant?
The API itself can be used in a GDPR-compliant way, but compliance depends on your setup. You need guest opt-in, a clear privacy statement, and a provider with a data processing agreement. European venues often prefer an EU-based provider for data location. Check this with your provider before you go live.
See the phone side for yourself
WhatsApp handles the guests who message. Bonnie handles the ones who call, and sends the WhatsApp confirmation either way. It’s live the day after you sign up, setup takes well under half an hour, and it works with the reservation platform you already use.