Skip to content
Healthcare · Playbook

The healthcare playbook. Built in the builder, decided by your hospital system.

Ten journeys, each drawn below as it runs. The decision comes from your hospital, lab or pharmacy system or criteria you set; the journey carries it. Clinical decisions stay in your system. Aims are targets to agree in the pilot, not results.

PLAYBOOKS · 01

Reach the result nobody opened.

A result released by your lab system sends a notice to the Inbox with no result inside, checks whether your app reported a view within forty-eight hours, and if not sends one WhatsApp with View result or Call me, then a call for silence.

Decides
your lab system's release; the patient.
Aim
results seen, on the record.
Built in the journey builder
Reach the result nobody openedHEALTHCAREThe notice carries no result; the result stays in your system, behind your login.
Healthcare
PLAYBOOKS · 02

Offer the health check when the pattern says it is due.

A patient not seen in fourteen months enters a segment; your system confirms the check is due and not booked, then one WhatsApp offers Book a slot or Not now, and a tap fetches the open slots and books in your system.

Decides
your screening rules and your scheduler.
Aim
screenings booked without a call list.
Built in the journey builder
Offer the health check when the pattern says it is dueHEALTHCAREYour system confirms the check is due and not booked before anything is offered.
Healthcare
PLAYBOOKS · 03

Offer home sample collection the day a test is ordered.

A test ordered in your lab system asks whether collection covers the patient's address, then sends one WhatsApp with Collect at home or Visit the lab; a tap books the collection in your system and confirms the time window.

Decides
your lab system and its collection coverage.
Aim
more samples collected, fewer tests never taken.
Built in the journey builder
Offer home sample collection the day a test is orderedHEALTHCAREYour lab system confirms coverage before the offer; a tap books the collection.
Healthcare
PLAYBOOKS · 04

Book the follow-up the discharge letter asked for.

A discharge with a follow-up due waits three days, asks your scheduler whether it is booked, and if not sends the open slots in one WhatsApp; the patient picks in the message, and silence gets a call from your desk.

Decides
your scheduler; the patient.
Aim
follow-ups booked before they are forgotten.
Built in the journey builder
Book the follow-up the discharge letter asked forHEALTHCAREYour scheduler answers first; the patient picks a slot in the message.
Healthcare
PLAYBOOKS · 05

Catch the refill before it lapses.

The journey waits until the refill date your pharmacy system holds, sends Order refill with one tap, checks seven days later whether the refill was collected, and only then reminds once more and calls.

Decides
your pharmacy system's date and stock.
Aim
fewer refills that quietly lapse.
Built in the journey builder
Catch the refill before it lapsesHEALTHCAREWaits for the date your pharmacy system holds; checks before anyone is reminded twice.
Healthcare
PLAYBOOKS · 06

Turn a booking session into a booking.

A session with the booking screen opened twice and no appointment made checks consent, fetches the open slots from your scheduler, and sends one WhatsApp with the slot they were looking at; a tap books it in your system.

Decides
your scheduler; the patient.
Aim
more bookings from the sessions that stalled.
Built in the journey builder
Turn a booking session into a bookingHEALTHCAREA session rule, a consent check, the slots your scheduler holds, one message.
Healthcare
PLAYBOOKS · 07

Confirm tomorrow's appointment, or reschedule it in the message.

A reminder waits for confirm, reschedule or cancel by button, reply or keypad, fetches open slots from your scheduler if asked, and calls the patient who says nothing.

Decides
your scheduler; the patient.
Aim
fewer no-shows.
Built in the journey builder
Confirm tomorrow's appointmentHEALTHCAREYour scheduler answers mid-journey.
Healthcare
PLAYBOOKS · 08

Fill the slot a cancellation frees.

A cancellation in your scheduler sends push and Inbox to the waitlist segment for that clinic; the first tap books the slot in your system and confirms, and everyone else hears nothing more.

Decides
your scheduler; the waitlist you define.
Aim
freed slots filled the same day.
Built in the journey builder
Fill the slot a cancellation freesHEALTHCAREThe waitlist is a segment you define; your scheduler decides who got there first.
Healthcare
PLAYBOOKS · 09

Check in after discharge, and escalate the worried.

A day-three WhatsApp with three buttons sends I'm worried to your care team by API the same minute, books a callback for Some questions, and schedules the day-ten check-in for the rest.

Decides
the patient's answer; your care team.
Aim
the worried patient reached the same day.
Built in the journey builder
Check in after discharge, and escalate the worriedHEALTHCAREThree buttons; the worried answer becomes a task for your care team the same minute.
Healthcare
PLAYBOOKS · 10

Bring back the patient who has drifted.

A patient who enters RFM At Risk on visits gets one message from the clinic, not an offer; a reply becomes a task for patient services, and silence waits thirty days, checks for a visit, and ends with a call.

Decides
your RFM windows; your patient services team.
Aim
the drifting patient reached before they are lost.
Built in the journey builder
Bring back the patient who has driftedHEALTHCAREOne message from the clinic, not an offer; a reply reaches a person.
Healthcare

Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.

The pilot

One use case. Six to eight weeks. A number you agreed first.

Book a Demo