Shared team inbox
Bring WhatsApp conversations into one queue with assignment, tags, and team ownership. The inbox API and route exist; live messages require a verified provider channel.
Available interfaceMeet Wavy · WhatsApp customer engagement
Every customer conversation, moving in the right direction.
Wavy brings inbox, campaigns, templates, contacts, rules, AI assistance, and payment-provider paths into one WhatsApp workspace — with human review where it matters.
- Cloud API first
- One team inbox
- Approval-aware workflows
AI CopilotConfig dependent
CampaignApproval required
PaymentProvider gated
Oneshared team inbox
Humanreview at the edge
Clearprovider receipt states
Safesynthetic-first QA
One WhatsApp operating system
From first message to a useful next step.
Each part works alone. Together they give your team one connected customer journey. Capability labels show what is implemented, what needs configuration, and what is planned.
Campaign drafts
Prepare approved template messages for opted-in audiences and keep receipt states distinct. Launch is gated by owner-or-admin approval and an approved template.
Available interfaceCampaign attribution
Campaign receipts show delivery, read, and failure counts per send. Conversation-to-action attribution, ROAS, revenue tracking, and repeat-purchase linking are planned and require a verified analytics backend that does not exist yet.
PlannedAI Copilot
Draft replies, summarize long chats, translate messages, and score conversation quality. The Copilot service degrades gracefully when no LLM key is configured.
Configuration requiredRules & automation
Create welcome, keyword, routing, and custom bot-handoff rules with explicit enabled toggles. Rule execution runs on inbound webhook events.
Available interfaceContacts & segments
Organize contacts, attributes, CSV import/export, and audience segments. Opt-in is tracked per contact; importing does not grant messaging consent.
Available interfaceConsent & suppression
Per-contact opt-in tracking, audience segment consent rules, and suppression checks are enforced before campaign launch. The opt-in field is stored per contact; importing does not grant consent.
PartialTemplates
Create, submit to Meta, sync, and manage message templates. Only templates with Meta-approved status may be used in campaign launches.
Available interfaceApproval & review gate
Campaign launches require owner-or-admin approval and an approved Meta template before execution. AI Copilot drafts are returned for human review and are never auto-sent. The approval boundary is enforced in the campaign launch path and AI draft workflow.
Available interfacePayment provider paths
Provider paths for UPI links, Razorpay, PhonePe, and Stripe Link exist in code. Live charging requires configured credentials, webhook verification, and reconciliation.
Configuration requiredAnalytics overview
Ticket counts, message-status breakdowns, bot-vs-operator splits, and average CX scores. Full ROI and attribution dashboards are on the roadmap.
PartialProvider receipt states
Distinguish queued, sent, delivered, read, failed, and unknown provider states. Queue acceptance is not delivery; a provider message ID is required before marking sent. Campaign stats track an 'accepted' count when the provider queue receives a send, but 'accepted' is not yet a first-class message or recipient status in the data model, so provider acceptance and verified delivery remain distinct.
PartialCRM sync
An Airtable upsert helper runs on contact create/update. Sync is best-effort and never blocks the main request path.
Configuration requiredWhatsApp Commerce
A catalog route and solution page exist. Product catalog management, inventory sync, and full commerce flows are planned and not yet implemented.
PlannedClick-to-WhatsApp Ads
Ad-sourced conversation attribution and CAPI conversion upload are planned. No ad-management backend exists yet.
PlannedForms & chat widget
Structured in-chat form capture and an embeddable website chat widget are planned. Solution pages exist as placeholders.
PlannedA reviewable workflow
Connect. Configure. Review.
- 01Connect a verified channelUse a separately verified WhatsApp Cloud API or QR-pairing path; unknown provider state stays blocked. The channel and QR APIs exist; live connection needs Meta credentials.
- 02Set context and approvalsAdd tone, knowledge documents, routing rules, teammates, consent tracking, and the approval boundary. Each workspace manages its own configuration.
- 03Act with receiptsDraft, approve, queue, and distinguish provider acceptance from delivery and read states. Queue acceptance is not delivery; a provider message ID is required before marking sent.
Capability status
What is built, configured, and planned.
Source paths and API routes exist for items marked Available interface or Configuration required. Partial means a foundational slice is implemented. Planned means the direction is known but no backing implementation exists yet.
Available interface
Inbox, campaigns, templates, contacts, segments, rules, consent checks, and the approval gate — API routes and source paths are implemented.
Configuration required
Copilot LLM, payment providers, CRM sync, and live WhatsApp sends — code exists but needs credentials and provider setup.
Partial
Analytics overview, provider receipt states, and consent suppression cover foundational slices; full attribution, ROI, and the accepted intermediate state are on the roadmap.
Planned
Campaign attribution, WhatsApp Commerce, Click-to-WhatsApp Ads, in-chat Forms, and a Chat Widget — solution pages exist as placeholders.
Proof in progress
Measure the conversation, not just the send.
Real customer stories will be added after consented pilots. Until then, Wavy shows the operating signals teams should track.
Response qualityAI draft review
Can an operator understand the context and edit the draft before action?
Customer momentumReceipt clarity
Can the team distinguish queued, delivered, read, failed, and unknown states?
Business impactConversation-to-action
Which chats create a qualified lead, payment, booking, or retention moment?
Questions
Frequently asked about Wavy.
Can customers connect their own WhatsApp number?
Wavy is designed as a multi-tenant product. Each workspace must connect and manage its own number, contacts, inbox, automations, and bot configuration after the relevant provider gate.
Can Wavy connect to another chatbot?
The connector contract supports Automix agents, external webhook bots, and a built-in FAQ engine; each connector still requires its own scope and security review.
Can Wavy collect payments inside WhatsApp?
The payment layer has provider paths for UPI, Razorpay, PhonePe, and Stripe Link. Live charging requires configured credentials, webhook verification, reconciliation, and explicit release approval.
How does consent work?
Importing contacts does not grant messaging consent. Opt-in is tracked per contact. Campaign launches require approved templates and opted-in segments.
Is WhatsApp Commerce available?
Catalog sharing and full commerce flows are planned. A catalog route and solution page exist as placeholders; inventory sync and order management are on the roadmap.
Start with the conversation
Explore the Wavy workspace.
See the workflow, states, and approval boundaries before connecting a real channel.