--- title: "Appointment management with an AI agent" description: "What confirming appointments by hand costs, what the slot nobody refilled costs, and what an agent does from the confirmation to the refill." url: https://studiochat.io/blog/turnos-que-nadie-confirma locale: en translations: { es: https://studiochat.io/es/blog/turnos-que-nadie-confirma.md, pt: https://studiochat.io/pt/blog/turnos-que-nadie-confirma.md } site: https://studiochat.io --- [ Back to blog](/blog) It is nine in the morning. Somebody says they cannot make their eleven o'clock. What should happen is simple. The slot goes back on the calendar. Four people asked for an appointment this week and did not get one. Somebody writes to them, in order, until one says yes. What actually happens is that reception is serving three people at the desk, the phone is ringing, and at eleven that slot is empty. ## [The cost isn't the no show, it's the slot nobody refilled](#the-cost-isnt-the-no-show-its-the-slot-nobody-refilled) An appointment nobody showed up for costs more than the appointment is worth, because the resource was reserved and the cost of having it available got paid anyway. But the loss is not produced by the absence. It is produced by two things that happen afterwards. The first is when you found out. If the confirmation goes out two hours ahead, you find out in time to know, not in time to act. If it goes out a day ahead, the slot is refillable. The second, and almost nobody looks at this one, is whether anybody did anything with that information. Because finding out a day ahead and having nobody free to call the waiting list produces exactly the same result as never finding out. ## [The same slot, today and with an agent](#the-same-slot-today-and-with-an-agent) One slot that opens up, end to end * the agent does it * a person does it * always a person the steps of the appointment * the agent does itSend the confirmation early enough WhatsApp Goes out with the lead time needed to refill the slot, not the one that came as the reminder's default. * the agent does itRead the reply and understand it WhatsApp Understands I can't on Thursday but I can on Friday, which is much better data than a cancellation, because it does not free a slot: it moves one. * the agent does itFree the slot on the calendar Calendar Frees it immediately, not when somebody gets to the system in the afternoon. * the agent does itOffer it to the waiting list Waiting list Writes to the list in order, with a short response deadline, and moves to the next when nobody answers. This is the step that by hand never happens. * the agent does itRebook whoever asked for another day Calendar Offers the calendar's real gaps and confirms the new appointment without anybody reading a grid. * the agent does itRecord the appointment for billing Billing Logs what was done and for whom, which is where money gets lost when the day was busy. * always a personDecide whether to charge the no show Billing Charging or waiving a missed appointment is a commercial decision about a relationship. A person makes it. Appointments per month: 300 Minutes of admin per appointment today: 14.0 Hourly cost of whoever runs the calendar: USD 12 Share of appointments left empty: 4% Value of one empty slot: USD 40 Today that is 70 hours a month of admin and 12 appointments left empty. Between the time and the lost slots, USD 1,320 a month. With the agent holding 6 of the 6 steps, 4 hours and USD 66 are left. The difference is USD 1,254 a month, USD 15,048 a year. And 36% of that difference is not time: it is the slots that get filled again because somebody offered them five minutes later. Of what a person still does, the heaviest step is: Decide whether to charge the no show. You set all five numbers. How the minutes split across steps is ours, taken from how it gets done by hand. The modelling assumption: the slot left empty falls in the same proportion as the confirming and the refilling stop depending on somebody having time. The move worth making is switching off only the step that offers the slot to the waiting list, leaving the confirmation on. That is the implementation nearly everybody does, and the number shows why it returns half: confirming produces the data and refilling is what turns it into revenue. This object also has [a page of its own](/appointments-with-an-agent), in case you want to send just that. ## [What the agent does that a person cannot](#what-the-agent-does-that-a-person-cannot) **It writes to the waiting list five minutes later.** Not when there is a gap at the desk. A freed slot has a short shelf life, and that window is exactly the one a busy reception cannot serve. **It reads a reply that is neither yes nor no.** Most real replies are not a confirmation or a cancellation: they are a negotiation about dates. A confirm or cancel button loses that data; an agent resolves it. **It is still there at eight in the evening.** The message saying they cannot make tomorrow arrives after reception closed, and it is the one that leaves the most room to refill. ## [What stays with a person](#what-stays-with-a-person) Deciding whether to charge the no show. It is a commercial decision about a relationship, and in many industries it is the most delicate decision of the month. And the calendar exceptions: the patient who needs an appointment today, the client who has to be fitted in even though there is no room. That is judgment and it does not get written into a rule. ## [How it gets implemented](#how-it-gets-implemented) Three kinds of access and nothing more: reading the calendar ahead of time, writing to it, and a waiting list a system can read. If you have to get one thing in order before starting, it is that list. In many operations it lives in the receptionist's head and in no field, and without it refilling has nobody to offer the slot to. Start with the confirmation alone, for a week, to measure response rate by channel. Then refilling, which is where the return is. And last the billing record, which is the least noticed and recovers the most loose money. ## [What to measure](#what-to-measure) The no show rate moves slowly and depends on things you do not control. It is not the number. The number is: of the slots that were freed, what share got filled again. It starts near zero in almost every operation, because nobody is measuring the gaps that got filled, and it moves fast. And the second: how many hours of lead time the confirmation has today, against how many you need to fill a slot. If the first is smaller than the second, the rest of the project does not matter yet. Frequently asked questions ### What does an AI agent do with appointment management? It sends the confirmation far enough ahead that the slot can still be refilled, reads the reply even when it is I can't on Thursday but I can on Friday, frees the slot on the calendar, offers it to the waiting list in order with a short response deadline, rebooks whoever asked for another day, and records the appointment for billing. ### Why does refilling matter more than confirming? Because confirming only produces the data and refilling turns it into revenue. When somebody frees a slot, it has to be offered to the waiting list within minutes, and that is exactly what a busy team cannot get to at eleven on a Tuesday. The slot stays empty even though demand exists. ### Do we need to change the booking system? No. You need three kinds of access: reading the calendar far enough ahead, writing to it to cancel, move or assign, and having a waiting list somewhere a system can read. That list is what is missing most often: it exists in the receptionist's head and in no field. Share [ X](https://x.com/intent/post?text=The%20slot%20that%20opens%20at%20nine%20and%20stays%20empty%20because%20nobody%20had%20time%20to%20offer%20it&url=https%3A%2F%2Fstudiochat.io%2Fblog%2Fturnos-que-nadie-confirma) [ LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstudiochat.io%2Fblog%2Fturnos-que-nadie-confirma) [ WhatsApp](https://wa.me/?text=The%20slot%20that%20opens%20at%20nine%20and%20stays%20empty%20because%20nobody%20had%20time%20to%20offer%20it%20https%3A%2F%2Fstudiochat.io%2Fblog%2Fturnos-que-nadie-confirma)Copy link Cristian Pereyra Cristian Pereyra · Co-founder · Engineering, StudioChat Want agents like these working for your team? [Talk to us now](https://cal.com/studiochat)