In Automation Appointment reminders, SMS template input fields inserts data depending on whether the SMS reminder is sent for one/multiple appointments on the same day with the same provider.
Setup Appointment Reminder Recipient
The input fields rely on the recipient of the patient’s appointment reminder.
-
Click the navigation menu > Patients > Patient page > Address tab
-
Send Appt. Reminders > Select the recipient of the patient’s appointment reminder
By default, this is set to the head of the family, who is usually responsible for patient communication. Change the recipient of the appointment reminder if the patient’s reminder should not be sent to the head of the family.
Single Appointment Reminders
-
Patient is the recipient of their own appointment reminder
- Firstname: Recipient name
- Appointment Name(s): you
- Next Appointment(s): on Tue 16/09/21 at 09:00am
Example: Hi James, this is a dental appointment reminder for you on Thurs 16/09/2021 at 09:00am.
-
Patient is a family member of the recipient
- Firstname: Recipient name
- Appointment Name(s): Patient name
- Next Appointment(s): on Tue 16/09/21 at 09:00am
Example: Hi James, this is a dental appointment reminder for Noah on Thurs 16/09/2021 at 09:00am
Multiple Appointment Reminders
When a family have appointments on the same day with the same provider, one SMS will be sent out if the family members have the same recipient for their appointment reminders. For example, Mum is the head of the family and receives appointment reminders for herself and her children.
- If the family’s appointments are scheduled at various times on the same day, the below data will be inserted into input fields.
-
Firstname: Recipient name
-
Appointment Name(s): you, Joel and Keegan
-
Next Appointment(s): on Tue 16/09/21 at 09:00am, 12:00pm, 3:00pm
-
-
If the family has consecutive appointments, the below data will be inserted into input fields
- Firstname: Recipient name
- Appointment Name(s): you, Joel and Keegan
- Next Appointment(s): on Tue 16/04/19 starting at 10:00am
Comments
Article is closed for comments.