Your customers send a signal every day. Act on it the day it happens.
A salary that grew. A transfer that now goes to another bank every month. An app opened and closed with nothing done. Most banks record these. Here each one starts a journey on the customer's channel, checks with your core 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.
- 01Your core decides
A salary credit larger than the last one.
Your core confirms eligibility, and one WhatsApp offers the upgrade with a tap.
- 02Segment entry
The salary that did not arrive.
The customer enters a segment you defined and gets one message from the bank, not an offer. A reply reaches a person.
- 03Story if read
A transfer to another bank, third month running.
A check of what they hold with you, then one Story about the product they are buying elsewhere.
- 04Session rule
The loan calculator used twice, no application.
A session rule sends the pre-approved figure from your core, with a tap to apply.
- 05Story in the app
The app opened and closed with nothing done, seven days in a row.
A session rule starts one Story on the three things customers use most, and stops when they transact.
- 06Card activation
A card issued and never activated.
A Story with the steps, a wait, a check with your core, and one reminder if the card is still inactive.
- 07Your core system
A card declined abroad.
One WhatsApp button; a tap switches international use on and writes the outcome back.
- 08Keypad reply
A transaction that needs confirming.
A call captures the keypad answer and escalates to WhatsApp, then SMS, if nobody picks up.
- 09Your core decides
A balance that has sat idle for sixty days.
Your core confirms the amount is free and the product is not held, and one message offers the term deposit with a tap.
Signals from four places, one customer record.
Your core sends the transaction, the salary credit, the decline and the application status by API. The app and the site send what customers do, and the session itself. The alerts you already send become events. Every reply, read and keypad answer comes back to the same record.
Your alerts are already behaviour data.
A template declares which of its fields count as an event. The transaction alert you send today becomes a transaction event with amount and merchant type, with no SDK and no release. Behaviour history starts on day one, from the traffic you already send.
Catch the customer who is leaving quietly.
Nobody closes the account. The salary moves, the transfers to another bank recur, the card spend falls. Segments on your own definitions catch each one, RFM scores deposits and card spend separately, and entering a segment starts a journey. One message, on their channel, then silence.
Offer the upgrade the month the income changes.
A salary credit greater than the previous month starts the journey. It asks your core whether the customer qualifies, and only then sends one WhatsApp with Upgrade or Not now. A tap goes to your system to process. No call, no campaign, no offer to someone who does not qualify.
Sell the next product on the signal, not the calendar.
A balance that sits idle for sixty days is a term deposit. A ticket bought abroad is travel insurance. Rent paid on the same date every month is a home loan conversation. Each signal checks your core for eligibility and what the customer already holds, then sends one offer on the channel they answer. If they do not act, the journey ends. The same offer is not repeated to the same customer.
Turn intent into an application.
The calculator used twice with no application, the form abandoned at document upload. A session rule sends the figure your core pre-approves, with a tap to continue where they stopped. Consent checked first, and the journey stops when the application completes.
See where the app loses people.
The SDK captures what customers do in the app. Funnels show where card activation, onboarding and loan applications stop. A session rule turns what did not happen into a trigger: the app opened with no transaction, a biller added and the bill never paid. Ask the question in plain language and get the answer this session, not a ticket.
Educate and market with Stories you can measure.
A text says one thing and reports one delivery. A Story in your app, on your domain or inside an email walks the customer through the new card, the feature they have not tried or the offer, page by page, and reports views, completion, the drop between pages, poll answers and form submissions. Card activation steps, a feature walkthrough, a product explainer: built in the builder, withdrawn in one action, no release.
Verification that runs itself.
Call the customer and capture the keypad answer when they pick up. If the call goes unanswered, escalate to WhatsApp, then SMS, and branch on the reply there. A branch per response, a deadline per branch, a path for silence. The same shape serves fraud confirmation and collections.
- ANSWERED
- Keypad answer1, 2 or star, on the call
- Permitted actionYour system validates and executes
- UNANSWERED
- WhatsAppButtons, with a deadline
- SMSKeyword reply, or stop
Move alerts off SMS, keep the evidence.
For customers with the app, transaction alerts and notices travel by push and the in-app Inbox over our own network, with read state. SMS stays as the fallback on the carrier's failure signal, not a timer. Every message keeps one record: route, attempts, outcome, exportable.
A standing savings view puts a figure in your currency against what routing did, by traffic type.
Lanes for OTP, alerts and marketing, on the traffic you already send.
Codes, alerts and statements go through the API today, with pricing, categorisation and reporting, and nothing else switched on. Each traffic type gets its own channel order, escalation and dispatch rate, so a marketing burst does not queue in front of a login.
Push your compliance team can approve.
Content does not pass through a third-party push network; the device-maker network receives only a content-free wake-up. Each message is encrypted to a key held only on the customer's device. Device-targeted, not end-to-end, and the platform says so.
Data that stays home.
Operational data in its own databases. A dedicated or in-country installation with high-availability pairs and a separate disaster-recovery site.
A journey you could ship in the pilot.
Salary credit greater than the previous month → eligible? your core → WhatsApp: Upgrade / Not now → tap: your system processes → confirmation → no tap: silence.
Playbooks you can configure.
Ten journeys a bank can configure, from the card upgrade on a salary rise to due-date collections, each drawn as it runs in the builder.
- 01Offer the card upgrade the month the salary rises.
- 02Offer the deposit when the balance sits idle.
- 03Catch the salary that stopped arriving.
- 04Win back the money going to another bank.
- 05Turn a loan calculator into an application.
- 06Activate the card that is sitting in a drawer.
- 07Turn a declined card abroad into a one-tap fix.
- 08Verify a transaction without a human dialling.
- 09Move transaction alerts off SMS with every attempt on the record.
- 10Remind on the due date, then escalate.
Multi-channel verification with keypad capture, built by configuration in the journey builder.
These are configurations you build in the pilot, not documented deployments.