Client onboarded
Your agency sets up a workspace for the client, connects the client's Meta Business number, and imports the client's opted-in contact list with consent records.
Industry · Marketing Agency
Marketing agencies use Wavy to manage WhatsApp campaigns across multiple client workspaces, collaborate with team members in a shared inbox, and run consent-aware broadcasts with template approval and human review gates. Campaign workers recheck opted_in contacts and campaign launch uses an approved template and review gate; other sends follow separate controls.
What Wavy does for marketing agencies
These are the workflows Wavy is built to support for digital marketing agencies, WhatsApp marketing service providers, and social media agencies managing client campaigns. Each job has a clear input, a review boundary, and an honest output state.
1. Multi-client campaign management. Your agency manages WhatsApp campaigns for multiple clients. Each client can have its own workspace with its own WhatsApp Business number, contact list, and approved templates. Your team creates campaigns within the appropriate client workspace, builds segments from opted-in contacts, and submits each campaign to a review queue. A human reviewer — either your team member or the client's — must approve the campaign before any message is dispatched to the provider.
2. Template creation and approval tracking. For each client, your team creates message templates and submits them to Meta for approval. Wavy surfaces the approval status honestly — a template cannot be used in a campaign until Meta approves it. Your team can see which templates are approved, pending, or rejected across all client workspaces, and plan campaign schedules accordingly.
3. Team collaboration and client reporting. Multiple team members can work in the same shared inbox — handling inbound replies, drafting campaign messages, and reviewing AI-suggested responses. The AI assistant, if enabled, can draft reply suggestions, but no draft is sent without human review and approval. Campaign delivery states (queued, delivered, read, failed) are tracked per message, giving your team honest data for client reporting.
Example workflow
This is an illustrative workflow showing how the pieces fit together for an agency managing a client campaign. It is not a promise of outcomes — your results depend on your own provider configuration, contact quality, and message content.
Your agency sets up a workspace for the client, connects the client's Meta Business number, and imports the client's opted-in contact list with consent records.
Your team creates a campaign template for the client and submits it to Meta. Wavy shows the template's approval status — it cannot be used until Meta approves it.
Opted-in contacts are segmented based on the campaign target audience. Contacts without opt-in are excluded — suppression is enforced before the campaign is created.
The campaign is scheduled with the approved template and opted-in segment. It enters a review queue — a human (agency or client) must approve it before dispatch.
After approval, messages are sent through the WhatsApp Cloud API. Wavy tracks each message as queued, accepted, delivered, read, or failed across the client workspace.
If any contact replies 'STOP' or asks to opt out, Wavy suppresses all future campaign messages to that contact immediately — across all campaigns in the workspace.
Provider and configuration dependencies
WhatsApp Business API (Meta Cloud API). Each client must connect their own Meta Business account and WhatsApp Business number. Wavy does not provide shared numbers — each client's message reputation, quality rating, and template approvals belong to their own Meta account. Your agency manages campaigns within each client's workspace, but the provider relationship is the client's.
Approved message templates. Every campaign template must be submitted to and approved by Meta before it can be used. Wavy surfaces the approval status per template per workspace; it cannot bypass Meta's review. Templates rejected by Meta cannot be used until revised and re-approved.
Contact opt-in records. Each client is responsible for maintaining evidence of consent for their contacts. Wavy enforces suppression for contacts who opt out, but the initial opt-in records are the client's responsibility. Your agency should verify that imported contact lists have valid opt-in evidence.
Optional: AI assistant. If enabled per workspace, the AI assistant can draft suggested replies for inbound conversations. Copilot drafts are returned for human review; bot connectors are a separate path and are not represented by this draft flow.
Consent and review boundaries
Wavy is designed so that no consequential action happens without a human decision. Specifically:
• Campaign broadcasts require reviewer approval in the campaign queue before they are sent to the provider — this applies to every client workspace.
• AI-drafted replies are suggestions in the inbox — they are never sent to a contact without a human clicking approve.
• Template usage is gated by Meta's approval — Wavy shows the status honestly and prevents use of unapproved or rejected templates.
• Opt-out requests are processed immediately — once a contact opts out, no campaign message will be dispatched to them, even if they remain in a scheduled segment.
Questions
Yes. Wavy supports multiple workspaces, each with its own WhatsApp Business number, contact list, and templates. Your agency team can work across workspaces, but each campaign enters a human review queue before dispatch — no campaign is sent autonomously.
Wavy can schedule campaigns, but each scheduled campaign enters a human review queue before dispatch. Recurring campaigns require fresh approval for each send — Wavy does not auto-dispatch without human review.
Wavy tracks honest per-message delivery states — queued, accepted, delivered, read, and failed. These are provider receipts, not engagement metrics. Your team can use this data for client reporting, but Wavy does not fabricate performance numbers or attribution data.
The AI assistant can draft reply suggestions for inbound conversations. It does not generate campaign templates autonomously — your team creates and submits templates to Meta for approval. No AI-generated message is sent without human review.
Set up workspaces for each client, connect their Meta Business numbers, import opted-in contacts, and start managing campaigns — with human approval gates at every consequential step.