Prerequisites
- A Courier API key
- Twilio connected with delivery status polling turned on, so Courier knows whether each text arrived
- A connected email provider
- Your patients stored in Courier with a phone number, an email address, and a timezone
Build the Journey
Create the Journey and its trigger
appointment-reminder, and choose the API Invoke trigger.Add three fields to the trigger schema:appointment_id: your ID for the appointmentappointment_at: when the appointment starts, as an ISO 8601 datetimeremind_at: when to send the reminder, as an ISO 8601 datetime. Your app computes it, 24 hours beforeappointment_at
Add an appointment reminders topic
Wait until the reminder time
data.remind_at as the field. Each patient’s run waits until their own reminder time.Send the SMS reminder
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.Give the text time to arrive
Email the patient if the text wasn't delivered
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.Set a cancelation token and publish
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
Start the reminder when an appointment is booked
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.Stop it when the appointment moves
POST /journeys/cancel with its token. Pending steps never fire.appointment-booked-appt_4Fq9-2026-12-03T17:30, so the new request doesn’t return the canceled run.Verify
Run it on a short clock
appt-test-{{data.appointment_id}}. Publish the copy and invoke it for a test patient with remind_at a few minutes from now.Follow the run
Check the email fallback
DELIVERED, and the email goes out.Check the opt-out
FILTERED with the reason UNSUBSCRIBED.Confirm a cancel stops the run
FAQ
Can the reminder include the reason for the visit?
Can the reminder include the reason for the visit?
How do I add a second reminder an hour before?
How do I add a second reminder an hour before?
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.