home / use cases / scheduling and calendar / appointment-reminders

Appointment reminders that cut no-shows

Every morning an Aivell reads your appointment calendar a few days ahead and sends each customer a reminder — then actually handles the replies. A request to move becomes a rebooking, a cancellation frees the slot and alerts your desk. It runs on schedule, onboard, with your customer list never leaving the building.

Watch the demo

starts when: The Schedule fires each morning and scans the days ahead

The problem

Every empty chair had a name on it. The physio slot that stayed vacant at 10:15, the consultation nobody turned up for — each no-show is prepared time, blocked staff and a room doing nothing, at a cost of roughly $200 per hour of lost productivity. And most of them were not malice; someone just forgot.

Reminders fix forgetting, but sending them by hand is its own daily chore — and the reminder-service subscriptions that automate it want your whole client list uploaded first. For a clinic, a physio practice or a legal office, that list is exactly the thing you cannot hand over.

How your Aivell does it

The chore runs on the Schedule, every morning, without anyone pressing anything:

  1. The calendar is read a few days ahead. Whatever is booked right now is what gets reminded — moved appointments included, cancelled ones excluded.
  2. Each customer gets a personal reminder. Date, time, address, what to bring — written fresh for each appointment, in the customer’s language, not a template blast.
  3. A second nudge lands the day before. Two touches is the pattern that moves the no-show numbers; both are noted in the calendar event so the desk sees what was sent.
  4. Replies are handled, not collected. “Can we move it” becomes a rebooking with new slots offered; “I have to cancel” frees the slot and alerts Elena immediately so someone from the waiting list gets the time.
  5. The risky ones get flagged. A first-time client who ignored both reminders is exactly who fails to appear — the chore warns Elena that morning so she can decide whether to call.

Guardrails keep it boring in the right way: it can only touch the appointments calendar, and it can only write to the person whose appointment it is. The rest — timing, tone, who gets warned — is plain language you adjust as you learn what works.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · remind before appointments ● active

every morning at 7, read the appointments calendar three days ahead

three days out, send a reminder — date, time, address, what to bring

the day before, send a short second nudge

note in the event which reminders went out

a reply asking to move? offer the next two free slots and rebook

a cancellation? free the slot and email Elena so she can fill it

first-time clients who answered neither reminder — warn Elena that morning

appointments marked private get no reminder at all

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule runs the chore every morning
Calendar reads appointments, moves the rebooked ones
Email sends reminders, understands the replies

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Calendar May move or cancel events only in the appointments calendar; every other calendar on the box is read-only.
Email Writes only to the address attached to the appointment, plus Elena. Bulk mail and any other recipient are blocked.

Questions, answered.

What happens when a patient replies "can we do next week instead"? +

The reminder is not a dead-end notification — it is an email from a colleague who can act. Your Aivell reads the reply, finds the next free slots, offers them, and moves the booking once the patient picks. Elena only hears about it in the log.

Can reminders go out at different times for different appointment types? +

Yes — timing is just a sentence in the chore. Three days and one day before is a common pattern; surgeries might get a week's notice with prep instructions, while a quick fitting gets one nudge the evening before.

Is my patient list shared with a reminder service? +

No, and that is the difference. Cloud reminder tools hold your entire client base on their servers. Here the calendar, the addresses and the message writing all stay on the box in your office — nothing about who visits you leaves the network.

Do reminders respect what's actually in the calendar right now? +

Yes. The chore reads the live calendar each morning, so an appointment moved yesterday gets its reminder for the new time, and a deleted one gets silence — no ghost reminders for slots that no longer exist.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee