Diner opts in
A dine-in customer scans a QR code or signs a consent form to receive WhatsApp updates. Your team records the opt-in and adds the customer as a contact in Wavy.
Industry · Restaurants & Food
Restaurants and food businesses use Wavy to share menus and menu links, handle pre-orders and reservation queries in a shared inbox, and send consent-aware promotional campaigns for specials and events. Campaign workers recheck opted_in contacts and campaign launch has a review gate; manual and rule-based sends follow separate controls.
What Wavy does for restaurants
These are the workflows Wavy is built to support for restaurants, cloud kitchens, and food businesses. Each job has a clear input, a review boundary, and an honest output state.
1. Menu sharing and pre-order handling. A diner messages your WhatsApp number asking for the menu or to place a pre-order. Wavy captures the conversation in the shared inbox. Your team shares menu details or a menu link via text or template message, confirms the order details, and — if you have connected a payment provider — sends a payment link after human review. Order status updates (confirmed, preparing, ready for pickup) are sent using approved templates with honest delivery tracking.
2. Promotional campaigns for specials and events. For opted-in diners, your team builds a campaign to announce a weekend special, a festival menu, or a live-music night. The campaign uses a Meta-approved template, targets only the opted-in segment, and enters a review queue before dispatch. If a diner opts out, they are suppressed from all future campaigns immediately.
3. Reservation and feedback management. Diners message to request or modify reservations. Your team handles these in the shared inbox, confirms changes with approved templates, and can send a feedback request after the dining experience — but only to opted-in contacts, and only after human review. The AI assistant, if enabled, can draft suggested replies, 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 dine-in customer scans a QR code or signs a consent form to receive WhatsApp updates. Your team records the opt-in and adds the customer as a contact in Wavy.
Your team creates a weekend-special announcement using a Meta-approved template. The template is reviewed for menu accuracy and pricing before submission.
Opted-in diners are added to a 'weekend special' segment. Diners 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 diner 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. Order confirmations, specials announcements, and feedback requests 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 diner 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 diner queries 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:
• Promotional campaigns 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 diner without a human clicking approve.
• Opt-out requests are processed immediately — once a diner opts out, no campaign message will be dispatched to them.
Questions
Yes. Your team can share a menu catalog, confirm order details in the shared inbox, and send a payment link if a payment provider is connected. Order confirmation messages use approved templates and are sent after human review.
No. Wavy can schedule campaigns for opted-in diners, 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.
Wavy includes a built-in contact manager and conversation tracking in the shared inbox. Direct POS or delivery-platform integrations are listed as planned — check the integrations page for current status.
No. The AI assistant can draft suggested replies for diner queries, but every draft requires human review and approval before it is sent. The assistant does not send messages or process orders on its own.
Connect your own Meta Business number, import diners with consent, create approved templates, and start sharing menus and campaigns — with human approval gates at every consequential step.