One appointment identity
Reminders should refer to the same appointment the front desk edits, the clinician sees, and the patient manages in the portal.
- Shared appointment context
- Fewer mismatched times
Appointment reminders
Reduce no-shows and last-minute confusion by keeping reminder work attached to real appointments, patients, and clinic-configured delivery channels — instead of maintaining a separate notification product that drifts from the schedule.
Integration setup
Appointment reminders connect through clinic-specific email and SMS accounts and settings. During onboarding, we confirm which reminder channels your practice uses, who owns each account, and what setup is required.
Why connection matters
Because the schedule is not static. Patients reschedule, clinicians take leave, locations change, and waitlist fills move. A reminder system that does not share appointment identity with the clinic schedule becomes another list to reconcile — often after the wrong message already went out.
Reminders should refer to the same appointment the front desk edits, the clinician sees, and the patient manages in the portal.
Delivery depends on accurate patient contact details maintained in the practice record, not a one-off spreadsheet export.
Reminder delivery is configured for the practice so ownership of email and SMS accounts is explicit during onboarding.
Workflow
Staff create or update the visit in the clinic schedule with patient, time, service, and location context attached.
Patients can also view and manage appointment activity through the portal when those workflows are enabled for the practice.
Reminder delivery uses the clinic's authorized notification setup rather than a personal staff inbox workflow.
Cancellations, reschedules, and waitlist fills are schedule operations first. Reminder context should follow the appointment, not fight it.
Connected handoffs
Reminders only work when the schedule is the system of record for time, provider, and location.
Patients still need a place to confirm, request, or manage appointments beyond a one-way reminder.
When a reminder prompts a question, staff and patients continue in a conversation attached to patient context.
Review flat per-practice plans and request a walkthrough focused on your no-show and reminder process — with the same connected clinic view you evaluate day to day.
In practice
Two patients move times and one cancels. Staff edit the appointment records in the clinic schedule rather than updating a separate reminder spreadsheet.
A waitlist patient takes the cancelled slot. The new appointment carries patient and service context immediately.
Portal schedule activity and reminder delivery continue from the updated appointment identity instead of an exported list from this morning.
The next day's reminders refer to the schedule as it actually stands, not the version that existed before the afternoon reshuffle.
Reminders FAQ
Reminder workflows are part of the connected scheduling and patient-communication model. Delivery channels such as email and SMS are connected through clinic-specific accounts and settings confirmed during onboarding.
No. Reminders notify. The patient portal is where patients complete concrete tasks — reviewing appointments, forms, messages, bills, and enabled telehealth sessions. Practices usually need both.
Staff update the appointment in the clinic schedule. Because reminders and patient-facing schedule activity are meant to follow that appointment context, the operational goal is one change in the system of record rather than separate edits in a notification tool.
Yes. Location-aware scheduling is part of the platform model. Reminder and schedule operations should preserve the appointment's location and provider context so patients receive information that matches the site they are supposed to attend.
Bring how you currently remind patients, who owns exceptions, and where reschedules break down. We will focus the walkthrough on that operating path.