One send, thousands reached
A single scheduled broadcast replaces the manual forward-by-forward process, so the person running the sale spends the afternoon on the shop floor instead of a phone screen.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business reaches thousands of opted-in customers with one send instead of manually messaging contacts one by one.
Works with
What it does
A marketer builds an audience segment, picks an approved message template, and schedules a broadcast to go out at a chosen time. The system respects Meta's per-recipient template limits and reports delivery, read, and click rates back to the sender.
A sari showroom with four thousand saved contacts still sends its Diwali sale the old way: someone opens WhatsApp on a shop phone and forwards a photo to group after group, hoping numbers don't hit a forward limit and the message doesn't land mid-forward-tagged in someone's spam folder. Nobody knows who actually opened it.
Broadcast campaigns replace that with a proper send. A marketer picks a segment, chooses an approved template, and schedules it once. The message goes out through the same business number customers already save in their phones, paced automatically so the account's sending limit is never breached, with delivery and read counts reported back the same day.
Wavy runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Filter saved contacts by tag, purchase history, or last-contacted date, so the sari showroom's Diwali send goes to regular buyers rather than every number that ever messaged the shop once, however briefly, months ago and never again since.
Choose from templates Meta has already reviewed, fill in the variable fields — item name, offer date, store link — and preview exactly how it renders on a customer's phone screen before committing to send it out to anyone.
Set a date and time, or send immediately, and the dispatcher paces individual messages to stay inside the account's current messaging-tier limit rather than firing every message at once regardless of the ceiling Meta has currently set.
Meta's webhook reports sent, delivered, read, and failed status per recipient as it happens, so the dashboard fills in progressively through the afternoon instead of arriving as one final, delayed number long after the send went out.
Why it matters
A single scheduled broadcast replaces the manual forward-by-forward process, so the person running the sale spends the afternoon on the shop floor instead of a phone screen.
Delivered and read counts come back per recipient, so a repeat no-show segment can be dropped from the next send instead of paid for again.
Automatic pacing against Meta's tier limit means a big sale doesn't accidentally trip the same throttling mechanism that exists to catch and punish genuine spam senders on the platform.
The detail
Every WhatsApp Business Account starts on a 250-conversation-per-24-hours tier and earns a higher one only through sustained, well-received sending — there is no paid upgrade to jump the queue. Broadcast campaigns are built around this reality: the dispatcher paces the send rather than firing every message at once, and it reports back the tier the account is currently allowed, not a number the business wishes it had. A showroom's four-thousand-contact list may need two or three days of dispatching on a fresh number, not one afternoon.
Every recipient must already be opted in to receive marketing messages, and the template used must be pre-approved by Meta before it can be selected here — this tool sends approved templates, it does not get them approved (that happens in message template management). Meta also enforces a separate per-user marketing template limit that can silently cap how many messages a single template reaches in a rolling period, independent of the account tier, so a broadcast can report fewer sends than contacts even when nothing looks wrong.
Cost matters here in a way manual forwarding never made visible: every delivered marketing template is a billable conversation, charged by Meta per conversation opened, not per message inside it. A segment of contacts who reply and keep the conversation open for the following twenty-four hours costs the same one conversation fee regardless of how many messages get exchanged in that window.
Industry use cases
10 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 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 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 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 moreThe business fills more of its calendar and loses fewer no-shows by confirming and reminding customers automatically.
Learn moreQuestions
Two limits can cut the number down: the account's overall 250-conversation (or higher, once earned) 24-hour tier, and a separate per-user cap Meta places on any single marketing template. If the segment is larger than the current tier allows, the dispatcher paces the rest across the next eligible window rather than dropping them, and the dashboard shows exactly how many are still queued.
Only if they've given verifiable opt-in for marketing messages — messaging someone who hasn't written first is exactly what the marketing template category and the broader opt-in policy exist to govern carefully. The segment builder only pulls from contacts with a matching consent record on file, so an unconsented number never appears as a selectable recipient in the first place, no matter how the segment is filtered or sorted.
Each delivered marketing template opens one billable conversation per recipient, priced by Meta according to the recipient's country and the template's category, not by message count. The cost-estimate step before scheduling projects this total using the segment's size and destination countries, so there are no billing surprises waiting to appear only after the broadcast has already gone out to everyone selected in the send.
A broadcast can only be built on a template already carrying an approved status, so a rejection during review simply removes that template from the selectable list until it's fixed and resubmitted for another round. A campaign already scheduled on a previously approved template keeps sending normally regardless — approval status is checked once at send time, not retroactively revoked partway through a live campaign.
The rest of your stack
No rip-and-replace — reach opted-in customers at scale works alongside the systems already running your business.
Available today