Reminders designed to reach patients before they miss the chair.
Automated text and email messages before upcoming visits, confirmations logged back to the PMS, and pre-medication alerts — for practices on Dentrix, Eaglesoft, Open Dental, and other major PMS. TCPA-compliant consent and STOP handling included.
Illustrative display. Actual reminder log varies by configuration and PMS.
Designed to keep your schedule filled and patients informed
Manual phone calls take time your front desk may not have. mConsent reminders are designed to reach patients by their preferred channel — text or email — and log the response back to the chart.
SMS & email delivery
Designed to send appointment reminders by text and email based on the cadence your practice configures — days, hours, or a combination before the visit.
One-tap confirmation
Designed to let patients confirm or request a change by replying to the message. The response is designed to log against the PMS appointment record.
Configurable schedule
Set reminder intervals that match how your office operates — a week before, a day before, an hour before, or a custom combination your team prefers.
Intake forms with reminders
Designed to include a link to digital intake forms inside the reminder message so patients can complete paperwork before arrival.
Automated recalls
Designed to send recall messages to patients approaching or past their next recommended visit, helping your practice stay connected.
TCPA-compliant messaging
SMS workflows are designed to capture express patient consent and to honor STOP-to-unsubscribe requests consistent with the TCPA, state messaging laws, and carrier requirements.
From PMS appointment to patient confirmation
Your PMS stays the system of record. mConsent is designed to read the schedule, send the right message at the right time, and write the patient’s response back to the chart.
- Read the schedule — designed to pull upcoming appointments and patient contact details from the PMS.
- Send reminders — text and email at the intervals your practice configures, with intake form links when enabled.
- Capture patient response — confirm, cancel, or reschedule replies designed to update appointment status.
- Flag pre-med patients — designed to identify patients with pre-medication requirements and include an alert.
- Write back to chart — designed to log confirmation status and delivery receipts against the patient record.
Illustrative display. Actual reminder log varies by configuration and PMS.
Designed to flag pre-med patients before their appointment
For patients who may require pre-medication before certain procedures, mConsent is designed to include a pre-med alert alongside the standard appointment reminder.
- Designed to identify eligible patients — reads pre-medication flags from the patient record in the PMS.
- Designed to include a pre-med message — adds a pre-medication reminder alongside the standard notification.
- Designed to support practice safeguards — communicates pre-med requirements to patients before their visit. The practice is responsible for clinical determinations.
- Designed to log delivery — records that the pre-med reminder was sent and whether the patient acknowledged it.
The practice is responsible for clinical determinations about which patients require pre-medication. mConsent reads flags from the PMS and is not a substitute for clinical judgment.
Illustrative display. Actual message content is configurable by the practice.
Reminders work alongside the rest of the mConsent platform
Appointment reminders are one tool inside the Communication module. They are designed to work with intake, payments, and scheduling to keep the patient journey connected.
Communication
The parent module — reminders, 2-way texting, Quick Fill, recalls, and patient messaging in one suite.
Paperless Intake
Designed to collect intake forms before the visit and attach them to the reminder message link.
mPayr
Designed to send payment links alongside reminders so patients can settle balances before or after the visit.
Zaha AI
AI phone coverage designed to route scheduling calls and attach call summaries to the patient record.
Insurance Concierge
Designed to verify eligibility and benefits before the appointment, surfaced alongside the reminder workflow.
Online Scheduling
Designed to let patients self-schedule online and receive automated reminders for the new appointment.
Common questions about appointment reminders
See how automated reminders fit your practice
A short demo covering reminder setup, patient confirmation flow, pre-med alerts, and PMS write-back. Subject to your master services agreement.
mConsent appointment reminders are part of the Communication module. Capability described on this page is illustrative based on typical configurations; actual results vary by PMS version, network, and practice. Pricing and program terms are governed by the MSA at activation. mConsent operates as a Business Associate under HIPAA and executes a BAA with client practices.
Full Disclosures & Trademarks
Technology partner status
mConsent is an independent software vendor that operates as a technology partner connecting to Dentrix, Eaglesoft, Open Dental, Dolphin, and other practice management systems. mConsent is not affiliated with, endorsed by, or sponsored by the companies that own or operate those systems.
Connector scope & capability
mConsent appointment reminders are designed to read and write supported data with currently-supported PMS versions. Available reminder channels, confirmation actions, write-back behavior, and pre-medication alert features depend on the PMS version installed at your practice, your network configuration, and options selected during onboarding. mConsent does not promise feature parity across PMS versions, editions, or environments.
SMS, voice & TCPA
Where any feature on this page sends a message to a patient — appointment reminders, recall messages, pre-medication alerts, or confirmation requests — the system is designed to capture express patient consent and to honor opt-out requests consistent with the federal Telephone Consumer Protection Act (TCPA), state messaging laws, and carrier requirements. The practice is responsible for the lawful use of these features — including how it obtains, records, and refreshes consent.
Pricing & MSA
All commercial terms — including pricing, included modules, available integrations, support hours, and uptime objectives — are governed by the master services agreement (MSA), order form, and applicable schedules executed between mConsent and the practice. Marketing copy on this page is descriptive of intended capability and does not modify or supersede those agreements. In any conflict, the executed agreements control.
Trademark attribution
Dentrix is a trademark of Henry Schein One, LLC. Eaglesoft is a registered trademark of Patterson Dental Supply, Inc. Open Dental is a registered trademark of Open Dental Software, Inc. Dolphin Management and Dolphin Imaging are products of Dolphin Imaging & Management Solutions, a Patterson Dental company. mConsent is an independent software vendor. Reference to these systems on this page is for identification purposes only.
HIPAA & protected health information
mConsent operates as a Business Associate under HIPAA and executes a Business Associate Agreement (BAA) with each customer. Patient information used in reminder workflows — names, contact details, appointment times, and pre-medication flags — is handled under the terms of the BAA, the practice’s Notice of Privacy Practices, and applicable federal and state laws. The practice remains responsible for its own use of the platform, including the consents it relies on.
Verified figures & forward-looking language
Aggregate platform figures referenced on this page are limited to: 5,000+ practices served since 2017, 5.5M+ patients, 30M+ documents processed, and 11M+ appointments handled across the platform. They reflect lifetime cumulative totals from mConsent system logs since 2017 and are not annualized. They are not a forecast or guarantee of any individual practice’s results. Phrases such as “designed to,” “intended to,” “built to,” and similar describe how a feature is engineered to behave in typical configurations and are not promises of any specific outcome, response time, or revenue impact for any individual practice.