Customer opts in
A customer consents to WhatsApp communication during vehicle purchase or service registration. Your team records the opt-in and adds the customer as a contact in Wavy.
Industry · Automotive
Dealerships, service centers, and automotive businesses use Wavy to capture sales leads in a shared inbox, send test-drive confirmations and service reminders via approved templates, and run consent-aware campaigns for offers and seasonal service drives. 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 automotive
These are the workflows Wavy is built to support for car dealerships, service centers, and automotive businesses. Each job has a clear input, a review boundary, and an honest output state.
1. Sales lead capture and follow-up. A prospect messages your WhatsApp number after seeing an ad or walking into the showroom. Wavy captures the conversation in the shared inbox, tags it with the vehicle model mentioned, and assigns it to a sales executive. The executive reviews the conversation, shares vehicle details and pricing, and schedules a test-drive confirmation using an approved template — all after human review. Wavy tracks delivery state honestly.
2. Service reminders and appointment scheduling. For opted-in customers with vehicles due for service, your team builds a reminder campaign — a service-due notification with a booking link. Each reminder uses a Meta-approved template, is scheduled based on service intervals, and enters a review queue before dispatch. If a customer books or opts out, subsequent reminders are suppressed. Rescheduling requests are handled in the shared inbox by your team.
3. Promotional campaigns for offers and seasonal drives. For opted-in customers, your team creates campaigns for festive offers, exchange programs, or seasonal service drives (monsoon check-up, winter readiness). The campaign uses a Meta-approved template, targets only the opted-in segment, and enters a review queue before dispatch. The AI assistant, if enabled, can draft suggested replies for 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 consents to WhatsApp communication during vehicle purchase or service registration. Your team records the opt-in and adds the customer as a contact in Wavy.
Your team identifies customers with service-due dates approaching and creates a reminder message using a Meta-approved template.
Opted-in customers with upcoming service dates are added to the reminder segment. Customers without opt-in are excluded — suppression is enforced before the campaign is created.
The service reminder campaign is scheduled and 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 remaining scheduled messages and future campaigns 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. Test-drive confirmations, service reminders, and promotional 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 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: AI assistant. If enabled, the AI assistant can draft suggested replies for customer 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:
• Test-drive confirmations and service reminders require reviewer approval before they are sent to the provider.
• Promotional campaigns enter a review queue — each scheduled message must be approved before dispatch.
• 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 service reminder campaigns, but your team must identify the service-due customers and build the segment. Each campaign enters a human review queue before any message is dispatched. Wavy does not auto-import vehicle telemetry or service schedules.
Yes. Your team handles the scheduling in the shared inbox and sends a test-drive confirmation using an approved template after human review. Wavy tracks delivery state honestly.
Wavy includes a built-in contact manager with segments and tags for lead tracking. Direct DMS integrations are listed as planned — check the integrations page for current status.
The AI assistant can draft administrative replies about pricing, availability, and scheduling. Technical specifications should be provided by your sales team. Every draft requires human review before it is sent.
Connect your own Meta Business number, import customers with consent, create approved templates, and start sending confirmations and campaigns — with human approval gates at every consequential step.