When the show rate drops, the reflex is to add reminders. A second email, then a third, then an SMS. It helps a little, and the reason it only helps a little is that it is treating a memory problem when most of what is happening is a commitment problem.
Three different failures wearing one name
“No-show” is a single line in a report covering three unrelated events with three different fixes.
They forgot
A real category, and a small one. Reminders solve it, which is why reminders help enough to keep people believing that reminders are the answer.
They were never really coming
Someone clicked a slot because it was easier than closing the tab, or because a rep asked twice and the polite exit was a calendar link. Nothing in the reminder chain changes this — they did not lose track of the meeting, they reconsidered whether they wanted it, and the reminder is the moment they reconsider.
The wrong person booked
They booked in good faith, then discovered the topic sits with a colleague. This looks identical to the second case in the data and is a completely different problem: not weak intent, but a routing failure.
A reminder is a good answer to the smallest of the three causes, and no answer at all to the other two.
The booking is where the show rate is decided
By the time the invitation is sent, most of the outcome is already determined by how the slot was taken. Four things move it, and none of them is a reminder.
| Factor | Effect | What to do |
|---|---|---|
| Time between booking and meeting | Large | Offer this week. Intent decays; three weeks out is three weeks to reconsider. |
| Whether the visitor named the topic | Large | One required question in their own words. It is a small commitment and it shapes the call. |
| Whether they have been here before | Moderate | A first-touch booking from a cold click shows far worse than one from a returning reader. |
| Number of form fields | Negative past two or three | Every field that serves your CRM rather than the meeting costs you bookings. |
| Whether a human is named | Moderate | A meeting with a person is harder to skip than a meeting with a company. |
Read the show rate as a qualification metric
A show rate is not a scheduling statistic. It is a measure of how much intent existed at the moment of booking, and it should be read alongside the source rather than as a single number.
- Segment by source. A cold-outbound booking and a booking from someone who read four pages are not comparable.
- Segment by lead time. If same-week shows at 80% and three-weeks-out at 45%, stop offering three weeks out.
- Track whether the topic question was answered, and how well. Blank or one-word answers predict no-shows.
- Count rebooks separately. A rescheduled meeting is not a no-show, it is a scheduling conflict.
- Watch for the wrong-person pattern: no-shows clustered in one function usually mean routing, not intent.
What to do about the second cause
If most of your no-shows are people who were never really coming, the honest fix is upstream — fewer bookings, better ones. That is an uncomfortable sentence for anyone whose target is meetings booked, which is precisely why the metric produces the behaviour it does.
A rep pushed to book will book, and the no-show lands in a different column of a different report the following week. Measuring meetings held, or meetings that produced a next step, removes the incentive at the point it is created.
The related argument about ageing evidence is in a signal from March is not a signal in July — booking intent decays faster than almost anything else, which is why lead time matters as much as it does.
Bookingsis built around this: near-term slots first, one question in the visitor’s own words, and the visitor record already attached, so the person taking the call knows what was read and what was asked before anyone says hello. It is the same record Chat and Analytics write to.