Skip to content

The whole of it, with nothing hidden.

Most software pages describe a product that does not exist yet. Everything on this page is running today, in code you could read. The one section that is not says so in its heading, and it is near the bottom where you can find it rather than at the end of a paragraph where you cannot.

The appointment book

A practice that has never paid us anything can run its entire diary here. That is not a trial and it does not expire, because scheduling costs us almost nothing to run — it sends no messages.

Book, move, cancel
A day at a time, one column per practitioner, with the gaps in it shown as gaps.
Kinds of appointment
A name and a length, so booking is picking one rather than typing 45 every time.
Working hours
A normal week per practitioner, lunch breaks included. A description, never a rule: booking outside them says so and goes ahead.
Time off
Holidays block a day. There is no reason field, on purpose.
Double-booking
Asked about rather than refused. Two chairs and a squeezed-in re-check are your business, and the override is recorded.
Who moved it
Every booking, move and cancellation is written down against the appointment and the person who did it.
The same person twice
A number already on file is recognised as somebody you know, rather than becoming a second file.
Staff only
There is no way for a client to book themselves in. That is deliberate, and it stays that way until a plan includes reminders.

Reading a schedule you already keep

Most practices already have a scheduler they are not going to leave, and should not have to. It reads yours. It never asks for the password to it, and it never writes to it.

Calendar feed
A private link from your scheduling software, read on a loop.
Spreadsheet import
It works out the delimiter, the header row, the date and clock formats, and tells you which column it read as what.
Square Appointments
A real API connection, with its own tested status mapping.
Typed in by hand
For a practice with nothing to connect yet.
Rows it cannot read
Named by the line number your spreadsheet shows, with the reason, rather than silently dropped.
A client with no contact details
Still gets their appointment kept. A missing client never loses you the slot.
Several sites
Each with its own time zone, hours and settings.
Re-read on demand
Pull the schedule again whenever you want from Settings.

A hygienist runs twenty minutes over at half past nine. By noon the waiting room holds four people who were all told ten o'clock.

That is the whole product. Everything below is in service of getting that one sentence right, and getting it to the right six people.

Without anybody pressing anything

Drift

It notices by itself.

When appointments have been starting late in a row Drift says so, with how sure it is, and waits for somebody at the desk to agree. It will not send on a hunch, and it knows when it has no way of telling — a calendar feed that never reports a finished appointment is never treated as if it had.

The arithmetic of a slipping day

A reminder tool knows what time an appointment was booked for. Knowing what time it will actually start is a different problem, and this is the part of the product that solves it.

The cascade
One appointment over pushes everyone behind it, through gaps, breaks and back-to-back pairs.
Static or catching up
Choose whether a delay stays put or decays as the practitioner pulls the day back, at a rate you set.
Drift
Our name for the automatic detection: it watches how the day is really running and speaks up, with a confidence, and waits for a yes.
It knows when it cannot tell
A calendar feed that never reports a finished appointment is not treated as if it had.
Turnaround time
Minutes a practitioner needs between appointments, per person.
Parallel appointments
Two chairs, two rooms, two lanes — tracked separately.
Early finishes
A day running ahead is worked out too, not just a late one.
Cancellations absorb delay
A cancelled slot gives the time back to the day.

What the message actually says

“Running late” tells somebody nothing they can act on. A time to leave the house by does. Every message is built around the one number that changes what the person does next.

Delay notifications
The new start time and a time to arrive by, which is the number that actually helps.
Reminders
The message before the appointment, for practices with no reminder tool.
Updates
A second message only when the time has moved again by enough to matter.
Back on time
When a practice recovers, the people told get told again.
English and Spanish
Every message exists in both and clients get the one they are marked for.
Your own wording
Edit any template, with the character and segment count as you type.
Only who it matters to
A thirty-to-one-hundred-and-eighty-minute window, and a threshold you set.
Email as a fallback
For the messages that can be planned ahead.

“We're running about 30 minutes behind. You're still fine to leave at 10:40.”

It is the difference between a message somebody reads and a message somebody acts on, and it is why the expected start time has to be right rather than roughly right.

When somebody texts back

People reply to texts. A number that ignores them teaches them the practice is not listening, so every reply lands on one page at the desk and the ones that can be answered are.

Confirm
Reply 1. The desk sees who is still coming.
Reschedule
Reply 2, and the practice gets asked to deal with it.
On my way
A check-in before arrival.
STOP and START
Opt out immediately and permanently, or opt back in.
HELP
Answered automatically, because the carriers require it.
Anything else
Acknowledged and put in front of a human rather than parsed into a guess.

The brakes

Every one of these exists because a wrong message to a patient costs more than a missing one. They are not settings we added for completeness — each is here because of a specific way this could go wrong.

Take it back
Thirty seconds between planning a message and sending it.
A kill switch
Stops everything for a site or the whole practice. Any role can reach it.
Quiet hours
Nothing sends outside the hours you set, except a reply to a client.
A daily cap
A hard limit on how many messages one appointment can generate.
Preview mode
See every message it would send, written out, without one leaving the building.
Three locks on real sending
A development machine cannot text a patient. Any one of the three is enough.

The worst thing this software could do is text two hundred patients something wrong at ten at night.

Which is why the undo window, the quiet hours, the daily cap and the kill switch all exist, and why none of them can be turned off by accident.

Health information

Built in from the first line rather than retro-fitted, because retro-fitting this does not work.

Messages say nothing clinical
No treatment, no procedure, no practitioner name.
Three-way consent
Agreed, said no, and never asked — recorded per client and per channel, because the middle one is not the last one.
Encrypted at rest
Names, numbers, message bodies and raw payloads, with a key per practice.
First names only on screen
Staff never see more of a client than they need.
Look up without listing
Find a client by number without a browsable list of everybody.
An audit log
Who did what and when, with no client details inside the record.
Erase a client
Their details go for good; the appointment history stays, with nobody attached.
Retention that runs itself
Old message content clears on the schedule you set.

Knowing how it went

Measured from what actually happened, not from a counter somebody remembered to increment.

How late you really ran
Real start times against booked times, by practitioner.
What was sent
And what was held back, taken back, or failed, with reasons.
Delivery outcomes
What the carrier said happened to each message.
Reply rates
How many people confirm, move it, or opt out.
Every figure carries its denominator
No percentage without the count it came from.

Running the practice

The unglamorous half that decides whether software survives contact with a front desk.

Four roles
Owner, admin, front desk and practitioner, each seeing only what they should.
Two-factor
Required for anybody who can see client contact details.
A practitioner sees their own day
And nobody else’s.
Installs on a phone
Add it to the home screen and it opens like an app.
Sign yourself up
Create the practice and see your own day without talking to anybody.
Add your own staff
Without asking us.

Plans and add-ons

Both paid plans take add-ons, charged monthly alongside the plan. Buy them when you need them and drop them when you do not.

Free

$0forever

Scheduling for your whole practice. Sends nothing, so there is nothing to meter.

Messaging

$48a month

Up to 4 practitioners, 1 site, 2,000 messages a month.

Clinical

$120a month

Up to 30 staff, 5 locations, 6,000 messages a month, and a business associate agreement.

Add-ons

An extra practitioner or staff member

On either paid plan, as many as you need.

$9 a month

An extra site

Its own time zone, hours, settings and kill switch.

$19 a month

Another 1,000 messages a month

Added to your monthly allowance. Stack as many as you want.

$15 a month

Nothing is charged without telling you first, and going over an allowance never silently sends more than you have paid for — it tells the desk instead.

Not built yet

Every product page has a list like this. Most of them keep it in the sales call. We would rather you ruled us out on a Tuesday afternoon than found out in week three.

  • Client-side booking — practitioners and staff only for now
  • Taking payment — plans are not billed yet
  • The hardware tie-in for automatic delays
  • Push notifications on the phone app
  • Connections beyond calendar feeds, spreadsheets and Square

Find out what your real start times are

Set the practice up, point it at the schedule you already keep, and look at a week of your own days. Most practices are surprised by what they see. Nothing reaches a client until you decide it should, and finding out costs nothing.