Traveler opts in
A traveler books a tour and provides explicit consent to receive WhatsApp updates. Your team records the opt-in and adds the traveler as a contact in Wavy.
Industry · Travel & Tourism
Travel businesses use Wavy to share itineraries, send booking confirmations and pre-departure reminders, and handle traveler queries 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 travel and tourism
These are the workflows Wavy is built to support for travel operators, tour companies, and hospitality businesses. Each job has a clear input, a review boundary, and an honest output state.
1. Booking confirmation and itinerary sharing. When a traveler books a trip — through your website, a phone call, or a WhatsApp inquiry — your team creates a conversation in Wavy, confirms the booking details, and sends an itinerary using a Meta-approved template. The send is reviewed by a human before it reaches the traveler. Wavy tracks whether the message was delivered, read, or failed, and surfaces that state honestly.
2. Pre-departure reminder sequences. For opted-in travelers, your team builds a reminder campaign: a packing list 48 hours before departure, a check-in reminder 24 hours before, and a welcome message on arrival day. Each reminder uses an approved template, is scheduled to a specific time, and enters a review queue before dispatch. If a traveler opts out at any point, remaining reminders are suppressed.
3. Traveler support and query handling. Travelers message your WhatsApp number with questions — route changes, dietary requests, weather concerns. Wavy captures these in a shared inbox where your support team can respond. The AI assistant, if enabled, can draft suggested replies, but no draft is sent without human review and approval. Complex queries are tagged and routed to the right team member.
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 traveler books a tour and provides explicit consent to receive WhatsApp updates. Your team records the opt-in and adds the traveler as a contact in Wavy.
A team member creates a booking confirmation message using an approved template and sends it after reviewing the content. Wavy tracks delivery state honestly.
Pre-departure reminders are added to a campaign with the opted-in traveler in the segment. Each reminder is scheduled and enters the review queue.
A reviewer approves each reminder before it is queued for dispatch. No reminder is sent to the provider without this approval step.
Approved messages are sent through the WhatsApp Cloud API. Wavy tracks queued, accepted, delivered, read, and failed states for each message.
If the traveler replies 'STOP' or asks to opt out, Wavy suppresses all remaining scheduled messages immediately — even if they are already in the review queue.
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. Booking confirmations, itinerary messages, and reminder templates 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 traveler you message. Wavy enforces suppression for contacts who opt out, but the initial opt-in record is yours to keep.
Optional: AI assistant. If enabled, the AI assistant can draft reply suggestions for traveler 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:
• Booking confirmations and itineraries require reviewer approval before they are sent to the provider.
• Reminder campaigns enter a review queue — each scheduled message must be approved before dispatch.
• AI-drafted support replies are suggestions in the inbox — they are never sent to a traveler without a human clicking approve.
• Opt-out requests are processed immediately — once a traveler opts out, no campaign message will be dispatched to them.
Questions
Wavy can schedule reminder sequences for opted-in travelers, but each campaign enters a human review queue before any message is dispatched. The sequence is a tool for your team, not an autonomous sender.
Wavy supports catalog sharing and structured forms inside WhatsApp conversations. Payment collection requires connecting your own payment provider (UPI, Razorpay, PhonePe, or Stripe). Your team reviews each booking before a confirmation is sent.
The AI assistant can draft replies in multiple languages if enabled, but every draft requires human review. Wavy does not auto-translate and send without approval.
Your team updates the contact record in Wavy. Messages are sent to the number on file — Wavy does not guess or auto-update contact details.
Connect your own Meta Business number, import travelers with consent, create approved templates, and start sending confirmations and reminders — with human approval gates at every consequential step.