Fixed quote after a free call

Hygiene recall, reactivation and treatment-plan follow-up

Recall intervals are agreed in the treatment room, but the reminder depends on the right date being recorded and the right message going out. We build a workflow that reads recall due dates from your practice system, sends reminders in the patient's preferred channel, follows up once or twice and hands lapsed patients and unbooked treatment plans to a person for a call. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why dental recalls slip

Recall is where a practice keeps its hygiene book full, and it is also where patients quietly drop out. The first reminder goes out, the patient means to book, and if nobody follows up they simply fall out of the cycle.

Treatment plans go quiet in the same way. A patient leaves with a written estimate and a promise to think about it, and without a consistent, gentle follow-up the questions about cost, insurance or options never get answered.

Intervals differ by patient. In the UK, NICE guidance sets adult intervals between 3 and 24 months based on risk, and no more than 12 months for under-18s, so a reminder workflow has to follow the interval the dentist set, not a fixed six months.

What we build

What our dental recall system includes

Recall list from your PMS

Patients due or overdue, read from the recall dates your practice system already holds, with no separate spreadsheet to maintain.

Reminders by preferred channel

Text, email or both, following the contact preferences recorded for each patient, with a booking link or call-back option.

Polite second and third reminders

A short sequence with clear stop rules, then a hand-off to a person instead of endless messages.

Lapsed patient list

Patients who did not respond go to a call list for a personal phone call, ordered by how long they have been overdue.

Treatment-plan follow-up

A check-in after the visit for unbooked plans, with questions about cost or insurance routed to the treatment coordinator.

Monthly summary

One email with recalls sent, booked and outstanding, so the practice manager can see the cycle at a glance.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Due list built

    Every night the workflow reads recall due dates and unbooked treatment plans from the practice system.

  2. 02 Automated

    Reminder sent

    Patients get an approved reminder with a booking link in their preferred channel.

  3. 03 Automated

    Follow-up

    No booking after a set number of days triggers one or two polite reminders, then stops.

  4. 04 Staff review

    Personal call

    Lapsed patients and plan questions go to the front desk or treatment coordinator to call.

  5. 05 Dentist or owner decides

    Clinical decisions

    Recall intervals and treatment options are set and changed only by the dentist or hygienist.

How it behaves

How recall reminders behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the patient sees

  • A reminder when their recall is due, in the channel they prefer
  • A booking link or a call-back option
  • At most two polite follow-ups, then a personal call instead of more messages

What staff see

  • A daily lapsed-patient call list ordered by how overdue each patient is
  • Unbooked treatment plans with any questions the patient asked
  • A monthly summary of recalls sent, booked and outstanding

What the automation does

  • Reads recall dates and unbooked plans every night
  • Applies channel preferences, quiet hours and opt-outs
  • Stops the sequence as soon as an appointment appears

Edge cases and fallbacks

Patient books by phone mid-sequence
The nightly check sees the appointment and stops any further reminders.
No mobile or email on file
The patient goes straight to the call list.
Recall date missing or odd
Flagged for staff to fix; no reminder is guessed.
Patient has moved away or died
Staff mark the record and the workflow excludes it from then on.
Practice system unavailable
That night's run is skipped and retried, never sent from stale data.

Architecture

Recall and reactivation for a dental practice at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Practice system Recall due dates n8n schedule Nightly check Contact rules Channel, opt-outs Reminders Text or email Front desk Lapsed call list Recall log Sent and booked
  • Input
  • Logic and services
  • Output
  • People
  • Data

How it flows

  1. 1 Each night the workflow reads which patients are due or overdue for recall, and which treatment plans are unbooked.
  2. 2 Contact rules apply each patient's channel preference, opt-outs and quiet hours.
  3. 3 Reminders go out with a booking link; one or two follow-ups are sent if nothing is booked.
  4. 4 Patients who still have not booked go to a call list for a person, and every step is logged.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Hygiene recall, reactivation & treatment-plan follow-up project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How recalls are recorded today, recall types, intervals, contact preferences and current reminder wording.

  2. 02

    Design

    2 to 3 days

    Sequence and stop rules, channels, call-list format and what the monthly summary shows.

  3. 03

    Build

    1 to 2 weeks

    Read access to the practice system, n8n schedule, messages, call list and log.

  4. 04

    Shadow run

    About 1 week

    The list is built daily but messages go to a test inbox so staff can check every patient on it.

  5. 05

    Launch

    1 to 2 days

    Start with one recall type, then add the rest once the team is comfortable.

  6. 06

    Support

    Ongoing

    Stabilization window, then optional monthly care for new recall types and wording.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Open Dental API (Recalls, Appointments, Patients) Dentally API Dentrix or Ascend through an authorised API Exchange vendor Twilio SMS Gmail, Outlook or your email provider

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, wording, data flows and the written specification.

    $200 – $400

  • Build

    The n8n workflow, logic, AI step and error handling.

    $500 – $1,300

  • Integrations

    Practice system, phone or messaging and alert channels.

    $150 – $400

  • Testing and shadow run

    QA against acceptance criteria and a side-by-side run with your team.

    $100 – $250

  • Launch and training

    Switch-on, team walkthrough and run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Treatment-plan follow-up can be added to the same workflow. Messaging and n8n costs are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing). US A2P 10DLC registration fees also apply.
  • n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: recall intervals follow the dentist

NICE guidance sets the shortest interval between oral health reviews at 3 months and the longest at 24 months for adults and 12 months for under-18s. Reminders follow whatever interval the clinician recorded.

Source: www.nice.org.uk

US: reminders vs marketing texts

The FCC healthcare exemption covers purposes such as appointment reminders and wellness checkups, with frequency and length limits. Promotions such as whitening offers are marketing and need prior express written consent.

Source: www.law.cornell.edu

UK: marketing emails and texts

Under PECR, unsolicited marketing by electronic mail (which includes texts) needs consent, or the soft opt-in conditions, with a simple way to refuse in every message. Pure recall reminders are kept free of marketing.

Source: www.legislation.gov.uk

EU and UK: health data

Recall data is health data, a special category under Article 9 GDPR (and UK GDPR), so access is limited to what the workflow needs and processors are under contract.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Hygiene recall, reactivation & treatment-plan follow-up questions, answered.

Open Dental has a REST API with recall, appointment and patient resources, and Dentally has an API with patients, appointments and availability. Dentrix and Ascend connect through Henry Schein One's API Exchange of authorised vendors. For other systems we check what export or integration route the vendor offers before quoting.

No. We agree a short sequence (a reminder and up to two follow-ups) with clear stop rules, respect quiet hours and opt-outs, and hand anyone who has not responded to a person instead of messaging again.

Yes. Unbooked plans get a friendly check-in that offers a call with the treatment coordinator. The message never discusses clinical details; questions about options or cost go to a person.

Never. The interval is a clinical decision recorded by the dentist or hygienist. The workflow only reads it.

Offers are marketing. In the US that needs prior express written consent for texts, and in the UK it needs consent or the soft opt-in under PECR. We keep promotional messages in a separate flow that only reaches patients who agreed.

Recalls due, reminders sent, bookings made from reminders, patients moved to the call list and treatment plans booked after follow-up. We set up the log so you can compare month to month.

Free 20-minute call

Want this for your dental practice?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call