Use the WhatsApp Business Platform or Coexistence, connect it to a unified inbox, build a short booking flow, and keep audit-proof opt-in records to satisfy ACMA rules. Start today by enabling click-to-chat and checking your eligibility for the API. Wattle and similar platforms exist precisely to turn this stack into a working front desk rather than a side project.
TL;DR:
- Coexistence preserves the WhatsApp number, message history, and contacts, but you must open the Business app once every 13 days to keep it active.
- The 24 hour window for free form replies makes an approved booking or reminder template necessary for messages sent after that period.
- ACMA requires express or inferred consent, clear sender identification, and a free unsubscribe option; record each opt in’s timestamp, source, and method in exportable logs.
- Escalate after two failed attempts, when frustration appears, or when someone requests a person; give staff captured details, prior actions, and the transcript.
- Check live calendar availability, create a booking only after the customer confirms a specific slot, then send a secure payment link or invoice.
WattleBring WhatsApp Support Into One InboxWattle helps teams manage WhatsApp conversations, book appointments, and hand complex questions to staff from one workspace.Explore Wattle
Table of Contents
- Setting up WhatsApp for support: coexistence vs API
- How to design a unified inbox and handoff so humans never repeat questions
- Automating bookings, payments and calendar sync from WhatsApp
- ACMA compliance: consent, unsubscribe and audit records for WhatsApp messaging
- Metrics, SLAs and routine checks to keep WhatsApp support reliable
- How Wattle approaches WhatsApp support in practice
- What actually matters when you build this
- Try WhatsApp support built around booking and compliance
- FAQ
- Sources
Setting up WhatsApp for support: coexistence vs API
The first decision is whether you need Coexistence or the full WhatsApp Business Platform. Coexistence lets you keep using the WhatsApp Business app on your phone while connecting the same number to the API, so your message history and contacts carry over and you can scale gradually. The Coexistence documentation confirms the number and message history persist, and that you must open the app at least once every 13 days to keep coexistence active. Choose the full API instead when you are scaling from day one and do not need the consumer app as a fallback.
Onboarding follows a fixed sequence regardless of which path you pick:
- Verify your business phone number and confirm it can receive an SMS or voice code.
- Register your business details with Meta, including display name and category.
- Connect a webhook so incoming messages and status updates reach your inbox or platform.
- Submit your welcome and notification templates for approval before sending anything outbound.
- Open the WhatsApp Business app at least once every 13 days if running coexistence.
Your minimal launch flow needs four things in place before you send a single message: a click-to-chat link on your website and socials, an approved welcome template, a clear understanding of the 24 hour free-form messaging window, and at least one approved notification template for bookings or reminders. Get those four right and you have a working channel, not just a connected number.
How to design a unified inbox and handoff so humans never repeat questions
A support bot that hands off badly costs you the customer’s patience twice: once when they wait for the bot, and again when a human asks the same questions from scratch. The fix is passing full context forward, not just the message.
- Carry captured fields (name, booking type, order number) into the handoff payload, not just the raw chat.
- Attach the detected intent and which flow step the bot was on when it stalled.
- Include any failed actions or validation errors so the human knows what has already been tried.
- Pass the transcript and an AI-generated summary rather than making staff scroll the whole thread.
Set explicit handoff triggers rather than hoping staff notice a stuck conversation: escalate after two failed attempts at the same step, when frustration language appears, or the moment a customer asks for a person. Insist your inbox supports a mobile-installable view, search by phone number, threaded history per customer, and summaries attached directly to the conversation, because a handoff without those is just a longer queue.
Pro Tip: Treat the inbox as a live conversation layer, not a ticketing backlog. Staff should see what the bot already tried before they type a single word.
Automating bookings, payments and calendar sync from WhatsApp
A booking flow only earns its keep when it moves a customer from “I’d like an appointment” to a paid, confirmed slot without a phone call. That means task-scoped steps with exact-action confirmation before anything is written to your calendar or billed to a card.
A working sequence looks like this:
- Capture the service type, preferred date range and contact details inside the chat.
- Check real availability against your connected calendar before offering times.
- Create the booking only after the customer confirms the specific slot.
- Send a payment request, either a secure Stripe link or an invoice-first option depending on the service.
- Confirm the booking and payment status back to the customer in the same thread.
The integrations that make this possible are Google Calendar or Cal.com for availability and booking, Stripe for payment collection, and Xero or QuickBooks Online for invoicing. Wattle’s own booking flow for WhatsApp appointments follows this exact capture, confirm, pay sequence, built around task-scoped actions that require explicit confirmation before anything changes in your calendar or your books.
ACMA compliance: consent, unsubscribe and audit records for WhatsApp messaging
Commercial messaging on WhatsApp sits squarely inside Australian spam law, and treating it as a grey area is how businesses end up with an infringement notice. ACMA requires express or inferred consent before you send commercial messages, clear identification of your business as the sender, and a functional, free unsubscribe mechanism that you honour promptly.
Businesses that skip sender identification or a working unsubscribe facility are a recurring theme in ACMA’s published investigations and infringement notices, which show enforcement against companies sending marketing SMS and WhatsApp messages without proper consent records.
Welcome sequences and retention nudges are not automatically exempt as “transactional” messages. ACMA’s guidance on common telemarketing and e-marketing mistakes flags this misclassification as a frequent pitfall, so a welcome message that drifts into promotion needs the same consent and unsubscribe treatment as a marketing blast.
Build your audit trail before you need it, not after a complaint:
- Record the timestamp, source and exact method of each opt-in (web form, in-store, verbal confirmation).
- Store the retention period for consent records and review it on a fixed schedule.
- Test your unsubscribe flow yourself every quarter to confirm it still works end to end.
- Keep exportable logs so you can respond to a complaint or audit without reconstructing history from memory.
Our own checklist of the opt-in records worth keeping covers the seven specific records that hold up under scrutiny, which is a useful companion once you have the policy settled. For a broader view of how spam and Do Not Call Register rules apply to automated outbound messaging generally, this plain-English compliance guide is a solid reference.
Metrics, SLAs and routine checks to keep WhatsApp support reliable
A channel you cannot measure is a channel you cannot improve, and WhatsApp support has its own set of numbers worth watching weekly rather than quarterly.
- Track containment rate: the share of conversations the bot resolves without a human touching them.
- Watch first-response time and handover rate separately, since a fast bot reply can mask a slow human handoff.
- Measure booking completion rate from first message to confirmed, paid appointment.
- Monitor unsubscribe and complaint volumes as an early warning for consent or messaging problems.
Set your own operational targets rather than treating any figure as a fixed rule, since what counts as healthy varies by industry and message volume. Staff coverage should match your busiest messaging windows, with a clear after-hours rule: either the bot handles routine enquiries alone overnight, or urgent topics escalate to an on-call number. Reporting needs to cover AI-generated conversation summaries, a live appointment list, and exportable audit events your compliance review can pull without engineering help, which is exactly what our feature set is built to surface.
How Wattle approaches WhatsApp support in practice
Everything above maps directly onto how we’ve built Wattle’s omnichannel platform. Calls, WhatsApp messages, SMS and web chat all land in one inbox, so a customer who messages on WhatsApp and later calls gets a human who already has the full thread, not a blank screen.
Opt-in records are kept automatically against every contact, with six-digit verification required before any protected action, like confirming a booking change or releasing payment details, goes through. Google Calendar and Stripe integrations turn a WhatsApp message into a checked, booked and paid appointment without a staff member touching a spreadsheet, and Xero or QuickBooks Online handle the invoice on the other end.
We built booking flows designed so a bot never books, cancels or charges anything without exact-action confirmation first. We say plainly that missed calls and messages mean missed jobs, and the point of a connected inbox across phone, web, WhatsApp and SMS is that nothing falls through a channel gap again.
What actually matters when you build this
Most advice on WhatsApp support obsesses over automation scope: how many enquiries the bot can close without a human. That number matters less than whether your handoff preserves context, because a customer who has to repeat themselves to a human is often more frustrated than one who never spoke to a bot at all.
The bigger blind spot is compliance. Businesses spend weeks tuning conversation flows and then bolt on consent tracking as an afterthought, right before a complaint forces the issue. Opt-in records, clear sender identification and a working unsubscribe facility are not paperwork on top of your WhatsApp strategy. They are the foundation that keeps the channel open at all, and ACMA’s enforcement history shows the cost of skipping them.
If you are starting from zero, build the audit trail and the handoff policy before you build the clever booking flow. A support channel that resolves half your enquiries but keeps shaky consent records is a liability. One that resolves fewer enquiries but never loses a customer’s context, and never sends a message without proper consent, is the one that lasts.
— Christopher
Try WhatsApp support built around booking and compliance
We built Wattle to be the front desk you would hire if you could: it answers on WhatsApp, phone, web chat and SMS, books the appointment, takes the payment, and hands anything sensitive to a real person with full context attached.
- Plans include the unified inbox, booking automation and six-digit verification described above.
- Starter runs $99 per month, Pro at $499, and Max at $999, all billed monthly on our pricing page.
- Connect calendar, payment, and invoicing services during setup, no separate integration project required.
Check the plans and features that fit your support volume on our pricing page, or review the full capability list on our features page before you commit.
FAQ
What is the difference between WhatsApp Business app and the API?
The WhatsApp Business app is a free, single-device app for small volumes, while the WhatsApp Business Platform (API) supports automation, multiple agents and higher volume messaging. Coexistence lets you run both against the same number during a transition, preserving your number and message history.
Do I need customer consent to message on WhatsApp for business?
Yes. ACMA requires express or inferred consent for commercial messages, along with clear sender identification and a working unsubscribe option that you act on promptly.
How do I keep an audit trail for WhatsApp opt-ins?
Record the timestamp, source and method of each opt-in, along with your retention policy, and store it somewhere exportable for a compliance review. Our opt-in records checklist sets out the specific records worth keeping.
Can WhatsApp support handle bookings and payments directly?
Yes, when connected to a calendar and a payment processor, a WhatsApp flow can check availability, confirm a booking and send a payment request in the same conversation. Our task-scoped booking flow uses exact-action confirmation before anything is booked or charged.
What happens if a bot cannot resolve a WhatsApp enquiry?
A well-designed flow escalates to a human after a set number of failed attempts or on detecting frustration, passing the full transcript and captured details along with it. This avoids making the customer repeat information they already gave the bot.