Skip to content
Braav Labs — AI front desks and follow-up for Toronto clinics.
Dental · Recall

Recall that runs on a schedule, not on spare time.

Every practice has a list of patients who are due or overdue for a cleaning. Working that list is real revenue, and it is also the first task to slip when the desk is busy. Automated recall contacts those patients on a set schedule by text and email, stops the moment someone replies or books, and writes the result back so your team knows who is coming in.

Contacts
Due and overdue patients
Channels
Text and email
Stops
The moment they reply or book
Records
Written back for your team

Where the practice loses patients.

Dental recall automation for Toronto clinics. Due and overdue patients contacted by text and email on a set schedule, stopping once they book or reply.

  • The recall list only moves when someone has time

    It lives in the practice software and gets worked in the quiet hours. In a busy month there are no quiet hours.

  • Lapsed patients drift away quietly

    A patient who missed one cleaning is easy to bring back. A patient who has not heard from you in two years has probably found another dentist.

  • Open hygiene time is hard to fill at short notice

    A cancellation this afternoon needs a list of people who want an earlier slot, worked right away. By the time someone gets to it, the slot has passed.

  • Manual messages are uneven

    Some patients get three reminders and some get none, depending on who was at the desk that week.

What we set up, step by step.

Built on the tools the practice already uses, in the practice's name. Anything clinical goes to a person.

  1. 01

    Pull the list your software already has

    Due, overdue and lapsed patients, grouped by how long it has been. We only use what recall needs.

  2. 02

    Write the messages with you

    Plain, friendly, in your practice's voice, with one clear way to book. Nothing clinical, nothing that sounds like a sales push.

  3. 03

    Set the cadence and the stop rules

    How many messages, how far apart, and what stops the sequence: a reply, a booking, an opt-out, or a staff note.

  4. 04

    Add a short-notice list

    Patients who said they would take an earlier slot get offered cancellations in order. The first to confirm gets it.

  5. 05

    Report what came back

    Who replied, who booked, who asked to stop. Your team sees it without opening another tool.

Out of scope, deliberately

Nothing clinical. Ever.

These systems handle scheduling, access and logistics. They do not answer clinical questions, assess symptoms, triage urgency or give advice of any kind. A caller in pain reaches the practice, not a model. That boundary is written into the build, not added as a disclaimer, and we will decline work that asks us to move it.

Our experience here

Braav Labs is currently building the new-patient journey for a dental practice in Scarborough, Ontario. That project is in build, not complete, and the practice has not yet approved public attribution, so it is presented on this site without their name. It is the only dental engagement to date.

Questions practices ask.

  • Not if the cadence is sensible and it stops the moment someone responds. Every message has an easy way to opt out, and opt-outs are respected everywhere.

Want this looked at against how your practice actually runs?

Get my free audit

How an engagement runs.

The same five steps whatever we are building, so you always know which one you are in.

Pricing
Fixed price, quoted after a scope call
You have the number before anything is built. Nothing is billed by the hour.
Timeline
A date at quote time
Stated as a commitment, not an estimate that drifts once work starts.
Ownership
Everything stays in your name
Domains, hosting, inboxes and every account, on your billing, documented.
  1. 01

    Scope call

    Twenty minutes on how inquiries reach you today. No deck, no discovery package.

  2. 02

    Written scope and a fixed quote

    What gets built, when it lands, what it costs. Fixed before anything starts.

  3. 03

    Build and review

    You see it working on your own content, not a screenshot of it working.

  4. 04

    Launch and handover

    Accounts in your name, a written record of what runs where, a walkthrough.

  5. 05

    Support, if you want it

    A separate decision, made after something is already running.