Your funnels already know who stalls, who funds and who drifts. Act on it the same day, without a ticket.
A wallet verified and never funded. A credit limit approved and untouched for thirty days. The same bill paid on the same date, three months running. Most wallets, payment apps and lenders record these on a dashboard. Here each one starts a journey on the user's channel the day it lands, asks your ledger or credit engine first, and stops the moment they act.
The moments that matter.
Each one is a moment the platform can act on. Here is what it does.
- 01One message
A wallet verified and never funded.
Forty-eight hours after your ledger says verified with no top-up, one push with the Add money deep link, then silence until money lands.
- 02Your ledger decides
A salary that lands in the wallet for the first time.
Your ledger confirms the credit and what they already hold, then one WhatsApp offers a savings pocket with a tap.
- 03Session rule
The Add money screen opened twice, no top-up.
A session rule fires when the session ends and sends one push that opens the step they left.
- 04Credit engine first
A credit limit approved and untouched for thirty days.
Your credit engine confirms the limit is still live, then one WhatsApp shows a use case with a tap to pay.
- 05Your credit engine
The third instalment paid on time.
Your credit engine is asked for a higher limit. If it agrees, one message says so. If not, nothing is sent.
- 06RFM · At Risk
Top-ups falling for three weeks.
RFM on your own events and windows moves them to At Risk; one Story on the feature they never used, one nudge, then silence.
- 07Receipt event
The same biller paid on the same date, three months running.
The receipt you already send becomes a payment event; a segment catches the pattern and one WhatsApp offers autopay with a tap.
- 08Wait until date
An instalment due on a date your ledger holds.
The journey waits until that date, sends Pay now, stops when paid, and escalates by channel if not.
- 09OTP lane
A login code that has to arrive now.
Authentication traffic carries its own route, escalation and dispatch rate, so a growth campaign never delays a login.
Signals from four places, one user record.
Your ledger sends the KYC status, the top-up, the payment, the limit and the instalment date by API. The app sends what users do, and the session itself. The receipts you already send become events. Every read, tap and keypad answer comes back to the same record.
The receipts you already send are behaviour data.
A template declares which of its fields count as an event. The payment receipt you send today becomes a payment event with amount, biller and balance, with no SDK and no release. Behaviour history starts on day one, from the traffic you already send.
Catch the wallet that is emptying quietly.
Nobody closes a wallet. The top-ups get smaller, the balance moves back to the bank, the app opens less often. RFM on your own events scores top-ups and payments separately, on windows you set, and entering At Risk starts a journey. One Story on the feature they never used, one nudge, then silence.
Raise the limit the day the instalment clears.
A third instalment paid on time starts the journey. It asks your credit engine whether a higher limit is available, and only then sends one WhatsApp with Raise my limit or Keep it. A tap goes to your system to apply. No call, no campaign, no offer your credit engine would refuse.
Sell the next product on the signal, not the calendar.
A salary that lands in the wallet is a savings pocket. The same biller paid three months running is autopay. A limit approved and untouched is an instalment plan at a merchant. Each signal asks your ledger what the user already holds, then sends one offer on the channel they answer. If they do not act, the journey ends. Nobody gets the same offer twice.
Turn intent into a first top-up.
The Add money screen opened twice with no top-up, the bank transfer step abandoned. A session rule sends one push that opens the step they left. Consent checked first, and the journey stops the moment money lands.
See where the app loses people.
The SDK captures what users do in the app. Funnels show where KYC, the first top-up and the loan application stop. A session rule turns what did not happen into a trigger: KYC started and no document uploaded, the calculator used and no application. Ask the question in plain language and get the answer this session, not a ticket.
Explain the product with Stories you can measure.
A push says one thing and reports one delivery. A Story in your app, on your domain or inside an email walks the user through the new card, the credit limit they have not used or the pocket they have not opened, page by page, and reports views, completion, the drop between pages, poll answers and form submissions. Built in the builder, withdrawn in one action, no release.
Grow by referral, credited honestly.
Per-person referral links with a leaderboard turn member-get-member into a configuration. Installs are credited back: deterministically on Android, as an estimate on iOS, and the page says which. The tap on the link is an event, so the reward can wait for the new user's first payment before it pays out.
OTP on its own lane, on the traffic you already send.
Codes and receipts go through the API today, with pricing, categorisation and reporting, and nothing else switched on. Authentication traffic carries its own route, escalation and dispatch rate, so a growth campaign never delays a login.
Push your compliance team can approve.
A balance, a limit or a repayment notice never transits a third-party network. Each message is encrypted to a key held only on the user's device. Device-targeted, not end-to-end, and the platform says so.
Data that stays in country.
Operational data in its own databases. A dedicated or in-country installation with high-availability pairs and a separate disaster-recovery site, for the licence that says where wallet data must live.
A journey you could ship in the pilot.
KYC verified, wallet empty (your ledger) → wait 48 hours → top-up seen? → yes: stop → no: check consent → push with the Add money deep link → topped up within three days? → yes: stop → no: one WhatsApp, then silence.
Playbooks you can configure.
Ten journeys a wallet, payment app or lender can configure, from the first top-up after KYC to the limit increase on the third instalment, each drawn as it runs in the builder.
- 01Fund the wallet within forty-eight hours of KYC.
- 02Offer the savings pocket the day the salary lands.
- 03Raise the limit the day the third instalment clears.
- 04Turn an unused credit limit into a first draw.
- 05Bring the Add money visit to a top-up.
- 06Catch the wallet that is emptying quietly.
- 07Set up autopay on the third bill to the same biller.
- 08Finish the KYC that stalled at the document.
- 09Remind on the instalment date, then escalate.
- 10Grow by referral, credited honestly.
These are configurations you build in the pilot, not documented deployments.