Use case

Order and delivery updates

Delivery updates are the messages customers actually want, which makes them the cheapest trust you can buy. The work is firing them on real events and knowing what they cost.

Trigger · order shipped Approval-first
How it runs

Step by step, with the channel named.

01
The order is paidorder.paid lands on the contact and on your webhook at once.WhatsApp
02
Dispatch fires the shipping templateAn approved utility template with the tracking detail filled in.WhatsApp
03
Delivery fires the confirmationSame journey, next event.WhatsApp
04
Any reply lands in the shared inboxWith an owner, so a delivery problem is not lost.WhatsApp
05
A review request follows laterConsent-checked, on a dated step.Google
What runs it

The parts of uxjo doing the work.

JourneysEvent-driven steps

Fired by real order events rather than a schedule.

Runs on WhatsAppUtility templates

The category that clears review for transactional updates.

MeasurementDelivery and read receipts

Per message, so a broadcast has a real completion state.

GovernanceCost ledger

The real cost of every send, auditable 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
Order paidTrigger · order.paid
Wait for dispatchCondition · webhook
Shipping templateWhatsApp · utility
Receipt by emailEmail · your provider
Delivered, then review requestGoogle · dated step

Both branches run. A shipping notice belongs in the thread the customer already reads, and the receipt belongs in an inbox they can search later.

Real events, not a schedule.Each step is fired by your own system posting the event, so the message matches what actually happened.
What changes

The same job, before and after.

Without uxjo

  • Customers ask where the order is, one at a time
  • Tracking links pasted by hand
  • No delivery confirmation, so disputes are guesswork
  • Message cost invisible until the invoice

With uxjo

  • Fired on order.paid and dispatch, from your own systems
  • Variables filled from the record, no copy and paste
  • Delivery and read receipts per message
  • Real cost recorded per send in an auditable ledger
Every channel

What each channel contributes.

WhatsAppThe update itself

Utility templates on the real events, with receipts captured.

EmailThe paper trail

Receipts and invoices through your own provider.

GoogleThe review after

Requested on a dated step, stored and scored.

FacebookWhere the order began

Ad referral joined to the paid order.

Questions

What people ask before they start.

Do these need template approval?

Yes, and uxjo checks it. Utility templates are the right category for transactional updates, and a template still in review cannot be selected.

Can my own system trigger these?

Yes. Post the event to the API and the journey runs, or subscribe to order.paid and act in your own stack.

How do I know a message actually arrived?

Delivery and read receipts are captured per message, so a send has a real completion state rather than an assumed one.

What does each message cost?

Every send carries its real cost into a ledger, so the cost of a delivery-update programme is a number you can look up.

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