Skip to main content
Text a patient 24 hours before their appointment, email them if the text isn’t delivered, and stop the reminder when the appointment moves. Each message says when to come in and links to your app for the rest, so clinical details stay in your system. Keep PHI out of the message. The reminder carries the time and a link, never the reason for the visit or a specialty that reveals one. For BAAs and Courier’s HIPAA program, see HIPAA and BAAs.

Prerequisites

Build the Journey

1

Create the Journey and its trigger

Open Journeys, select New Journey, name it appointment-reminder, and choose the API Invoke trigger.Add three fields to the trigger schema:
  • appointment_id: your ID for the appointment
  • appointment_at: when the appointment starts, as an ISO 8601 datetime
  • remind_at: when to send the reminder, as an ISO 8601 datetime. Your app computes it, 24 hours before appointment_at
2

Add an appointment reminders topic

In the preferences editor, add a topic named Appointment reminders with the default On. Leave it off Required, so patients can opt out.You’ll map both reminder templates to this topic. Mapping a template to a topic makes Courier enforce the patient’s preference on every send. See Build a preference center.
3

Wait until the reminder time

Add a delay node, set the interval type to Until, and turn on Dynamic Interval. Select data.remind_at as the field. Each patient’s run waits until their own reminder time.
4

Send the SMS reminder

Add a send node on the SMS channel and select + Create to write the template. Use the clinic name, the time, and a link, and nothing about why the patient is coming in:
datetime-format shows the time in the patient’s timezone from their profile, and in New York time when it isn’t set. See Variables. In the template’s settings, set the subscription topic to Appointment reminders.
5

Give the text time to arrive

Add a delay of 30 minutes. Courier polls Twilio for each text’s status, so a check made right after the send would find most texts not yet delivered.
6

Email the patient if the text wasn't delivered

Add a send node on the Email channel with the same reminder, and map its template to the Appointment reminders topic too.Give it one condition: send_status.<SMS node ID> was not DELIVERED. The node ID is the SMS node’s id, shown in the editor and returned when you create the Journey over the API. Patients whose text arrived skip the email. Patients whose text failed, or who have no phone number, get it. A text still waiting on carrier status after 30 minutes also triggers the email, so lengthen the delay if your carriers report slowly.
7

Set a cancelation token and publish

In the Journey’s settings, set the cancelation token to appt-{{data.appointment_id}}. Each appointment’s run carries its own token, so a reschedule stops only that reminder. Always pass appointment_id, because a token that references missing data isn’t set.Publish both templates, then select Publish on the Journey and copy its ID.

Trigger it from your app

1

Start the reminder when an appointment is booked

Call POST /journeys/{templateId}/invoke from the code that books the appointment. Replace appointment-reminder with your Journey ID. The samples use an appointment a week from now and a reminder a day before it.
Send times as UTC ISO 8601 strings. For an appointment booked less than 24 hours out, send a one-off confirmation instead of starting the reminder. The idempotency key makes a retried request return the same run instead of starting a second reminder.
2

Stop it when the appointment moves

When an appointment is canceled or rescheduled, call POST /journeys/cancel with its token. Pending steps never fire.
For a reschedule, cancel first, then start a new run with the new times. Include the new time in the idempotency key, such as appointment-booked-appt_4Fq9-2026-12-03T17:30, so the new request doesn’t return the canceled run.

Verify

1

Run it on a short clock

Duplicate the Journey for testing, set the copy’s 30-minute delay to 2 minutes, and change its cancelation token to appt-test-{{data.appointment_id}}. Publish the copy and invoke it for a test patient with remind_at a few minutes from now.
2

Follow the run

Open the Journey’s Logs tab and select the run. Click a node to see its input, the conditions it evaluated, and its output. Open the SMS message and confirm the text has the time and the link, and nothing clinical.
3

Check the email fallback

Invoke the copy for a test patient with an invalid phone number. The SMS doesn’t reach DELIVERED, and the email goes out.
4

Check the opt-out

Opt the test patient out of Appointment reminders and invoke again. Both sends end as FILTERED with the reason UNSUBSCRIBED.
5

Confirm a cancel stops the run

Invoke once more, then cancel with the test token while the run waits at the first delay. The run reads Canceled in the Logs tab.

FAQ

The reason for a visit is protected health information, and a text shows on lock screens and shared phones. Keep it in your app behind sign-in. See HIPAA and BAAs.
Add another Until delay on a second field, such as remind_1h_at, followed by a second SMS node. The appointment reminder recipe has both reminders, ready to copy.