Use case

Customer re-engagement

Winning back a quiet customer takes months, not days. That only works if the sequence is patient, alternates channels, and stops the instant someone answers.

Trigger · no activity for 90 days Approval-first
How it runs

Step by step, with the channel named.

01
A contact goes quietNo activity for a window you set. The trigger is the absence itself.WhatsApp
02
Consent is checked before the first stepAnd again before every step after it.WhatsApp
03
An email step opens gentlyThrough your own provider, so your domain reputation stays yours.Email
04
A WhatsApp template follows laterOnly if consent still allows, and only outside the quiet hours you set.WhatsApp
05
One reply ends the sequenceThe moment they answer, the journey stops and a person takes over.WhatsApp
What runs it

The parts of uxjo doing the work.

JourneysLong-dated sequences

Steps measured in weeks or months, not minutes.

Multi-channelWhatsApp and email

Alternating channels in one sequence, on one record.

ConsentChecked at every step

Not once at the start.

ConversationHandover on reply

The sequence ends and the thread gets an owner.

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
No activity for 90 daysTrigger · absence
Consent checked before each stepCondition · every send
Open by emailEmail · your provider
Wait 6 daysDelay · no message
WhatsApp template, stop on replyWhatsApp · quiet hours

The trigger is an absence rather than an action, which is why it needs a window you set. Everything after it is consent-checked individually.

Patient, and easy to stop.A single reply ends the whole sequence and hands the thread to a person.
What changes

The same job, before and after.

Without uxjo

  • A quarterly blast to the whole list
  • Same message on the same channel until it stops working
  • No way to tell who has already come back
  • Opt-outs tracked per channel, or not at all

With uxjo

  • Triggered per contact by their own quiet window
  • Email and WhatsApp alternating in one sequence
  • Any reply ends it and assigns an owner
  • One opt-out honoured everywhere, enforced in the data layer
Every channel

What each channel contributes.

EmailThe patient channel

Longer copy on your own domain, costing nothing per send.

WhatsAppThe one that gets read

An approved template, inside quiet hours you set.

InstagramWhere they may resurface

A comment or DM lands on the same record and ends the sequence.

GoogleProof they were happy once

Their earlier review sits on the same contact.

Questions

What people ask before they start.

Why alternate WhatsApp and email?

They fail differently. Email carries a longer message and costs nothing per send, WhatsApp gets read. A sequence that uses both has more chances to land without becoming repetitive on one channel.

Does email send from uxjo servers?

No. Email goes through your own provider with your own credentials, so deliverability and domain reputation stay under your control.

What ends the sequence?

Any reply, or an opt-out. Both stop it immediately, and an opt-out is honoured across every channel rather than just the one it arrived on.

Can I limit when these send?

Yes. Quiet hours and per-number pacing both apply, so a re-engagement step cannot go out at an unreasonable time.

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