A defensible answer in disputes
The audit trail shows exactly how and when consent was captured and for which category, which is the difference between a documented answer and no defence at all in a dispute.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business stays compliant with WhatsApp's messaging policy and avoids number bans by only messaging people who have actively agreed to be contacted.
Works with
What it does
Every contact record stores how and when consent was captured (website form, checkout checkbox, in-store QR scan) along with which message categories they agreed to receive. Any broadcast or automated sequence checks this consent record before sending and immediately honors opt-out requests, including WhatsApp's own STOP-style replies.
A wellness clinic's WhatsApp number gets suspended after a batch of promotional messages goes to a list somebody exported from an old walk-in register — patients who gave their number for appointment confirmations, not marketing, and several reported the messages as spam. Nobody had a record proving what those patients actually agreed to.
Opt-in and consent management is the record that would have stopped that. Every contact stores exactly how and when consent was captured — a website form, a checkout checkbox, an in-store QR scan — and which specific message categories they agreed to. Any broadcast or sequence checks this record before sending, and an opt-out, including WhatsApp's own STOP-style replies, is honoured immediately across every pending send.
Wavy runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
A website form, checkout checkbox, or in-store QR scan records the moment a customer agrees to be messaged, along with exactly which categories — order updates, marketing, appointment reminders — they specifically consented to receiving.
Before any broadcast or automated sequence fires, it checks that each recipient has an active, category-matched consent record already on file, excluding anyone who genuinely doesn't have one on record from that specific send entirely.
A customer's STOP-style reply or an explicit opt-out request is detected and applied instantly, removing them from every pending broadcast and sequence across the whole account at once, not just the one they replied to.
The consent audit exporter can produce a full compliance record — source, timestamp, category — on demand, giving the business documented proof if a customer ever disputes agreeing to be messaged at all in the first place.
Why it matters
The audit trail shows exactly how and when consent was captured and for which category, which is the difference between a documented answer and no defence at all in a dispute.
A customer who says stop is removed from every pending broadcast and sequence across the whole account at once, rather than having to separately unsubscribe from each list a business happens to run.
Consent captured for order updates doesn't get treated as consent for promotional content, which is exactly the mismatch that got the wellness clinic's number suspended.
The detail
Since November 2024, WhatsApp's policy places the burden of proving opt-in on the business, not on Meta — if a customer disputes ever agreeing to receive a message, it's the business that has to produce evidence, and the audit trail this capability maintains is that evidence. A business with no consent record has no defence beyond its own word against the customer's, which is a losing position in any dispute Meta adjudicates. This is not a theoretical risk: it is the exact mechanism the wellness clinic's suspension worked through.
Consent is category-specific, and this distinction is where businesses most commonly get caught out. A patient who provided their number specifically for appointment confirmations has consented to utility-category messages about that appointment — nothing about that consent extends to marketing messages about a seasonal promotion. Reusing consent captured for one category to justify sending a different category is a policy violation even though a consent record technically exists, because the record doesn't cover what was actually sent.
Failing to honour an opt-out is treated as seriously as never having consent in the first place, and it can lead to WABA suspension — the entire WhatsApp Business Account, not just the offending contact's messages. This makes the opt-out propagation worker one of the highest-stakes pieces of this whole capability: it has to catch and apply every opt-out signal, including WhatsApp's own built-in STOP-style replies, immediately and across every pending send, because a delay of even a day can mean one more message going to someone who already asked to stop.
Industry use cases
13 industries where Wavy applies this directly.
A customer messages a dealership's WhatsApp number after seeing a Click-to-WhatsApp ad, browses the vehicle catalog in-chat, and books a test drive slot through a native form that checks the showroom's real-time calendar.
See the automotive playbookA prospect fills out a website contact form, receives an automated WhatsApp qualification flow asking about company size and budget, and is routed to the assigned account executive's shared inbox queue the moment they answer "yes" to wanting a demo.
See the b2b sales playbookA lending business sends a one-time passcode via an authentication template when a customer logs into their loan portal, and later sends a utility template reminding them a payment is due in three days.
See the banking and finance playbookA shopper browses a product catalog inside WhatsApp, adds a lipstick shade to their cart, doesn't complete checkout, and receives a reminder message with the exact shade and a link back to the cart twenty minutes later.
See the beauty and cosmetics playbookA prospective student messages an ed-tech company's number, completes a lead-capture flow asking about the course of interest, and is booked into a counselor's calendar slot without ever leaving WhatsApp.
See the education playbookA freelance designer sets up a simple keyword-triggered flow so new client inquiries automatically receive a portfolio link and a booking form for a discovery call.
See the freelancers and consultants playbookA patient books a consultation through a native form, receives a reminder template the morning of the appointment with confirm/reschedule quick-reply buttons, and gets a post-visit follow-up message asking for feedback.
See the health and wellness playbookA customer asks about curtain pricing via a click-to-chat website widget, browses a curated catalog of fabric options in-chat, and receives a follow-up message a day later if they didn't confirm an order.
See the home decor and furnishing playbookAn agency manages WhatsApp numbers for three retail clients inside one Wavy workspace, with agents scoped to only the numbers for their assigned client and separate campaign-performance dashboards per brand.
See the marketing agencies playbookA buyer clicks a Click-to-WhatsApp ad for a listed property, answers a short qualification flow about budget and timeline, and books a site-visit slot through a native form connected to the agent's calendar.
See the real estate playbookA diner messages the restaurant's number to check table availability, receives a native booking form to select party size and time, and gets a confirmation template once the table is locked in.
See the restaurants and food playbookA regular client receives an automated reminder that their usual six-week haircut appointment is due, taps a quick-reply button to confirm the suggested slot, and gets a same-day reminder message before their visit.
See the spas and salons playbookA traveler inquires about a weekend package via a QR code at a travel fair booth, completes a native form capturing travel dates and group size, and receives a utility template confirming the booking with itinerary details attached.
See the travel and tourism playbookMore from Wavy
The business reaches thousands of opted-in customers with one send instead of manually messaging contacts one by one.
Learn moreThe business answers routine questions instantly, day or night, without adding support staff.
Learn moreThe business collects clean, structured customer data (bookings, orders, applications) without redirecting people to an external website.
Learn moreMultiple staff members handle customer conversations from one WhatsApp number without stepping on each other or losing context.
Learn moreCustomers browse products, ask questions, and place an order without leaving the WhatsApp conversation.
Learn moreThe business wins back sales that would otherwise be lost when a customer starts checkout but doesn't finish.
Learn moreQuestions
Since November 2024, the burden of proof sits squarely with the business, not Meta — you need to produce the specific consent record: the source (website form, checkout, QR scan), the timestamp, and the category they agreed to. This system's audit log exists specifically to be that evidence; without it, a dispute comes down to your word against the customer's word entirely.
No. Consent is category-specific — agreeing to order-status updates doesn't cover marketing messages at all, and sending promotional content on the strength of a different category's consent is a genuine policy violation even though a consent record technically exists already for that contact on file. A separate, category-matched opt-in is required before any marketing messages can go to that person.
Immediately, and across every single pending broadcast and sequence at once, not just the one the customer originally replied to in order to stop everything. The opt-out propagation worker is built to catch this instantly, including WhatsApp's own STOP-style replies, because failing to honour an opt-out promptly is treated as a genuinely serious policy violation that risks account suspension entirely.
Without a documented consent record, the business has essentially no defence in that dispute at all to fall back on, and the outcome can include restrictions or suspension of the WhatsApp Business Account itself. This is precisely the scenario the audit trail exists to prevent — a contact with no verifiable, category-matched consent shouldn't be receiving marketing messages in the first place.
The rest of your stack
No rip-and-replace — message only customers who said yes works alongside the systems already running your business.
Available today