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

Every new-patient inquiry answered in the same minute.

A new patient who fills in your website form is usually filling in two or three other clinics' forms the same evening. The practice that replies first, with a real time to come in, is the one they pick. New-patient follow-up answers form, chat and message inquiries straight away, collects what your team needs, and offers a booking instead of a callback promise.

Covers
Forms, chat, messages
Replies
In the same minute
Collects
What your team needs first
Ends with
A booked time or a person

Where the practice loses patients.

New-patient follow-up for Toronto dental clinics. Website, chat and message inquiries answered in the same minute, with a booking instead of a callback.

  • Website forms wait in an inbox

    They arrive while the desk is with patients and get answered hours later, after the person has already booked somewhere that replied.

  • Messages come in from everywhere

    Website, Google Business Profile, Instagram, Facebook. Nobody owns all of them, so some are never answered at all.

  • A callback promise is not a booking

    "We'll call you tomorrow" gives the patient a whole evening to keep shopping.

  • First visits start with paperwork

    Details collected on the phone get typed in again at the desk, and the first appointment starts late.

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

    List every place inquiries come from

    Forms, chat, Google, social messages. Each one gets routed to one place so nothing sits unanswered.

  2. 02

    Write the first reply

    Warm, short, from your practice. It confirms the inquiry and asks only what your team needs before a first visit.

  3. 03

    Offer a time, not a callback

    Where your booking system allows it, the patient picks a slot. Where it does not, the details go to the desk flagged as a new patient.

  4. 04

    Follow up if they go quiet

    A short, spaced reminder sequence that stops as soon as they reply or book.

  5. 05

    Hand the record to your team

    Everything collected lands where your desk already works, so the first visit starts on time.

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.

  • A reply from your practice within the minute: thanks, a couple of short questions, and a way to pick a time. It does not pretend to be a staff member.

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.