Customer opts in
A customer signs up for WhatsApp updates through your website or in-store QR code. Your team records the opt-in and adds the customer as a contact in Wavy.
Industry · Beauty & Cosmetics
Beauty and cosmetics brands use Wavy to share product details and catalog links, run consent-aware launch campaigns for opted-in customers, and handle product inquiries in a shared inbox. 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 beauty and cosmetics
These are the workflows Wavy is built to support for beauty brands, cosmetics companies, and personal-care businesses. Each job has a clear input, a review boundary, and an honest output state.
1. Product catalog sharing and inquiries. A customer messages your WhatsApp number asking about a product. Your team shares the relevant catalog items or product details in the shared inbox, answers questions about shades, sizes, or ingredients, and — if a payment provider is connected — sends a purchase link after human review. Wavy tracks whether the message was delivered, read, or failed, and surfaces that state honestly.
2. Product launch campaigns. For opted-in customers, your team builds a campaign to announce a new product line, a seasonal collection, or a limited-edition release. The campaign uses a Meta-approved template, targets only the opted-in segment, and enters a review queue before dispatch. If a customer opts out, they are suppressed from all future campaigns immediately.
3. Reorder and restock reminders. For opted-in customers who have previously purchased consumable products (skincare, haircare, supplements), your team creates restock reminder sequences. Each reminder uses an approved template, is scheduled based on expected usage cycles, and enters a review queue before dispatch. The AI assistant, if enabled, can draft suggested replies for product inquiries, but no draft is sent without approval.
Example workflow
This is an illustrative workflow showing how the pieces fit together. It is not a promise of outcomes — your results depend on your own provider configuration, contact quality, and message content.
A customer signs up for WhatsApp updates through your website or in-store QR code. Your team records the opt-in and adds the customer as a contact in Wavy.
Your team creates a product launch announcement using a Meta-approved template. The template is reviewed for product accuracy, pricing, and compliance before submission.
Opted-in customers are added to a 'new launch' segment. Customers 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 must approve it before any message is queued for dispatch.
After approval, messages are sent through the WhatsApp Cloud API. Wavy tracks each message as queued, accepted, delivered, read, or failed.
If a customer replies 'STOP' or asks to opt out, Wavy suppresses all future campaign messages to that contact immediately.
Provider and configuration dependencies
WhatsApp Business API (Meta Cloud API). You must connect your own Meta Business account and WhatsApp Business number. Wavy does not provide a shared number — your message reputation, quality rating, and template approvals belong to your Meta account.
Approved message templates. Launch announcements, restock reminders, and product inquiry responses must each be submitted to and approved by Meta before they can be used in a campaign. Wavy surfaces the approval status; it cannot bypass Meta's review.
Contact opt-in records. You are responsible for maintaining evidence of consent for each customer you message with promotional content. Wavy enforces suppression for contacts who opt out, but the initial opt-in record is yours to keep.
Optional: Payment provider. If you want to collect payments inside WhatsApp, connect your own UPI, Razorpay, PhonePe, or Stripe account. Payment links are provider-dependent; the current API/UI path requires separate review before live use.
Optional: AI assistant. If enabled, the AI assistant can draft suggested replies for product inquiries in the inbox. 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:
• Launch campaigns and restock reminders require reviewer approval in the campaign queue before they are sent to the provider.
• Payment links are provider-dependent; current UI confirmation is separate from backend approval enforcement.
• AI-drafted replies are suggestions in the inbox — they are never sent to a customer without a human clicking approve.
• Opt-out requests are processed immediately — once a customer opts out, no campaign message will be dispatched to them.
Questions
Wavy can schedule restock reminder campaigns for opted-in customers, but each campaign enters a human review queue before any message is dispatched. The campaign is a tool for your team, not an autonomous sender.
Yes. Your team can share catalog items, confirm order details in the shared inbox, and send a payment link if a payment provider is connected. Purchase confirmation messages use approved templates and are sent after human review.
No. Ingredient and allergy inquiries should be handled by your qualified team members. The AI assistant can draft administrative replies, but product-safety questions require human review and should not be answered autonomously.
Wavy includes a built-in contact manager and catalog sharing in the shared inbox. Direct e-commerce platform integrations are listed as planned — check the integrations page for current status.
Connect your own Meta Business number, import customers with consent, create approved templates, and start sharing catalogs and campaigns — with human approval gates at every consequential step.