Operator guide
WhatsApp Business app or Platform: choose the booking workflow
Compare a staff-managed WhatsApp conversation with a configured booking integration. Check number setup, handover, current message billing and migration before deciding.
By Gideon Langenhoven · Updated
Choose the workflow
Start with the enquiry your team needs to handle.
The decision is about the work around a conversation: who checks departure capacity, shares the booking link, confirms payment and handles exceptions. Count actual enquiries and staff handovers, then demonstrate the required workflow. There is no universal conversation-count threshold where every operator must switch.
Meta describes the Business app as a tool for customer conversations, business profiles and product information. A BookingTours Platform integration connects configured tour information, departure selection, temporary holds, web checkout and staff takeover. Integration setup is what connects those steps; access to an API alone does not reserve an external venue or prove payment.
Decision checklist
Test the requirements that change the choice.
Can staff check the departure in the booking system, share the right link and verify payment without a second diary? This can be a useful starting workflow before automating the conversation.
Demonstrate website, staff and WhatsApp requests for one departure, including an expired hold and unavailable capacity. Confirm which inventory is actually connected; a ferry or tasting reservation may need a separate confirmation.
Show the selected account's staff permissions, takeover and resume behaviour. Test a request the assistant cannot answer and a failed notice. No unlimited-agent or instant-response claim is assumed.
Use sample enquiries in the languages your guests use. Agree appropriate contact permissions, templates, escalation and data handling before using booking data in campaigns.
Confirm number ownership, migration or coexistence eligibility, history handling and fallback with the selected provider. Do not promise that a number migration preserves every chat or finishes within a fixed approval period.
Separate bills
Model the WhatsApp bill from the current account terms.
Operators settle their WhatsApp bill separately with WhatsApp. BookingTours software is R2,000/month for one admin, R500/month per additional admin and R500/month total during a pause, all including VAT. Onboarding is free. Payment processing, distribution and other quoted usage charges remain separate.
Meta's Platform pricing page, checked 2 October 2026, describes delivered-message pricing by market and category. It states that service replies within the customer-service window are free, with eligible utility responses also free. Use its current rate card and your account terms for billable messages and applicable volume tiers. This guide does not assert an October 2026 service-message charge or invent a Rand rate.
For a cost review, record the billing market/currency, message categories, billable delivered counts, quoted rates, taxes, any provider charges and quote date. Reconcile that bill separately from the software subscription. Use the annual cost calculator with those entered amounts.
Safe migration
Agree the cutover and the fallback.
Validate future bookings, deposits/balances, current capacity and guest contact permissions before switching links or a number. Assign a person to approve go-live and reconcile failed messages and uncertain payments. Keep an agreed fallback for incoming enquiries while account approval is pending.
Ask for a demonstration using synthetic records: one successful booking, an expired hold, a payment with uncertain confirmation and a staff takeover. A sample conversation is not an independent operator result. Cancellation is available at any time with access to collected data; agree the access/export process with the team.
Five-step WhatsApp journey · Migration checklist · Integration scope · Questions and corrections
Questions
Check the decision with your team.
Does Platform access alone automate my bookings?
No. Confirm the configured tour, availability, checkout, permissions and staff handover path. An API or generic webhook is not proof of an approved venue or OTA connection.
Who pays the WhatsApp bill?
The operator settles its bill separately with WhatsApp. Use the account’s current rates and actual billable messages; software, card processing and distribution costs are separate.
Will a number change preserve every conversation?
Confirm migration/coexistence eligibility and history handling for the selected provider before changing a number. Agree a lawful access/export process and a fallback; no universal history-transfer or approval-time promise is made.
Get started
Bring the booking and exception to a demonstration.
Use sample records to check the workflow before approving a migration.
View the demo without signing up · AI answers 24/7 · off-season pause R500/month