Use case · Cart and booking recovery
A drop-off is a timestamped event with the item, the step and the price still attached. Edverix starts the recovery journey the moment the next event fails to arrive, carries that context into the message, and measures the conversion against a control group.
Runs on
3 modulesJourney Orchestration
Triggers, waits, branches, goals and channel actions on a visual canvas, with per-node stats, versioning and a 30-day replay.
Explore JourneysMessaging Channels
Mobile push, web push, in-app, inbox, email, SMS, WhatsApp, RCS, on-site and webhooks, with no margin on delivery.
Explore ChannelsExperimentation & Attribution
A/B and multivariate tests, bandits, control groups, a universal holdout, attribution windows and feature flags.
Explore ExperimentationHow it runs
Each example is a trigger on your own events, an action through your own providers, and a number you can hold it to. The industry page shows the rest of that vertical's plays.
FromE-commerce & D2C
Trigger
checkout_started with no order_completed within 45 minutes
Action
WhatsApp with the cart contents and a live price, then push after four hours, then email the next morning
Proof
Conversion attributed inside a 24-hour window against a 10% control group
FromE-commerce & D2C
Trigger
payment_failed with error code
Action
SMS with a retry link within two minutes; branch on the error code to suggest a different method
Proof
Recovered order value by error code
Trigger
slot_selected with no booking_confirmed within 30 minutes
Action
WhatsApp holding the slot for a short window, with a one-tap confirm link
Proof
Booking completion rate against control
FromFintech & BFSI
Trigger
application_submitted missing, form_step_viewed at step three
Action
Transactional email with the saved application and required documents listed
Proof
Submission rate against control
Trigger
search_performed with results, no request_created in the session
Action
Push with the top three listings for that search and current availability
Proof
Request rate against control
Related industries
Each page names the events that matter, the plays that run on them and the reports the team lives on.
FAQ
Anything not answered here is a demo call away.
Request a demoAs soon as the wait you set expires without the next event arriving. A journey waits for order_completed for the window you choose, then branches to the first message; the customer exits the journey the moment the order lands, even mid-sequence.
Yes. The trigger event carries the cart or booking properties, and catalogue fields resolve at send time, so the message never shows a price that changed or an item that sold out.
Every recovery campaign holds back a control group, and conversions are attributed inside the window you set. The report shows lift against control, not just how many people who received a message later bought.
More use cases
Get started
Send your first event in an hour, simulate your first journey against real history, and keep every byte of it in a database you can query.