Customer opts in
A customer provides explicit consent to receive WhatsApp notifications during account opening or service registration. Your team records the opt-in and adds the customer as a contact in Wavy.
Industry · Banking & Finance
Consent-aware notifications and structured customer support on WhatsApp.
Banks, NBFCs, fintech companies, and financial service providers use Wavy to send consent-aware transactional notifications, handle customer support queries in a shared inbox, and manage document requests via approved templates. Campaign workers recheck opted_in contacts and campaign launch has a review gate; financial communication retains the safety boundaries below.
Not financial adviceWavy is a communication tool, not a financial advisor. It does not provide investment, tax, legal, or accounting advice. All financial decisions remain with qualified professionals.
Campaign consentCampaign workers recheck opted_in before dispatch and unsubscribe rules set opted_in to False; manual and inbound replies follow separate paths.
Campaign reviewCampaign launch checks role, draft state, and approved template. Copilot replies are drafts; manual, rule, bot, and payment sends have separate controls.
Important safety notice
Wavy is a communication tool — not a financial advisor.
Wavy is not a financial advisor, investment advisor, tax consultant, or legal advisor. It does not recommend financial products, assess investment risk, calculate tax liability, provide portfolio advice, or make credit decisions. The AI assistant inside Wavy drafts message suggestions for your team to review — it does not generate financial guidance, and no AI-suggested message is sent to a customer without a human clicking approve.
If your institution is subject to financial regulations (such as RBI guidelines, SEBI regulations, IRDAI rules, DPDP Act financial-data provisions, or other local financial-services laws), you are responsible for ensuring that your use of WhatsApp and Wavy complies with those obligations. Wavy does not provide regulatory compliance certification, and this page does not constitute legal, regulatory, or compliance advice. Consult qualified legal and compliance counsel before deploying WhatsApp-based communication in a regulated financial context.
Wavy does not store, transmit, or process financial records, account credentials, or transaction data on your behalf unless you explicitly input them into conversations. You are responsible for what you type into the shared inbox. Do not use Wavy to send account numbers, passwords, OTPs, full card details, or other sensitive authentication data — those communications should follow your institution's established secure channels.
What Wavy does for banking and finance
Three realistic jobs on WhatsApp.
These are the administrative communication workflows Wavy is built to support. None of them involve financial advice, investment recommendations, credit decisions, or transaction processing.
1. Transactional notification campaigns. Your team creates notification campaigns for opted-in customers — statement availability alerts, EMI due reminders, policy renewal notices, or KYC update requests. Each notification uses a Meta-approved template, targets only the opted-in segment, and enters a review queue before dispatch. A human reviewer must approve the campaign before any message is sent to the provider. Wavy tracks delivery state honestly — queued, accepted, delivered, read, or failed.
2. Customer support query handling. Customers message your WhatsApp number with non-transactional questions — branch hours, product eligibility, document requirements, application status. Your team responds in the shared inbox. The AI assistant, if enabled, can draft suggested replies for these administrative queries, but no draft is sent without human review and approval. Questions involving account details, transaction disputes, or financial advice are flagged for your team to handle through established secure channels — Wavy does not generate financial responses or auto-share account information.
3. Document request management. For customers in onboarding or KYC update workflows, your team sends document request messages using approved templates — listing required documents, submission deadlines, and next steps. Each document request is reviewed by a human before it reaches the customer. Wavy tracks whether the message was delivered, read, or failed. Document submission is handled through your institution's secure channels — Wavy does not process or store submitted documents.
Example workflow
A safe, end-to-end notification campaign sequence.
This is an illustrative administrative workflow. It does not involve financial advice, transaction processing, or credit decisions. Your results depend on your own provider configuration, contact quality, and message content.
Notification created
A team member creates a notification message using a Meta-approved template — for example, an EMI due reminder. The template contains only administrative details.
Segment built
Opted-in customers with upcoming due dates are added to the notification segment. Customers without opt-in are excluded — suppression is enforced before the campaign is created.
Human review
The notification campaign enters a review queue. A reviewer confirms the content contains no financial advice and approves it before any message is queued for dispatch.
Dispatch and tracking
After approval, messages are sent through the WhatsApp Cloud API. Wavy tracks each message as queued, accepted, delivered, read, or failed.
Opt-out suppression
If a customer replies 'STOP' or asks to opt out, Wavy suppresses all future campaign messages to that contact immediately — while respecting your regulatory obligations for mandatory transactional alerts.
Provider and configuration dependencies
What you need before these workflows go live.
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. Financial-services templates may face additional Meta review.
Approved message templates. Transactional notifications, document requests, and customer support templates must each be submitted to and approved by Meta. Templates containing financial content may require additional review. 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. In financial contexts, ensure your opt-in process complies with applicable financial regulations and data-protection laws. Wavy enforces suppression for contacts who opt out (subject to your regulatory obligations for mandatory alerts), but the initial opt-in record and regulatory compliance are yours to maintain.
Regulatory compliance. If your institution is subject to banking, securities, insurance, or other financial regulations, consult qualified legal and compliance counsel before deploying WhatsApp-based communication. Wavy does not provide regulatory compliance certification, and this page is not legal, regulatory, or compliance advice.
Optional: AI assistant. If enabled, the AI assistant can draft suggested replies for administrative queries in the inbox. The assistant does not generate financial advice, investment recommendations, or credit decisions. No draft is sent automatically — a human must review and approve every suggested reply before dispatch.
Consent, review, and safety boundaries
Where the human stays in control — and where Wavy stops.
Wavy is designed so that no consequential action happens without a human decision, and so that financial-safety boundaries are respected. Specifically:
• Notification campaigns and document requests require reviewer approval before they are sent to the provider.
• AI-drafted replies are administrative suggestions only — they are never sent to a customer without a human clicking approve, and they must not contain financial advice, investment recommendations, or credit decisions.
• Account-sensitive questions from customers are flagged for your team to handle through established secure channels. Wavy does not auto-generate financial responses or share account information without explicit human action.
• Sensitive data — account numbers, passwords, OTPs, full card details — must not be sent through Wavy. Use your institution's established secure channels for such communications.
• Opt-out requests are processed immediately, subject to your regulatory obligations for mandatory transactional alerts.
• No financial advice. Wavy does not recommend financial products, assess investment risk, calculate tax liability, provide portfolio advice, or make credit decisions. All financial decisions remain with qualified professionals using established institutional channels.
Questions
What banking and finance institutions ask about Wavy.
Can Wavy send transaction confirmations or account statements to customers?
Wavy can send notification campaigns alerting customers that a statement is available or that an EMI is due. However, Wavy should not be used to send full account statements, transaction details, or balances — those should follow your institution's established secure channels. Wavy is an administrative notification tool, not a transaction-delivery platform.
Is Wavy compliant with RBI, SEBI, IRDAI, or DPDP Act requirements?
Wavy does not provide regulatory compliance certification. If your institution is subject to financial regulations, you are responsible for ensuring your use of WhatsApp and Wavy complies. Consult qualified legal and compliance counsel. This page is not legal, regulatory, or compliance advice.
Can the AI assistant provide investment or credit advice to customers?
No. The AI assistant drafts administrative reply suggestions only — branch hours, document requirements, general product information. It does not generate investment advice, credit decisions, risk assessments, or financial recommendations. Every draft requires human review, and financial questions are handled by your qualified staff through appropriate channels.
Can Wavy process payments or fund transfers through WhatsApp?
No. Wavy does not process payments, fund transfers, or financial transactions. If you connect a payment provider, Wavy can generate payment links for approved use cases (such as fee collection), but each link is generated only when a team member explicitly requests one and is sent only after human review. Transaction processing follows your institution's established secure channels.
Bring your administrative communication to WhatsApp.
Connect your own Meta Business number, import customers with consent, create approved templates for administrative notifications, and start sending alerts — with human approval gates and strict safety boundaries at every step.