Eaglesoft Appointment Reminder Setup: The Canadian Clinic Guide (CASL-Compliant)

Eaglesoft appointment reminder setup runs in three stages: build your Recall Types and intervals, attach them to the service codes that trigger them, then activate a messaging channel and record CASL consent for every patient before a single reminder sends. The first two stages happen inside Eaglesoft. The third is where Canadian clinics carry obligations the software does not track for them.

Patterson Dental states that nearly 30,000 users rely on Eaglesoft, with integration into more than 55 authorised third-party solutions. This guide covers the exact menu paths for Eaglesoft recall setup, the CASL rules that apply to every automated message a Canadian practice sends, and how to judge whether Patterson eReminders alone is enough for your clinic.

What Is Eaglesoft Recall and Why It Drives Every Reminder

Recall is the module that tracks when each patient is next due. Where some systems call this continuing care, Eaglesoft organises it around Recall Types: a named entry such as prophylaxis, perio maintenance or bitewings, each carrying its own frequency and an assigned provider. A patient with no recall record, or with a frequency that does not match your clinical protocol, will not appear on the recall list and will not receive automated Eaglesoft patient reminders.

The link between clinical work and the recall date is the service code. According to Patterson's support documentation on tracking recalls, a service code with the Updates Patient Recall preference ticked will push the patient's recall date six months into the future by default when that code is walked out, or by the frequency set on the patient's own record. Miss that tick box on a code your hygienists use daily and the recall date silently never advances.

Recall frequency is a clinical decision, not an administrative default. The Canadian Dental Association's long-standing position is that continuing care intervals should follow a risk assessment of the individual patient rather than a single fixed schedule, with higher-risk patients seen more often. Whatever intervals your clinic settles on, they have to be entered accurately in Eaglesoft for any reminder system, built in or third party, to reach the right people.

Eaglesoft Appointment Reminder Setup: The Five Configuration Steps

The question of how to set up appointment reminders in Eaglesoft has a longer answer than the menu paths alone suggest, because two of the five steps sit outside the software. Work through them in order, since each depends on the one before it. The wider rules governing what those messages may say and who may receive them are covered in our guide to CASL compliance for dental SMS reminders.

Step 1: Enable Multiple Recalls

Open File | Preferences | General and tick Use Multiple Recalls. Patterson's documentation notes this option is available in Eaglesoft version 12 and above. Single-recall practices can track only one due date per patient, which forces prophylaxis, perio maintenance and radiographs onto the same interval. Multiple recalls let each run on its own clock, and that separation is what makes a segmented reminder sequence possible later.

Step 2: Build Your Recall Types and Statuses

Go to Lists | General Setup | Recall Types and select New. Each type takes a Description, a Frequency and a Provider, with optional Plus 1 Day and Use This Type By Default settings. Give every type a plain, patient-readable description, because that wording can surface in the reminder a patient actually reads.

Then open Lists | General Setup | Recall Statuses and define an abbreviation and description for each status your front desk uses, for example contacted, left message, appointment booked or declined. Statuses are what let you separate patients who have been chased from those who have not, and that distinction is what turns a recall list into a work queue somebody can actually work.

Step 3: Tag the Service Codes That Advance Recall

For each service code that should move a patient's recall date, tick Updates Patient Recall and select which recall type the code triggers. Recall types can also be attached to appointment types, so booking the appointment sets the expectation as well as completing it.

Audit this before going live. A code used hundreds of times a year without the tick box is invisible in testing and corrosive in production: those patients simply stop cycling. Patterson advises that once recall setup is complete, practices ring the Patterson Technology Center to run a database validation that updates existing recall dates, and that this validation needs exclusive use of the database, so it belongs outside surgery hours.

Step 4: Activate a Messaging Channel

Eaglesoft does not send patient messages by itself. Patterson's own option is eReminders, which sends phone calls, emails and text messages, lets patients confirm, automatically updates the status of scheduled appointments, and lets the practice choose its own reminder timeframe. The alternative is a third-party recall platform that reads your Eaglesoft database and runs the sequence outside it.

Whichever channel you pick, set at least two touchpoints per appointment: a confirmation request about seven days out, and a final reminder 24 to 48 hours before. For patients who are recall-due but not booked, a separate sequence at 7, 30 and 90 days past the due date does the reactivation work. Ready-made wording for each of those touchpoints is covered in our CASL-compliant dental appointment reminder templates.

Step 5: Record CASL Consent Before Anything Sends

This is the step that has no Eaglesoft menu path. Consent has to be captured at intake and recorded somewhere auditable, with the basis, the date and the method. Some practices add a dated note to the patient chart, others add a consent field to their intake forms, others rely on a messaging platform that logs consent natively. What matters is that the record exists before the first automated message goes out, not after a complaint arrives.

What CASL Requires of Every Eaglesoft Reminder

Canada's Anti-Spam Legislation governs commercial electronic messages, and automated appointment and recall messaging generally falls inside that definition. Consent comes in two forms, and the difference decides how long you may keep messaging a patient.

Innovation, Science and Economic Development Canada's guidance on getting consent to send email states that express consent "means someone has agreed (verbally or in writing) to receive a commercial electronic message from you" and that "there is no time limit unless the recipient withdraws his or her consent". Implied consent is narrower: the same guidance says it "may be valid for up to 2 years, or just 6 months in the case of inquiries or applications".

For a dental practice, that gap is the whole problem. A patient last seen 26 months ago is exactly the patient your recall list most wants to reach, and is exactly the patient whose implied consent has lapsed. Express consent captured at intake is the only version that survives a long absence, which is why getting CASL consent right at the point of capture matters more than any reminder setting.

Every message also needs a working unsubscribe. The same federal guidance requires an unsubscribe mechanism under subsection 11(1) of CASL, with clear instructions, and says requests must be actioned "within 10 business days or less and at no cost to the recipient". For SMS specifically, ISED's guidance on texting for good client relations is blunt: consent is required for text messages, a STOP request must be respected, and your business name belongs in the message.

Patterson eReminders vs a Standalone Recall Layer

Both routes work. The decision comes down to sequence depth, where your consent record lives, and how much Canadian-specific handling you need.

eReminders suits a practice that wants one vendor relationship and a straightforward confirmation workflow, with no synchronisation lag between the schedule and the message. The caveat for Canadian clinics is that the product page describes what the service sends without any reference to CASL, consent records or opt-out timelines, and Patterson advertises its Eaglesoft support as US-based. Neither is a defect. It does mean the compliance layer is yours to build and evidence.

A standalone layer suits clinics running longer sequences, recovering short-notice cancellations, or reactivating patients dormant past the two-year implied consent line. The best appointment reminder software for Eaglesoft in this category reads the patient database directly, so nobody is exporting spreadsheets on a Friday afternoon. Clinics weighing the same decision on another system can compare the Dentrix reminder setup path, the ABELDent automated recall setup or the ClearDent reminder configuration guide, which follow the same three-stage shape with different menus.

When Your Eaglesoft Reminder Configuration Needs More

A built-in confirmation tool is usually enough until one of these becomes true:

• Recall-due patients overdue by 90 days or more make up a large and growing share of your active list
• Front-desk staff spend hours each week on manual recall calls that a sequence could have made
• A meaningful number of patients sit past the two-year implied consent window with no express consent on file
• You cannot produce, on request, the date and basis of consent for a given patient
• You need bilingual French and English messaging for a francophone patient base
• Short-notice cancellations go unfilled because nobody has time to ring a waiting list

At that point a dedicated recall layer earns its cost by running the sequences a confirmation tool was never built for. DentRecall, for example, connects to Eaglesoft and 50+ other PMS platforms on a read-only basis, logs CASL consent with its basis and date, and runs a five-touchpoint sequence that carries a patient from overdue to confirmed without front-desk intervention. Clinics that add automated cancellation recovery on top of a working recall sequence tend to see the gap close fastest, because the two problems share the same waiting list.

Frequently Asked Questions

How do I set up recall in Eaglesoft?

Enable Use Multiple Recalls under File | Preferences | General, then create your recall entries under Lists | General Setup | Recall Types, giving each a Description, Frequency and Provider. Define your Recall Statuses under the same menu, then tick Updates Patient Recall on each service code that should advance a patient's due date. Patterson recommends running a database validation through the Patterson Technology Center once setup is complete.

Does Eaglesoft send appointment reminders on its own?

No. Eaglesoft tracks recall dates and appointments, but sending the message requires a messaging channel. Patterson's own option is eReminders, which sends phone calls, emails and text messages, lets patients confirm, and automatically updates the status of scheduled appointments. Third-party recall platforms that read the Eaglesoft database are the alternative.

Do Eaglesoft appointment reminders need CASL consent?

Yes. Automated reminders sent by SMS or email are commercial electronic messages under CASL, so consent is required before sending. Express consent has no time limit unless the patient withdraws it, while implied consent from an existing business relationship may be valid for up to two years, or six months in the case of an inquiry. The practice, not the software, is responsible for holding that record.

What is the default recall interval in Eaglesoft?

When a service code with the Updates Patient Recall preference is walked out, Eaglesoft moves the patient's recall date six months into the future by default, or by the frequency set on that patient's own record. The Canadian Dental Association's position is that continuing care intervals should reflect an individual risk assessment rather than a single fixed schedule, so the default is a starting point and not a clinical recommendation.

How quickly must a STOP request be honoured?

Federal guidance requires an unsubscribe mechanism under subsection 11(1) of CASL and says requests must be actioned within 10 business days or less, at no cost to the recipient. For SMS, respecting a STOP reply is explicitly called out in the government's texting guidance. Update the patient record straight away so no later sequence picks them back up.

Key Takeaways

• Eaglesoft appointment reminder setup is three stages: recall configuration, service code tagging, then messaging plus consent. Only the first two live in the software.
• The Updates Patient Recall preference on service codes is the hinge. Without it, recall dates never advance and reminders quietly stop reaching the right patients.
• Enable Use Multiple Recalls, available in Eaglesoft version 12 and above, so prophylaxis, perio maintenance and radiographs run on separate intervals.
• CASL express consent has no expiry, but implied consent lapses after two years, which is precisely when a lapsed patient most needs contacting.
• Patterson eReminders covers confirmations well. Longer recall sequences, consent audit trails and bilingual messaging are where a standalone Canadian layer adds value.