Transaction notification
₹{{amount}} {{direction}} on your account
{{direction}} to {{counterparty}} on {{date}}. Available balance: ₹{{balance}}. Didn't recognise this? Contact support from the app.
Industry
ReachBell for fintech.
Transaction alerts, EMI and bill reminders, KYC onboarding nudges, and statement notices — push, SMS, email, and WhatsApp from one place. Built for notifications and engagement, not OTPs.
The problem
The fintech messaging tax.
Three vendors, three dashboards, three audit trails — and the due-date reminder that needed to go out this morning is stuck behind someone else's API.
Most neobanks, lenders, wallets, and broking apps end up with a transactional sender from one vendor, a marketing suite from a second, and a reminders tool bolted on as a third. Each has its own segmentation language, its own webhook contract, and its own idea of what an “opted-in” customer is. When a compliance question lands — “what exactly did we send this customer, and when?” — the answer is scattered across systems that don’t agree with each other.
Due-date reminders are the canonical example. The push provider knows an EMI is coming up. The SMS tool knows the customer prefers texts. The marketing platform is still queued to send a cross-sell. None of them know about each other, so the customer gets three near-duplicate nudges — or worse, a “limit upgrade” offer the same morning their payment bounced.
And the highest-stakes messages are the ones you must get right: transaction notifications, KYC nudges, and important account notices. When those live in a different system from your consent records and preference center, “respect the customer’s choices” quietly turns into an ETL job instead of an automation step.
Templates
Notifications you can ship today.
Drop these into the composer and adjust the merge tags — every template works across web push, mobile push, and email. Keep sensitive detail in-app, not in the notification body.
EMI due-date reminder, 3 days before
Your EMI of ₹{{emi_amount}} is due {{due_date}}
Loan {{loan_id}} — auto-debit runs on {{due_date}}. Keep your account funded, or pay early from the app to avoid late fees.
KYC completion nudge
One step left to activate your account
Your KYC is almost done, {{first_name}}. Finish verification to unlock transfers and your full limit — takes about two minutes.
Statement ready
Your {{month}} statement is ready
View and download your account statement for {{month}} from the app. Closing balance: ₹{{closing_balance}}.
Cross-sell, consent-based
You may be eligible for a higher limit
Based on your repayment history, {{first_name}}, you can request a limit review. Tap to see your offer — no impact to apply.
Important account notice
Action needed on your account
We've updated terms for {{product}} effective {{date}}. Review the changes in the app and reach out if anything's unclear.
Automation flows
Three flows that earn their keep.
Built from the visual flow builder — each node is a send, a wait, or a condition. No code.
KYC & onboarding completion
Bring new sign-ups across the verification finish line across push, email, and WhatsApp without nagging the ones who already finished.
- 01Trigger: `signup.created` webhook from your onboarding service.
- 02If KYC isn't complete after 1 hour, send web/mobile push: "One step left to activate your account" with a deep link to the verification screen.
- 03If still incomplete after 24 hours, send email walking through the documents needed and what each unlocks.
- 04If still nothing after 3 days, send a WhatsApp reminder (opt-in only) offering a quick assisted-onboarding link.
- 05Exit the flow the moment `kyc.completed` fires — no further reminders go out.
EMI & bill due-date reminders
Reduce missed payments with timely, time-sensitive reminders — SMS and push for the deadline, email for the receipt.
- 01Segment: active loans/bills with a due date in the next 3 days, customer opted in to reminders.
- 023 days before: send push and SMS — "Your EMI of ₹{{emi_amount}} is due {{due_date}}" with a pay-now deep link.
- 03On due date, if unpaid by morning, send a single follow-up push (frequency-capped so it never doubles up with the 3-day one).
- 04On successful payment webhook, send an email receipt and tag the customer `paid_on_time`.
- 05If unpaid after the grace window, branch to a support-led collections flow instead of more marketing sends.
Statement-ready & engagement
Turn monthly statements into a habit loop — and surface relevant, consent-based offers without crossing into pushy.
- 01Trigger: `statement.generated` for an account.
- 02Send "Your statement is ready" push and email with a deep link to view it in-app (no sensitive data in the notification body).
- 03Wait 5 days, then for customers who haven't opened the app, send a low-frequency re-engagement push.
- 04Branch on consent + eligibility flags and send a relevant cross-sell email (e.g. limit review) — only to customers who opted into offers.
- 05Honour preference-center choices throughout — anyone set to "essential only" skips the engagement and cross-sell steps automatically.
In the wild
Who's using it.
We dogfood ReachBell on our own products before recommending it to yours.
ReachBell powers push, email, and automation for our internal portfolio — including VedHoroscope (a daily-horoscope app where personalisation needs to read like it came from your astrologer, not a CRM), StumpScore (a cricket-scores site that has to push score updates within seconds of a wicket without hammering subscribers off the list), and OmegleCo. (a chat product whose re-engagement loops live entirely on push and email).
The fintech playbook above isn’t a hypothetical — it’s the same event-trigger-template-segment loop those products use, with account and payment events swapped in for scores or horoscopes. One caveat we hold to: these are best-effort channels, so we don’t position ReachBell for OTP or 2FA code delivery — keep authentication codes on a dedicated provider and use ReachBell for the reminders, nudges, and notices around them.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Can I use ReachBell to send OTPs or two-factor authentication codes?
No — ReachBell isn't built for authentication-code delivery. Push and email are best-effort channels without guaranteed latency, so they're the wrong fit for time-critical security codes, and our Acceptable Use Policy excludes that use case. Use a dedicated OTP/2FA provider for codes, and use ReachBell for the notifications, reminders, onboarding nudges, and engagement messages around them.
How does ReachBell handle consent and customer preferences?
Every subscriber has a preference center and channel-level opt-ins, so a customer can keep essential account notices while muting marketing and cross-sell. Sends respect those choices automatically, and a global STOP/unsubscribe is always honoured. It's designed to be DPDP-aware and India-first.
Is there an audit trail of what was sent to each customer?
Yes. Every send — and every message skipped by a frequency cap, quiet-hours rule, or preference setting — is recorded in the audit log with timestamp, channel, and template. That gives compliance and support teams a clear record of what a customer was (and wasn't) sent.
Can I personalize messages with account, transaction, or loan data?
Yes. Every send accepts a flat JSON payload, and templates use {{merge_tags}} like {{first_name}}, {{emi_amount}}, or {{due_date}}. Keep sensitive details out of the notification body and link customers into the app to view them — the same data works across push, email, and WhatsApp so one automation can branch by channel without rewriting copy.
Which channel should I use for time-sensitive alerts versus reminders?
For time-sensitive account and transaction alerts, SMS and push tend to fit best; for due-date reminders and support, WhatsApp works well (opt-in only); and email suits statements and longer notices. ReachBell runs all of them from one dashboard so you can pick per message and fall back across channels.