Use case

Abandoned cart recovery

Most recovery messaging fails in one of two ways: it fires on a guess, or it keeps going after the person has already answered. This journey fires on the real cart event and ends the moment they reply.

Trigger · cart abandoned Approval-first
How it runs

Step by step, with the channel named.

01
A cart is abandonedThe real event from your store, not a timer somebody guessed at.WhatsApp
02
Consent and suppression are checkedEnforced in the data layer, so it holds for API sends too.WhatsApp
03
An approved template goes out, pacedA token bucket per number, so throughput scales with numbers.WhatsApp
04
The journey stops on any replyOne answer ends the sequence. No second nudge after a conversation starts.WhatsApp
05
A later step can use emailFor a longer window, sent through your own provider.Email
What runs it

The parts of uxjo doing the work.

TriggerThe real cart event

Fired by your store, so timing is accurate rather than assumed.

Runs on WhatsAppApproved templates

Only templates Meta has approved, with variables from the record.

PacingPer-number token bucket

Adding a number adds throughput instead of risking the first one.

GovernanceCost per message

Every send in a ledger you can audit line by line.

How it is built

The journey, as it exists in Studio.

A trigger, the conditions that hold it back, and the branches that decide what happens next.

Journey StudioPublished
Cart abandonedTrigger · store event
Consent, suppression, quiet hoursCondition
Send the recovery templateWhatsApp · paced
Wait 20 hoursDelay · no message
Email step, then stop on replyEmail · your provider

The delay branch is a real node, not a background timer. You can see the wait, change it, and know exactly when the next message is due.

Fired by the event, ended by the answer.A reply at any point stops the sequence, so nobody gets nudged mid-conversation.
What changes

The same job, before and after.

Without uxjo

  • A nightly export, so the message lands a day late
  • Sent to everyone, including people who opted out
  • Keeps going after the customer has already replied
  • Cost is a line on the Meta invoice, not per journey

With uxjo

  • Fired on the real cart event, so timing is a decision
  • Suppression enforced in the data layer, API sends included
  • One reply ends the sequence immediately
  • Cost per message in a ledger you can audit line by line
Every channel

What each channel contributes.

WhatsAppThe first nudge

An approved template, paced per number by a token bucket.

EmailThe second, later

Longer copy through your own provider, on the same journey.

FacebookWhere the cart often started

Click-to-WhatsApp referral joins the ad to the order.

InstagramShoppable posts

Products tagged in the post that created the cart.

Questions

What people ask before they start.

How soon does the message go out?

Whenever your journey says. The step is dated relative to the cart event, so the delay is a decision rather than a side effect of a sync schedule.

What if the customer replies?

The sequence stops. A reply ends the journey, so nobody receives a recovery nudge in the middle of a live conversation.

Can I send this to anyone who abandoned a cart?

Only if consent allows. Suppression is checked in the data layer, and a broadcast that fails a launch gate does not start at all.

What does it cost to run?

Each send carries its real per-message cost into a ledger, so recovery has a measurable cost against the orders it produced.

Industries

Who runs this most.

Not on this page?

Your journey is the one we have not listed yet.

Every business has a flow that is only theirs. Describe it in a message and we will map it with you, name the triggers, and tell you honestly what runs today and what does not. No form, no wait.

Talk to usStart free