The banking playbook. Built in the builder, decided by your core.
Ten journeys, each drawn below as it runs. The decision comes from your systems or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.
Offer the card upgrade the month the salary rises.
A salary credit greater than the previous month asks your core whether the customer qualifies, then sends one WhatsApp with Upgrade or Not now; a tap goes to your system to process.
- Decides
- your eligibility rules.
- Aim
- upgrades without a call.
Offer the deposit when the balance sits idle.
A balance idle for sixty days asks your core whether the amount is free and the product is not held, then sends one WhatsApp with Open a deposit or Not now; a tap goes to your system to open it.
- Decides
- your product rules and the balance your core holds.
- Aim
- deposits without a branch visit.
Catch the salary that stopped arriving.
A customer with a salary credit for three months and none in thirty-five days enters a segment and gets one message from the bank; a reply becomes a task for a relationship manager.
- Decides
- your segment definition.
- Aim
- the leaving customer reached before the account closes.
Win back the money going to another bank.
A third transfer to the same external bank in ninety days checks what the customer holds with you, then sends one Story about the product they buy elsewhere, and an offer if they read it.
- Decides
- your product rules.
- Aim
- share of wallet recovered.
Turn a loan calculator into an application.
A session with the calculator used and no application sends the figure your core pre-approves with a tap to apply, reminds once if the upload stalls, and stops when the application completes.
- Decides
- your credit rules.
- Aim
- more completed applications.
Activate the card that is sitting in a drawer.
A card-issued event starts a Story with the steps, waits, checks your core, and reminds once on the customer's channel if the card is still inactive.
- Decides
- your core system's card status.
- Aim
- more cards activated in the first week.
Turn a declined card abroad into a one-tap fix.
A decline from your core system sends a WhatsApp with one button, and a tap switches international use on and confirms.
- Decides
- your core system, then the customer.
- Aim
- fewer contact-centre calls, recovered international spend.
Verify a transaction without a human dialling.
A large transaction triggers a call with a keypad answer, escalating to WhatsApp then SMS if unanswered, with the result written back.
- Decides
- your fraud rules; the customer.
- Aim
- faster verification, fewer manual checks.
Move transaction alerts off SMS without losing one.
Alerts go by push and Inbox to app users over our own network and fall back to SMS on the carrier's signal; every message keeps its record.
- Decides
- your channel order, per message type.
- Aim
- lower alert cost, the same evidence.
Remind on the due date, then escalate.
The journey waits until the date your system holds, sends Pay now, stops when paid, and escalates by channel if not.
- Decides
- your due dates and risk tiers.
- Aim
- higher recovery, lower cost to collect.
Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.