Appointment Reminder
It's 3:30 and tomorrow's schedule is printed on the desk, twenty-five names deep. This agent works that list instead of a person: it texts and emails every name off your live schedule, reads what comes back, marks the clean yeses on the appointment, and hands anything ambiguous to a human. When the 9:00 cancels at 7:40, it is already offering that slot down your waitlist in the order you set.
Yours outright — no required subscription.
Every agent is built for your business — your systems, your approval chain, your way of working. We scope it on the call.
If this sounds too technical, don't worry. We take care of everything for you.
- Private VPS deployment. This agent runs on a server that belongs to you, not a shared cloud tenant. The message threads, the numbers, and the confirmation history live there too, under your keys.
- A technician agent alongside it. Every hire ships as a pair: the Appointment Reminder Agent working tomorrow's list, and a VPS-technician agent on the same box keeping it patched, backed up, and monitored. You're not hiring one thing, you're hiring a small team of two.
- A connection to the schedule itself. It reminds off the system of record your front desk already works out of, not off a day sheet somebody printed at 5pm. How tight the window is between a change at the counter and what goes out depends on how live that connection can be, and we size that honestly with you at setup.
- Reply handling with a human lane. A clean yes or no gets marked on the appointment. "Yeah I think so," "my wife handles the calendar," a reply in another language, or a reply about the wrong appointment when someone has three on the books routes to a person instead of being scored as confirmed.
- Waitlist rules written before it goes live. Who's eligible, in what order, how much notice counts as reachable, and which appointment types can drop into which gap. It fills by the rules you wrote, not by judgment — so a 90-minute hole doesn't get a 20-minute visit unless you said it could.
- Security hardening. Private VPN, firewall, and encryption configured on your server before it ever messages a patient or a customer.
- A live walkthrough, then 14 days of priority support — we show you both agents so nothing is a black box, then tune the send timing, the reply rules, and the waitlist order against your real schedule for two weeks. After that we remove our own access.
Not sure it fits? Check fit in 90 seconds in the free assessment chat.
Who this is for
- You're a four-op practice where one person spends the last hour of every day on confirmation calls, and still walks in the next morning to two chairs sitting empty at 9:00.
- You run five trucks, the dispatcher confirms tomorrow's stops by phone, and a tech still rolls to a house where nobody's home, the gate code changed, or the dog wasn't put away.
- You have a waitlist in name only — an ASAP tab, a spreadsheet, sticky notes on a monitor — and by the time anyone has a free minute to work it, the open slot is already gone.
- You bought software with reminders built in and nobody ever turned them on, or they fire off a stale schedule and text people about an appointment that moved at the counter last week.
How it earns trust
The failure mode of AI on reminders isn't that a message goes wrong — a front desk gets one wrong too. It's that you find out at 9:00, from an empty chair, with nothing to read. This one bets the other way: every message it sent, and every one it decided not to send, is on the page by morning.
The thread is stamped on the appointment
The exact text, the number or address it went to, the timestamp, the delivery receipt, and whatever came back, logged against that appointment on your own server. When a patient says nobody told them, you open the appointment and read the thread instead of arguing about it.
One morning sheet, four columns
Reminded, confirmed, no reply, declined — plus the backfill trail for every gap: who was offered the slot, in what order, at what time, and who took it. Your confirmation rate and your still-empty 9:00 sit on the same page, so the distance between them is yours to see, not something you have to go asking about.
A list of what it didn't send
Every message it held back and why: no consent on file, outside quiet hours, opted out, bad number, appointment changed after the run. That column is where drift shows up first. It's how you find the dead numbers and the stale schedule yourself, before a customer finds them for you.
The 14-day support window after delivery exists for exactly this — the first week of the not-sent list usually says more about your customer file than about the agent.
Pairs well with
These share a workflow with this role. Tick any to add them to your setup.
We had two holes in the schedule yesterday and nobody knew until 9am.
By 7:45 the gap is in writing and the offer is already going down your waitlist in the order you set, while somebody is still unlocking the front door. The honest limit: it can only offer. People who got in somewhere else weeks ago are still sitting on your list and never told you, so some mornings the slot still goes empty. What changes is that you know at 7:45 instead of 9:00, and every name got asked in order.
Sarah spends the last hour of every day making confirmation calls.
It takes the text and email pass off her completely and comes back with four columns: reminded, confirmed, no reply, declined. What's left is the short list — the people who never replied, and the ones who only ever answer a ringing phone. It can't call, and it can't tell a dead number or a landline from a good mobile, so it will keep messaging those until someone fixes the file. Ten minutes of calls that matter instead of forty of dialing everyone.
They confirmed and still didn't show.
This does not fix that, and it will report a confirmation rate higher than your show rate, because replying "C" costs the patient nothing. Read confirmed as "answered the text," not "will be in the chair." It also misreads some of the in-between replies — a confident-sounding maybe can slip through as a yes. That's why both numbers land on the same morning sheet instead of just the flattering one.
By the time we get to the waitlist the slot's already gone.
It offers the gap the minute the cancellation lands, in your order, without anyone dialing down a spreadsheet. It never bumps a booked customer to seat someone off the waitlist, and it never confirms the move by itself — it drafts the change and either a rule you wrote or a person clicks the last step. Waitlists decay, so expect a share of offers to go to people who are long gone. The list gets shorter and more honest the more it's worked.
I don't want it texting patients things it shouldn't, or moving appointments on me.
It never cancels, moves, or deletes an appointment on its own. It never messages someone without consent on file, never outside the quiet-hours window you set in the customer's local time, and never again after STOP — that one is permanent and no rule, no campaign, and no badly needed slot overrides it. Reminders carry date, time, place, provider, and how to reply, and nothing else: no procedure name, no diagnosis, no balance owed, no promo line. It never takes a card number, a deposit, or a no-show fee over text, and never negotiates one.
What's covered under the $1,997 setup, and what isn't?
One company, one system of record, one approval chain, plus the waitlist rules and the quiet-hours window set with you before anything sends. Typically about seven days from kickoff to it working tomorrow's schedule. You own the server, the code, and the keys; we keep the recipe we used to cook it. Multiple locations, or providers with genuinely different reminder policies, get scoped on the 15-minute call.
Hiring more than one? A department on tap — the subscription puts a build team behind every request, agent after agent.