No-show tracking: measuring and reducing missed appointments

Tuesday morning, 9:10. The front-desk coordinator at a physiotherapy clinic opens the day's list: fourteen appointments, two of them first-time patients. By half past eleven, three rows are still marked "scheduled." Nobody arrived, nobody called, nobody cancelled. The day rolls on, nobody touches those three rows, and at closing time they sit exactly where they were. Two weeks later, when the owner asks why utilisation dropped, there is no number to point at — only a shared impression that "a lot of people didn't turn up lately." The figures here describe one illustrative day. The real problem is not their size; it is that none of them was ever recorded.

This article starts by separating a no-show from a cancellation and a reschedule, then works through the formula and how to build its denominator. After that come the appointment statuses that make the number trustworthy, the segments worth reading it in, the four root causes of non-attendance, a reminder schedule, why easy cancellation helps, how to handle repeat offenders, and how to prove that any of it worked. Frequently asked questions close the piece.

What counts as a no-show, and how is it different from a cancellation?

A no-show is a customer who does not attend at the booked time and gave no notice. The weight of that definition sits in the second half: the absence of notice. A customer who calls two days ahead leaves you room — the slot can be resold, offered to someone on the waiting list, or used to reshuffle the team's day. A customer who simply does not appear burns capacity. Staff waited, a room or a video room was held, and nothing was produced in return.

That is why four outcomes that look alike in the calendar have to be counted separately:

• Completed: the appointment happened and its outcome was logged.
• Customer cancellation: notice was given; the slot was recovered, or could have been.
• Provider cancellation: the cancellation came from your side. That is an operations issue, not customer behaviour, and it does not belong in the no-show rate.
• No-show: no notice, no attendance.

Rescheduling sits in its own category and is usually good news: the customer still wants the relationship and is only moving the date. Count reschedules as no-shows and you end up punishing your own reminder system, because a well-built reminder chain converts part of your no-shows into reschedules. That conversion is precisely the point of measuring — turning a silent loss into a signal you can act on.

Which formula gives you the no-show rate?

The basic formula is straightforward: no-shows in a period divided by the appointments that were supposed to happen in that period. The difficulty lives in the denominator. Leave provider-side cancellations in it and you flatter your own rate with your own cancellations. Strip customer cancellations out entirely and you lose the ability to see reminders working, because a no-show converted into a cancellation disappears from the denominator too. In practice, keeping two numbers is healthier: a non-attendance rate that counts only unannounced absences, and a lost-slot rate that adds cancellations made inside the last twenty-four hours. The first measures customer behaviour; the second measures capacity you could not refill.

The second decision is the period. Weekly readings swing wildly — one bank holiday distorts the whole line. Monthly readings warn you too late. For most teams a rolling four-week average alongside a monthly snapshot works: the rolling figure carries the trend, the snapshot carries the report. In B2B sales the same reality is usually tracked from its positive side, as the percentage of booked meetings that actually happen; the mechanics of that meeting show rate are worth borrowing. It is the same fact viewed from either end, so pick whichever one your team already says out loud.

Which statuses must be recorded for the number to mean anything?

Measurement almost never collapses at the formula; it collapses at data discipline. As long as a missed appointment stays "scheduled" on screen, it appears in no report at all — it drifts into the past and quietly looks like something that happened. So closing statuses have to be mandatory: by end of day, every appointment should be completed, no-show, cancelled or rescheduled.

The only real obstacle is effort. If marking the outcome feels like extra paperwork, staff skip it, and skipped records make the data lie. Ways to cut that burden are covered in the piece on reducing CRM data entry, but the rule for appointments is narrow: closing a record should take one tap, without leaving the list.

Field teams face a second trap. An engineer drives out, nobody answers the door, and by the time they are back at the office the record never gets updated. The wider the gap between the event and the entry, the worse the data — which is why the appointment's fate has to be closed on the spot, from a phone. The habits described under using CRM on mobile feed straight into measurement quality here.

On the Rocketly side, No-show Tracking accumulates those closures on the customer record: it shows a person's past no-show count alongside their total appointments. A single day's mark stops being a note and becomes a history that is sitting there the next time someone books that person in.

Which breakdowns should you read the rate in?

A headline no-show rate is a thermometer: it tells you there is a fever, not where it came from. Decisions come out of segments, and five of them cover most businesses.

• Channel: a slot the customer picked on your booking page behaves differently from one agreed over the phone. Self-selected times usually hold better, because they were chosen against the customer's own calendar.
• First visit vs returning customer: non-attendance is always higher on first contact, where there is no relationship to anchor the commitment.
• Lead time: a slot three weeks out does not carry the same risk as tomorrow's. Long lead times feed both forgetting and second thoughts.
• Day and time band: Monday morning and late Friday afternoon rarely behave the same way.
• Host or location: if the same service shows different rates across branches, the problem is in the process, not the customers.

The logic is the same one that governs operational metrics generally: an average wait time means nothing as a single figure and everything when split by hour. You can lift that hour-by-hour framing straight out of call queue metrics and apply it to bookings. In Rocketly, Booking Analytics shows which days and time bands fill up, which slots attract no demand at all, and what share of bookings end in cancellation — so you narrow or widen availability against real demand rather than a hunch.

Why do customers not turn up? Four root causes

Four very different stories hide behind non-attendance, and each needs a different fix.

Forgetting. The most common and the cheapest to solve. If nothing was written into the customer's own calendar when they booked, you have outsourced the appointment to human memory. Reminders and calendar entries fix this.

Unclear value. If the customer cannot say what attending gets them, that hour is easily bought by something else. For demos and advisory sessions in particular, sending the agenda in advance changes attendance noticeably.

Obstacles. Traffic, parking, school pickup, a video link that will not open. These are friction problems, not intent problems, and most of them are solved by two extra lines in the reminder: directions, parking notes, the join link.

Awkwardness. The customer no longer wants to come but finds cancelling effortful or embarrassing, so they choose silence. This group is not fixed by more reminders; it is fixed by easier cancellation.

You cannot guess which cause dominates in your business — you have to ask. A one-question follow-up sent the next day works on the same logic as any satisfaction survey and can sit inside the setup you already use for measuring customer satisfaction. Four weeks later you have a distribution instead of an opinion.

When, how often and through which channel should reminders go out?

A reminder's job is not only to remind. It is to give the customer a chance to tell you they cannot make it. A well-built chain converts some no-shows into cancellations and some cancellations into reschedules. The schedule below is a solid starting point for most appointment types.

Timing	Channel	Purpose	Signal to watch
At booking	Confirmation email plus calendar invite	Get the slot into the customer's own calendar	Invite acceptance rate
48-72 hours before	Email	Open room for an early cancellation and save the slot	Reschedule and cancellation rate
24 hours before	Email and in-app notification	Ask for confirmation	Confirmation click rate
1-2 hours before	Short reminder	Clear last obstacles: travel, parking, join link	Same-day cancellations
10 minutes after the slot	Phone call	Rebook the missed appointment the same day	Recovered appointments

More touches are not automatically better. Past three or four, you manufacture notification blindness and customers stop opening anything you send. For chain design, channel choice and message patterns, the article on appointment reminder automation lays out a fuller framework.

None of this survives being run by hand. In Rocketly, Automatic Reminders send a notification and an email to the relevant person 24 hours and 1 hour before the appointment, while Guest Reminder Emails do the same for visitors who booked through your public page and can be switched off with a single toggle. Where no calendar is connected, the Calendar Invite (.ics) takes over: the customer receives an invite with an .ics attachment, gets an update if the appointment moves, and a cancellation notice if it is called off. The booking then occupies space in the customer's calendar, not only in yours.

Why does making confirmation and cancellation easy lower no-shows?

Making cancellation hard feels intuitively right: if they cannot cancel, they will come. The opposite happens. A customer who finds cancelling hard does not cancel — they simply do not show up, and you learn about the loss at the appointment time, when nothing can be done. Easy cancellation moves the loss earlier, and an early loss is a manageable one.

So the reminder message should carry three actions together: confirm, reschedule, cancel. In Rocketly, One-Click Confirm and Cancel does this through a signed link — the customer confirms, moves or cancels without creating an account or entering a password, and the decision writes straight into the calendar. On your side, the Booking Approval Flow mirrors that control: an incoming request lands as "awaiting approval" rather than being written to the calendar, and if you decline it, the hour reopens for booking.

There is a revenue side to a slot that frees up early. An hour released two days out can go to someone on the waiting list; an hour released at the appointment time is simply gone. The same logic runs through the sales pipeline, where seeing a loss early shortens cycle time and feeds one of the levers behind sales velocity. Treating no-shows as a politeness problem hides that connection.

How should you handle repeat no-shows?

Missing once is an accident; missing a third time is a pattern. When a pattern appears, the move is not punishment but changing the terms. A three-tier approach covers most businesses.

• Tier one: record the history, change nothing else. A visible no-show count on the record is enough for whoever books the next appointment.
• Tier two: add an extra confirmation step for at-risk bookings, and release the slot to the waiting list if confirmation does not come.
• Tier three: change the conditions for repeat offenders — low-demand hours only, a deposit, or a short call before an in-person session.

In Rocketly, No-show Tracking carries the data half of that ladder: it shows a person's past no-show count next to their total appointments, so you notice a risky booking while you are still making the plan. On the conditions side, Booking Rules take over — buffers between appointments, a daily cap, how far ahead bookings can be taken and a minimum notice period all shape which slots get generated. Shortening a long lead time alone can move the rate by a few points.

One caution: before shutting a frequent no-show out entirely, look at what the relationship is worth in total. Two missed appointments from a customer on a regular maintenance plan who renews and refers is a different thing from one missed visit by a one-off booker. Reading the case through customer lifetime value keeps that decision arithmetic rather than emotional.

How do you prove your no-show work actually worked?

These projects usually begin by changing five things at once: new reminder copy, an extra touch, an easy cancel link, a shorter lead time, adjusted opening hours. Four weeks later the rate drops and nobody knows which change did it. So take a baseline first — the last eight to twelve weeks, ideally split by the segments above. Then change one variable at a time and leave at least three or four weeks of observation.

Second, do not look at the rate alone. Log the outcome of the appointments that do happen, because it is entirely possible to raise attendance while lowering the quality of what happens in the room. The discipline described in meeting notes and action tracking helps here; in Rocketly, the Meeting Bot joins online calls and captures the recording and transcript for you, while Appointment Analytics puts today's and this week's appointment counts, the status and outcome mix, and the completion rate into a single strip.

Third, first appointments deserve their own line. A new customer attending their first booking is a threshold much like the first-value moment in a product; relationships that fail to cross it mostly never begin. Borrowing the logic of activation rate and keeping a separate figure — the share of new customers who complete a first appointment — exposes what the headline number hides.

If you want bookings, reminders and no-show history living in one place, you can create a free Rocketly account and set up your appointment calendar.

FAQ

What is a good no-show rate?

It varies so much by sector and appointment type that a universal threshold would be misleading. The comparison that matters is with yourself: measure your own baseline, start with the worst segment, and pull your own number down quarter by quarter.

Does a reschedule count as a no-show?

No. A reschedule shows the customer is staying in the relationship and is usually evidence that your reminder chain is doing its job. Record it as its own status, then track separately what happens on the new date.

Do deposits eliminate no-shows?

They reduce them, but not for free. Asking for payment adds friction at the booking step and turns some customers away before they book at all. Try the cheap tools first — calendar invites, confirmation requests, easy cancellation — and keep deposits as a rule reserved for customers with a repeat no-show history.

Is it worth calling a no-show on the same day?

Usually yes, especially right after the missed slot. The purpose is rebooking, not accountability; a short call made that day converts into a new appointment far more often than an email sent a fortnight later.