Use case

Appointment reminders

A reminder is only useful if it arrives, and only defensible if the person agreed to receive it. This journey re-checks consent at send time rather than trusting a decision made at signup.

Trigger · date reached Approval-first
How it runs

Step by step, with the channel named.

01
An appointment is bookedFrom a form in the chat or from your own system by API.WhatsApp
02
A step is dated against the appointmentA day before, an hour before, whatever you set.WhatsApp
03
Consent is re-checked at send timeNot at signup. An opt-out since then stops it.WhatsApp
04
An approved template goes outVariables filled from the contact record.WhatsApp
05
A reply can rescheduleThe answer lands in the shared inbox with an owner.WhatsApp
What runs it

The parts of uxjo doing the work.

JourneysDated steps

Relative to the appointment, not to when the journey was published.

Runs on WhatsAppApproved templates

Utility templates that clear Meta review for reminders.

ConsentRe-checked at send

Consent is state on the contact, evaluated each time.

GovernanceHash-chained audit

A missing entry breaks the chain and is visible.

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
Appointment bookedTrigger · form or API
Dated against the appointmentDelay · 24h before
Consent re-checkedCondition · at send time
Skip if opted outBranch · no message
Approved template sendsWhatsApp · utility

Consent sits between the delay and the send, not at the start. A person who opted out after booking is skipped, and the skip is recorded.

The check happens at the last possible moment.That is the difference between a reminder you can defend and one you cannot.
What changes

The same job, before and after.

Without uxjo

  • A spreadsheet of numbers and a person with a phone
  • Consent recorded once at signup and never checked again
  • No proof of what was sent to whom
  • Reschedules arrive by voicemail

With uxjo

  • Dated steps relative to the appointment itself
  • Consent re-checked at send time, opt-outs honoured across channels
  • A hash-chained log where a missing entry is visible
  • Replies land in the shared inbox with an owner
Every channel

What each channel contributes.

WhatsAppThe reminder itself

Approved utility templates, paced per number.

EmailLonger instructions

Directions and prep notes on your own domain.

GoogleAfter the visit

A review request, and the review stored with a draft reply.

InstagramFirst contact for many

DMs in the same queue, so history starts earlier.

Questions

What people ask before they start.

What if someone opts out after booking?

The send is stopped. Consent is evaluated at send time, so a later opt-out is honoured even though the journey was already running.

Can a reminder be scheduled months or years out?

Yes. Steps can be dated far into the future, which is how service reminders and long treatment plans work.

Can people reply to reschedule?

Yes. The reply arrives in the shared inbox and can be assigned to an owner like any other conversation.

Is this safe for health-adjacent messaging?

Records are encrypted per contact with envelope encryption, searchable by blind index, and every action is recorded in the audit chain.

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