Act on the application, the checkout or the sign-up that stopped.
Most recoverable revenue sits in what did not happen. The platform notices it and acts, once.
Act on what the customer did not do.
A rule on the visit that ended without a payment or an upload starts the journey the moment the visit closes. No report, no export, no ticket.
- The visit that ended without a paymentA session rule on "reached checkout, never paid" fires when the session ends, once per customer.
- The application stopped at a step"Started the application, never uploaded a document" is a rule too, with the step named.
- What did not happen, as a triggerAbsent events count. The platform watches for the step that should have followed and did not.
Reach them once, where they answer.
Consent is checked inside the journey. The channel is the one the person actually responds to. A cap per customer per period keeps one reminder from becoming three.
- Consent checked in the journeyA node reads per-channel consent before every send, so the reminder never goes where it should not.
- The channel they answerThe contact record holds the channel each person responds on and the time they open. The journey uses both.
- One message, cappedA frequency cap per customer per period, set by you, stops the second and third reminder.
Stop the moment they finish.
The journey checks for completion before every reminder and ends when it finds one. A customer who paid after the first message never sees the second.
- An event check before every sendBought? Uploaded? The journey asks the event store, not a timer.
- An answer from your systemWhere the truth lives in your order or application system, a journey step asks it and branches on the reply.
- A record of the runEvery step, every decision and the value it was made on, kept per customer, so "why did they get this?" has an answer.
One record per customer, so the journey knows what happened.
The visit, the checkout, the reply and the consent sit on one contact record with an engagement score and the channel they answer on. Anonymous browsing is stitched to the customer when they identify themselves, so the recovery journey starts with the history, not a blank.
Customer IntelligenceA journey you could ship in the pilot.
Checkout started, not paid → consent → wait one hour → bought? → yes: stop → no: WhatsApp reminder with a button → no tap: one SMS.
The same goal on three industry pages.
Each is a playbook drawn as it runs, with the decision left to your systems.
- E-COMMERCE02Recover the checkout that stalled, once.checkout, not paid (session rule)consentwait 1 hourbought? stop
- Aim
- recovered checkouts, once per shopper.
- BANKS05Turn a loan calculator into an application.session rule: calculator used, no applicationconsentpre-approved figure (your core)WhatsApp with a tap to apply
- Aim
- more completed applications.
- FINTECH08Finish the KYC that stalled at the document.session rule: KYC started, no documentconsentWhatsApp with a tap to continuetapped?
- Aim
- more verifications completed.
Ask where they stalled, in plain language.
Ask the data where applicants dropped off this week and get a validated answer this session, not a ticket. Open the session and watch where the person hesitated, step by step, with the time spent on each.
Analytics & AsklyticsSix channels, one delivery record.
Push and Inbox over our own network, WhatsApp, SMS, email and voice on your own carrier contracts. One channel order per message type, one record per message.
Nine goals. Pick the next one.
- JOURNEYSRecover what stalledMost recoverable revenue sits in what did not happen. The platform notices it and acts, once.
- INTELLIGENCEBring back the driftingChurn shows in the data weeks before it shows in revenue. The question is whether anyone acts on it.
- JOURNEYSGet a response, not just a deliveryVerification, confirmation, collections. The message going out is not the job. The answer is.
- INTELLIGENCEKnow each customer in one recordNot a warehouse table and not an address book. What they did, what they agreed to, and when and where to reach them.
- CAMPAIGNSMeasure what a campaign changedOpens measure the platform. Conversions measure the decision. Most reporting stops at the first.
- DELIVERYSend more for lessMost messaging cost is sending everything the expensive way, and paying for a vendor's price change after it happens.
- STORIESShip content without a releaseAnything richer than text used to wait on an app release. A Story reaches the same place in minutes.
- DELIVERYProve what happenedNot "was it delivered". Prove what happened to this message, and why this customer received it.
- TRUSTKeep data where it must stayRegulated buyers can't use a shared service and can't hand messages to a third party. Both are solved by design, on the same platform.
Three things underneath every goal.
- Our own delivery layer, since 2008.Routing, gateway integration and push are first-party, so channel fallback is journey logic and every message keeps one record.Read more
- One dataset, no export.Events, contacts, consent and delivery live in one store the journeys read directly. No warehouse hop, no nightly sync.Read more
- Cloud, dedicated or on-premise.The same product runs in our cloud, on a dedicated instance or inside your own walls, in country.Read more
Frequently asked.
What counts as a stalled checkout or application?
Whatever you define. A session rule names the step that happened and the step that did not, with a window: reached checkout and no payment within an hour, started the application and no document upload within a day.
How soon after the drop-off does the journey start?
When the session ends, which the web tracker and the mobile SDKs detect by inactivity. The rule fires once per customer per session, so a browser left open does not trigger it twice.
Will a customer who completes still get the reminder?
No. The journey checks for completion before every send and ends the moment it finds one. Where the completion lives in your own system, a journey step asks that system first.
Which channel does the reminder use?
The one the customer answers on, read from the contact record, with consent checked per channel inside the journey. WhatsApp with a button is common, SMS as the fallback, push and the in-app Inbox for app users.
How do we stop over-messaging?
A frequency cap per customer per period that you set, and an engagement score that falls when a customer is over-messaged. The journey reads both before it sends.
What do we need to start?
The web tracker or the mobile SDK on the checkout or application flow, or the events from your own system by API, and one business owner for the use case. A pilot of six to eight weeks measures the result against a baseline you agree first.
Configurations you build in the pilot, not documented deployments.