> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hamla.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Cut no-shows with booking reminders
> Confirm a booking the moment it is made, then remind people before they are due. Two jobs, and they need different things from you.
A no-show costs you twice: the empty slot, and the customer who felt bad enough about missing it not to rebook.
Reminders are the cheapest fix in marketing. They are also two separate jobs, and it is worth knowing which is which before you start.
| | When it fires | What it needs |
| ---------------- | --------------------------- | --------------------------------------------- |
| **Confirmation** | The instant someone books | Just a booking connection. Works today. |
| **Reminder** | The day before they are due | Hamla has to know **when** the appointment is |
## The part people get stuck on
A booking connection tells Hamla **who** booked — their name and their email. It does not tell it **when** the appointment is.
That is fine for a confirmation, which goes out immediately. It is not enough for "remind everyone due tomorrow", because nothing in Hamla knows what tomorrow means for that person.
So you send the date. One extra field, once, at the moment your system already knows it.
## What you need
* **A way for bookings to reach Hamla** — a booking connection, a [Hamla form](/how-to/grow-your-list), or your own system through [Hamla Events](/how-to/hamla-events)
* **Email or push**, both on the Free plan. **WhatsApp** needs the Starter plan and is usually the one people actually read for appointments
* **The appointment date**, for the reminder half — see below
## Set it up
### The confirmation
> When someone books an appointment, send them a confirmation with the time and the address
That is the whole thing. It fires off the booking itself, so nothing else is required.
### The reminder
First, make sure the date reaches Hamla. If your booking system, POS or app knows it, send it with the booking:
```json theme={null}
{
"event": "appointment_booked",
"identity": { "phone": "+962790000000" },
"traits": { "appointment_date": "2026-09-14" }
}
```
The first time that trait arrives, Hamla creates a date field for it automatically. Now you can ask for the reminder:
> Every morning, message everyone whose appointment date is within the next day
And a second one, if you want it:
> Also message anyone whose appointment is within the next 3 days, once
## What actually happens
The reminder is not waiting on a timer next to each booking. It runs on a schedule — once a day — and each time it asks *who is due soon?* and messages exactly those people.
That is why it keeps working. Someone who books six weeks out is caught on the right morning without you doing anything, and someone who books tomorrow is caught on the same run.
**Keep re-entry on.** A reminder is a repeating moment — the same customer should be reminded before every appointment, not once ever. Turn on **Can enter again later** so people can be enrolled again.
## Launch it
> Launch the appointment reminder
Confirmation card, your click, live. Then it runs every morning on its own.
## Check on it
> How many people showed up after getting a reminder?
The number that matters is **no-shows**, not messages delivered. If reminders go out and people still miss appointments, the message is landing too late or on a channel they do not check — try moving it earlier, or to WhatsApp.
## Related
How to send the appointment date, and everything else your system knows.
The message that goes out after the appointment happens.
Where reminders fit among the six moments.
More ready-made asks.