Dental recall automation in GoHighLevel stores each patient's next hygiene due date in a date field and uses the Custom Date Reminder workflow trigger to send a reminder a set number of days before that date, then follow-ups if they have not booked. HighLevel's trigger fires before, on or after a date field you choose, contacts with an empty date never trigger it, and a before-reminder and an after-reminder need two separate triggers in the same workflow. The hard part is not the workflow; it is getting clean due dates from the practice software into the contacts. This page covers the 6-month recall logic, the multi-channel cadence, the overdue tiers at 6, 9, 12 and 18 months, reactivation offers and year-end insurance messaging, the list import from Dentrix, Open Dental or Eaglesoft, consent and HIPAA, how to measure recall rate, and cost. It is information, not legal advice.
How does dental recall automation work in GoHighLevel?
Dental recall automation in GoHighLevel runs from a custom due-date field on each contact, with Custom Date Reminder triggers before and after the date and an option to repeat every year.
Veterinary practices run the same recall pattern per pet, using a Pets custom object so each animal keeps its own due dates; see GoHighLevel for veterinary clinics. Optometry recall is the same build with a 12 or 24 month interval; see GoHighLevel for optometrists.
| Piece | Setting |
|---|---|
| Data | A custom date field on each contact, such as "hygiene_due", filled from the practice software |
| Trigger | Custom Date Reminder on that field, before the date (for example 30 days) |
| Second trigger | Another Custom Date Reminder for after the date (for example 14 days overdue), in the same workflow |
| Annual repeat | The trigger has a Match on Year option; for a rolling due date, update the field after each visit instead |
| Empty dates | Contacts with no value in the field do not trigger |
| Exit | When the patient books or the due date is updated |
Source: HighLevel's Custom Date Reminder trigger article (modified September 29, 2026, read November 2, 2026). The trigger works on contact date fields and supported opportunity date fields in contact workflows, and on custom object and company date fields in those workflow types. Its filters are Before Number of Days, After Number of Days, Day Is, Month Is, Match on Year and Has Tag. The article does not state a time of day, so check when it fires in your account and set the location time zone correctly. The GoHighLevel for dental practices guide places recall among the nine workflows a practice builds; this page is the detailed build.
- 30 days beforeEmail and text
- 7 days beforeText with openings
- 14 days overdueText
- 45 days overdueCall task for those who have not responded
How do you build six-month recall reminder logic in HighLevel?
Store the last hygiene visit date, calculate the due date as last visit plus the patient's interval (3, 4 or 6 months) in the practice software or at import, write it to a "hygiene_due" date field, and let Custom Date Reminder triggers fire 30 days before, 7 days before and at the overdue tiers.
- Create the fields. Settings > Custom Fields > Add Field: "Last hygiene visit" (date), "Hygiene due" (date), "Recall interval months" (number: 3, 4 or 6), "Recall type" (dropdown: prophy, perio maintenance, exam only), "Consent to text" (checkbox), "Insurance plan year end" (date). See custom fields and tags.
- Decide where the due date is calculated. Most practice management systems already hold a recall due date per patient; export that column. If yours exports only the last visit date, add the interval in the spreadsheet before import. HighLevel's workflow Math action can add days to a date field, but doing the arithmetic in the export keeps one source of truth.
- Create the workflow. Automation > Workflows > Create Workflow. Trigger 1: Custom Date Reminder, field "Hygiene due", Before Number of Days 30, Has Tag "recall-active". Trigger 2: same field, Before Number of Days 7. Trigger 3: After Number of Days 14. Trigger 4: After Number of Days 45. Each trigger enters the same workflow; an If/Else on the trigger reads which touch to send, or you build one small workflow per touch, which is easier to report on.
- Add the exit. Before each message, If/Else: appointment filter "has an upcoming appointment on the hygiene calendar". If yes, End Workflow and remove the tag "recall-active". The Appointment Status trigger (modified April 6, 2026) can run a separate workflow that removes "recall-active" the moment a hygiene appointment is booked, which is more reliable than checking at send time.
- Roll the date forward. After the hygiene visit is marked Showed, a workflow sets "Last hygiene visit" to the appointment date and "Hygiene due" to that date plus the interval, and re-adds "recall-active". Without this step every patient gets recalled once and never again.
- Test. Create a test contact, set "Hygiene due" to 30 days from today, publish, and watch Execution Logs tomorrow. Then set the date 14 days in the past and confirm the overdue text fires. HighLevel's article confirms contacts with an empty date field never trigger, so also test a contact with no date to confirm silence.
Why not a Wait step of 180 days after the visit? It works for a single interval but breaks when a patient's interval changes, when a visit is rescheduled, or when the account is paused and resumed. A date field plus the reminder trigger is re-computable and visible to the front desk; a contact stuck in a six-month Wait is neither.
What should the recall cadence be across text, email and phone?
A booking link by email and text 30 days before the due date, a text 7 days before, a text at 14 days overdue, an email with a reason to return at 30 days overdue, and a phone call at 45 days; after that the patient leaves recall and enters the overdue tiers below.
| When | Channel | Message | Exit |
|---|---|---|---|
| 30 days before due | Email and SMS | Hi {{contact.first_name}}, it is almost time for your next visit at {{location.name}}. Book here: {{calendar.link}} | Books |
| 7 days before | SMS | We still have openings before your visit is due. {{calendar.link}} | Books |
| Due date | None | Silence on the day itself avoids a third text in a week | |
| 14 days overdue | SMS | Hi {{contact.first_name}}, we have not seen you in a while. Want to book your next visit? {{calendar.link}} | Books |
| 30 days overdue | A short note from the hygienist with the booking link and office hours; no clinical content | Books | |
| 45 days overdue | Call task | A person calls the patients who have not responded; outcome recorded in a dropdown | Task closed |
Four automated touches over 75 days, then a person. Texts carry the booking link because they are read; email carries the longer note and the insurance reminder. Phone is reserved for people who ignored everything, because a call from the practice still moves patients who tune out texts. Cap the sequence, honour opt-outs and stop when the patient books. If someone no-shows after booking, the no-show recovery workflow takes over and hands them back to recall after 30 days.
How should overdue patients be tiered at 6, 9, 12 and 18 months?
Tier by months since the due date, not since the last visit: 0 to 3 months overdue stays in recall, 3 to 6 months (about 9 months since the visit) gets a reactivation sequence with a reason to return, 6 to 12 months gets a different offer and a call, and past 12 months overdue (18 months or more since the visit) the patient is treated as lapsed with one final sequence before the practice decides whether to keep messaging.
| Tier | Months since last hygiene visit (6-month interval) | Months overdue | What runs | Tone | Human step |
|---|---|---|---|---|---|
| Recall | 5 to 7.5 | Up to 1.5 | The cadence above | Routine: "it is time" | Call at 45 days overdue |
| Overdue 1 | 9 | 3 | Reactivation sequence A: three touches over 3 weeks | Welcoming: "we have kept your spot", easy booking | None unless they reply |
| Overdue 2 | 12 | 6 | Reactivation sequence B: two touches plus a call | Specific reason to return (see offers below) | Call by front desk |
| Lapsed | 18 and over | 12 and over | One final sequence of two touches, then tag "lapsed-final" | Short, respectful, with an opt-out | Practice decides whether to keep the patient active |
In HighLevel each tier is a Custom Date Reminder trigger on the same "Hygiene due" field with After Number of Days set to 90, 180 and 365, each with Has Tag "recall-active" so a patient who booked is excluded. The tiers are where most of the recoverable revenue sits, because practices tend to stop messaging after the first overdue text. Many practice management systems count a patient as inactive after 18 months without a visit, which is why the lapsed tier starts there; use your own system's definition so your HighLevel counts match your PMS reports.
What reactivation offers and insurance-benefit messages work?
A specific reason beats a discount: a reminder that the patient's dental insurance benefits reset at year end, a new hygienist or extended hours, or a direct "we have a Saturday opening next month"; discounts on hygiene are rarely needed and can conflict with insurance contracts, so check before offering one.
| Offer or reason | Best tier | Example wording | Caution |
|---|---|---|---|
| Insurance benefits expiring | All tiers, September to early December | Hi {{contact.first_name}}, most dental plans reset on December 31 and unused benefits do not carry over. If you are due for a visit, we have openings before year end: {{calendar.link}} | Only true for plans on a calendar year; store the plan year end per patient where you know it and send on that date instead |
| Convenience | Overdue 1 | We now open early on Tuesdays and have Saturday hygiene twice a month. Book here: {{calendar.link}} | Must be true |
| Hold a spot | Overdue 1 and 2 | We have kept a hygiene spot for you the week of {{custom_values.offer_week}}. Reply YES and we will call to confirm the time. | Needs a real block of openings behind it |
| Personal note | Overdue 2 | Email from the hygienist by name, two sentences, booking link | No clinical content about the patient |
| Fee or membership plan | Overdue 2 and lapsed, uninsured patients | If insurance is the reason you have paused visits, our in-house plan covers two hygiene visits a year. Details: {{custom_values.plan_link}} | Segment by the "insurance or self-pay" field first |
| Discount on hygiene | Rarely | May conflict with insurance contracts and state rules; ask your adviser before offering |
For the year-end message, build a separate workflow on the "Insurance plan year end" date field with Before Number of Days 60 and 30, and Has Tag "recall-active" or an overdue tier tag, so only patients who are actually due get it. Where you do not know the plan year, a date-based send in late October to everyone overdue, filtered to patients marked as insured, is the fallback. We have not found a primary source for the "patients leave hundreds of dollars unused" figures that appear in practice marketing, so the message states the mechanism (benefits reset, unused ones do not carry over) and not a dollar figure.
How do you import the recall list from Dentrix, Open Dental or Eaglesoft?
Export the recall or continuing-care report from the practice management system as a CSV with patient name, phone, email, last hygiene date, recall due date, recall type and consent, clean it, then import at Contacts > Import with the date columns mapped to the custom date fields in one of HighLevel's accepted formats; there is no native Dentrix, Open Dental or Eaglesoft connector, so the import is repeated weekly or replaced by a third-party sync.
- Run the recall report in the PMS. Every major system has one (Dentrix Continuing Care, Open Dental Recall list, Eaglesoft Recare). Export as CSV with the columns above plus patient ID.
- Clean it. One row per patient, phone numbers in E.164 (+1 and ten digits), dates in one of the formats HighLevel accepts: MM/DD/YYYY, YYYY/MM/DD, MM-DD-YYYY or YYYY-MM-DD, per the CSV File Format for Importing Objects article (modified February 25, 2026, read November 2, 2026). Rows with a date the importer cannot parse still import but leave the date field empty, which means those patients never trigger; check the import's error report for error 1014 "Could not parse the date". The file limit is 30 MB.
- Create the custom fields first with the same labels and types, as HighLevel's article requires, and include the patient ID as a custom field so later imports update rather than duplicate.
- Import. Contacts > Import > upload > map columns > choose "update existing contacts" using phone or email as the match key > add the tag "recall-active" and a tag for the import date.
- Validate counts. Smart list on "Hygiene due is not empty" should match the PMS report row count. Fix the gap before any workflow is published.
- Refresh weekly. Re-run the report and import with update, so patients who booked or visited get new dates and leave the workflow. Or connect the PMS by a sync app or webhook where the volume justifies the subscription; our integration study (checked October 28, 2026) found Open Dental has the clearest API path, Dentrix runs through a partner-gated API Exchange and Eaglesoft is listed by one sync vendor only. See integrations.
- Update the field after a visit so the next date moves forward, either from the weekly import or from the Showed-status workflow above.
Importing patient lists raises the same privacy and consent questions as any other messaging; see GoHighLevel for dental practices and the HIPAA add-on cost.
What consent and HIPAA rules apply to recall texts?
Recall texts need A2P 10DLC registration and documented opt-in, and if the account holds patient records or messages that reference a specific patient's care, HighLevel's position is that it needs the $297 a month HIPAA add-on and a signed BAA before patient information goes in; generic recall wording keeps the content minimal but does not remove the question.
Three HighLevel sources set the texting rules, all read November 2, 2026. What is A2P 10DLC (modified September 4, 2026) says registration is required when a business sends SMS or MMS to US recipients from standard local numbers. A2P opt-in compliance (modified July 30, 2026) requires verifiable, optional consent with STOP and HELP language and no pre-checked boxes, which is why the consent column from the PMS matters: patients with no recorded consent to text get email and a call, not SMS. On HIPAA, HighLevel's help says accounts are not compliant by default; the add-on, the BAA and what each covers are on is GoHighLevel HIPAA compliant and HIPAA compliant workflow automation. Whether a hygiene recall reminder is itself a HIPAA communication is fact-specific; confirm with a healthcare attorney. Message content in this page's templates names no procedure, no diagnosis and no treatment plan.
How do you measure recall rate?
Recall rate is the share of patients due in a period who booked a hygiene visit within a set window, usually 30 or 60 days of the due date; hygiene reappointment rate (patients who leave with their next visit booked) is the companion metric, and together they tell you whether recall automation is catching the patients the front desk missed.
| Metric | Formula | Where it comes from in HighLevel | Target |
|---|---|---|---|
| Recall rate (60 day) | Patients with a hygiene appointment booked within 60 days of "Hygiene due" / patients whose due date fell in the month | Tag "recall-booked" set by the Appointment Status workflow; smart list by due-date month | Your own baseline first; consultants commonly quote 75% to 85% as a goal, but we have not found a primary benchmark study |
| Reappointment at checkout | Hygiene visits marked Showed that have a next hygiene appointment booked the same day / Showed visits | Appointment Status workflow checks for a future appointment and tags "reappointed" | As high as the front desk can make it; automation covers the rest |
| Booked per touch | "recall-booked-touch-N" tags / contacts who received touch N | Tag per step | Shows which message earns its keep |
| Overdue backlog | Count of contacts in each overdue tier | Smart lists by "Hygiene due" range | Falling month on month |
| Opt-out rate | DND set after a recall text / recall texts sent | Contacts with DND and the recall tag | If it climbs, the cadence is too dense |
Measure messages booked, not messages sent. A recall workflow that sends 400 texts and books 60 visits is doing its job; one that sends 2,000 and books 70 is irritating 1,900 patients. Dental practice consultants publish re-appointment benchmarks in the 75% to 94% range, but each rests on that consultant's client data, so treat your own month-one number as the baseline.
What does dental recall automation cost?
With us, recall is part of a basic dental build at $500 to $4,000 one-time, quoted in writing after a free call; HighLevel's plan is $97 to $497 a month, the HIPAA add-on $297 a month if patient information goes in, and texting about $0.00747 per segment plus carrier fees, all at the time of writing (checked November 2, 2026).
| Item | Cost at the time of writing | Worked example: 1,200 active patients, 6-month interval |
|---|---|---|
| HighLevel plan | $97 Starter or $297 Unlimited a month | $97 a month for a single practice on Starter; see GoHighLevel cost |
| HIPAA add-on | $297 a month per agency account | Required if patient records or care-specific messages go in; see HIPAA add-on cost |
| SMS | $0.00747 per segment in and out, carrier fees extra | About 200 patients due a month, 3 texts each, plus replies: roughly 800 segments, about $6 plus about $3 carrier fees; see usage costs |
| $0.675 per 1,000 | 400 emails a month: under $0.30 | |
| Build | Within the $500 to $4,000 basic dental build | Fields, import, recall workflow, four overdue tiers, year-end workflow, testing, front-desk training; see setup cost |
| Weekly import or sync | Staff time, or a sync vendor's subscription | About 20 minutes a week for the CSV route |
To judge the return, take the value of one hygiene visit to your practice and divide the monthly platform cost by it: that is the number of recovered visits a month that pays for the system. Most practices with a backlog of several hundred overdue patients clear that in the first overdue tier.
Dental recall mistakes to avoid
- Empty date fields. Those patients never enter the workflow. Check the import error report for unparsed dates.
- No refresh. A recall list that is a month old texts people who already booked.
- No roll-forward. The due date never moves after a visit, so every patient is recalled once.
- Everyone gets the same message. Segment by recall type (prophy, perio maintenance, exam) and by insured versus self-pay.
- No human step. The patients who have been away longest need a call.
- Texting patients with no recorded consent. Route them to email and phone.
- No measurement. Track booked-per-touch, not messages sent.
What we do about this
We set up the fields, clean and import the first recall list, build the recall cadence, the four overdue tiers and the year-end benefits workflow, test them against test contacts and train the front desk on the weekly refresh. The 30-minute call and account audit are free and every price is a written quote; book it on our contact page.
Sources and further reading
Checked at the time of writing; prices, features and policies change. Checked November 2, 2026.
- HighLevel help: "Workflow Trigger - Custom Date Reminder" (modified September 29, 2026, read November 2, 2026): fires before, on or after a date field; Before/After Number of Days, Day Is, Month Is, Match on Year, Has Tag filters; skips contacts with no date; contact, opportunity, custom object and company date fields
- HighLevel help: "Workflow Trigger - Appointment Status" (modified April 6, 2026, read November 2, 2026)
- HighLevel help: "CSV File Format for Importing Objects" (modified February 25, 2026, read November 2, 2026): accepted date formats, E.164 phone numbers, create custom fields first, 30 MB limit
- HighLevel help: "What is A2P 10 DLC: Brand and Campaign Registration" (modified September 4, 2026, read November 2, 2026): registration is required when sending SMS or MMS to US recipients
- HighLevel help: A2P opt-in compliance (modified July 30, 2026): verifiable, optional consent, STOP and HELP language, no pre-checked boxes
- HighLevel pricing page and "HIPAA Compliance With HighLevel" help article, as cited on our HIPAA add-on cost and usage costs pages
Frequently asked questions about dental recall automation
What is a dental recall system?
It is how a practice brings patients back for hygiene and exam visits at the interval the dentist set, usually 3, 4 or 6 months. In GoHighLevel it is a due-date field per patient, reminders before and after that date, overdue tiers for patients who do not respond, and a weekly refresh from the practice management software.
What is the GoHighLevel trigger for dental recall reminders?
Custom Date Reminder, which fires before, on or after a date field you choose, with filters for number of days before or after, day of week, month, matching year and tag. HighLevel's help article was modified September 29, 2026. It does not fire for contacts whose date field is empty.
Can I send a reminder before and after the due date?
Yes, with separate Custom Date Reminder triggers in one workflow, one set to Before Number of Days and others to After Number of Days, per HighLevel's article. The overdue tiers on this page are four such triggers at 14, 90, 180 and 365 days after the due date.
How often should dental patients be recalled?
At the interval the dentist sets for that patient, commonly 6 months for routine hygiene and 3 or 4 months for periodontal maintenance; guidance bodies such as NICE in the UK recommend risk-based intervals rather than a fixed six months. Store the interval per patient in a number field so the automation follows the clinical decision.
What happens to patients with no due date?
They do not trigger the workflow, so clean the data first and check the import error report for unparsed dates (error 1014). A smart list on "Hygiene due is empty" with the active-patient tag shows exactly who is missing and needs a date from the practice software.
How do I get due dates from my practice software?
Export the recall or continuing-care report from Dentrix, Open Dental, Eaglesoft or your system as a CSV, clean the dates into one accepted format, and import with "update existing contacts" on, repeated weekly. There is no native HighLevel connector for these systems; a third-party sync app or webhook can replace the import when the volume justifies its cost.
How many recall messages should I send?
Two before the due date, two after, then a phone call at about 45 days overdue; after that the patient moves to the overdue tiers, which send two or three touches each at 3, 6 and 12 months overdue. Stop the moment the patient books, and measure booked-per-touch so you can drop a message that earns nothing.
Does recall automation need patient consent?
Texting needs consent and registration: HighLevel says A2P registration is required for SMS to US recipients and sets opt-in rules for the consent wording. Patients with no recorded consent get email and a call instead. Keep records and follow your compliance policy.
Does dental recall need the HIPAA add-on?
Usually. HighLevel says accounts are not HIPAA compliant by default, and a recall list holds patients and care dates, so most practices use a HIPAA-enabled account with a signed BAA ($297 a month at the time of writing). Whether a generic reminder is protected information is a question for your healthcare attorney; see is GoHighLevel HIPAA compliant.
Can you build dental hygiene recall automation for my practice?
Yes, we build recall automation for dental practices as part of a dental build, including the first list import, the overdue tiers and the year-end benefits workflow. The first call and audit are free and the quote is in writing.