Prospect inquires
A prospect messages your WhatsApp number asking about a course. Wavy creates a conversation in the shared inbox and tags it with the course name.
Industry · Edutech
Educational institutions, edutech companies, and coaching centers use Wavy to handle course inquiries in a shared inbox, send enrollment confirmations via approved templates, and run consent-aware campaigns for admissions and batch announcements. 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 edutech
These are the workflows Wavy is built to support for educational institutions, edutech platforms, and coaching centers. Each job has a clear input, a review boundary, and an honest output state.
1. Course inquiry qualification. A prospect messages your WhatsApp number asking about a course, batch schedule, or fee structure. Wavy captures the conversation in the shared inbox, applies tags based on the course mentioned, and assigns the lead to an admissions counselor. The counselor reviews the conversation and sends a qualification reply with course details — no AI sends a message on its own. Wavy tracks whether the message was delivered, read, or failed.
2. Enrollment confirmation and fee collection. When a prospect decides to enroll, your team sends an enrollment confirmation using a Meta-approved template. If a payment provider is connected, a fee payment link is generated only when a counselor explicitly requests one and is sent only after human review. Wavy tracks the payment link delivery and the enrollment confirmation state honestly — queued, delivered, read, or failed.
3. Admissions and batch announcement campaigns. For opted-in prospects, your team creates campaigns to announce new batch start dates, admission deadlines, or scholarship opportunities. Each campaign uses a Meta-approved template, targets only the opted-in segment, and enters a review queue before dispatch. If a prospect opts out, they are suppressed from all future campaigns immediately. 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 prospect messages your WhatsApp number asking about a course. Wavy creates a conversation in the shared inbox and tags it with the course name.
An admissions counselor reads the conversation, shares course details and schedule, and assigns a lead stage. No AI-generated message is sent without the counselor's review and approval.
Interested prospects who have given explicit opt-in are added to a 'batch announcement' segment. Prospects without opt-in are excluded.
A batch-start announcement is created with an approved template and the opted-in segment. It enters a review queue — a human must approve it before dispatch.
After approval, messages are sent through the WhatsApp Cloud API. Wavy tracks each message as queued, accepted, delivered, read, or failed.
If a prospect 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. Enrollment confirmations, batch announcements, and fee 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 prospect 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 course fees inside WhatsApp, connect your own UPI, Razorpay, PhonePe, or Stripe account. Payment links are provider-dependent; current UI confirmation is separate from backend approval enforcement.
Optional: AI assistant. If enabled, the AI assistant can draft suggested replies for course 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:
• Enrollment confirmations and fee payment links require reviewer approval before they are sent to the provider.
• Admissions and batch announcement 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 prospect without a human clicking approve.
• Opt-out requests are processed immediately — once a prospect opts out, no campaign message will be dispatched to them.
Questions
No. Wavy captures inquiries in the shared inbox, but enrollment confirmations and fee collection require human review and approval. The AI assistant can draft replies, but no enrollment action happens without a counselor's explicit decision.
Wavy can schedule reminder sequences for opted-in students, but each campaign enters a human review queue before any message is dispatched. Your team controls what is sent and when.
Wavy includes a built-in contact manager with segments and tags for lead tracking. Direct LMS or SIS integrations are listed as planned — check the integrations page for current status.
The AI assistant can draft administrative replies about schedules, fees, and enrollment procedures. It does not generate academic content or evaluate student work. Every draft requires human review before it is sent.
Connect your own Meta Business number, import prospects with consent, create approved templates, and start handling inquiries and campaigns — with human approval gates at every consequential step.