- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
A status looks like a label and behaves like a decision — it drives the reminders, the follow-up and every report about the calendar.
Different status of appointment: what each one is actually claiming
An appointment status looks like a label and behaves like a decision. It determines which reminders go out, which follow-up fires, whether the slot is released for someone else, and — because it feeds every report about the calendar — whether the business’s view of its own week is accurate. A calendar where everything stays on its booked status is a calendar that tells you nothing after the fact.
The statuses themselves vary by platform, but the underlying set is consistent, and the distinctions that matter are the ones people collapse.
The set, and who is expected to set each one
| Status | What it claims | Who sets it |
|---|---|---|
| New or unconfirmed | A slot is held, nobody has agreed it yet | The booking itself |
| Confirmed | Both sides expect it to happen | The customer replying, or staff |
| Showed | It happened | Staff, afterwards |
| No-show | The time passed and nobody came | Staff, afterwards |
| Cancelled | Called off before the time | Either side |
| Invalid | The booking was never real | Staff, on review |
The two halves of that table behave differently. The first three lines are about expectation and can be automated; the last three are records of what happened and mostly cannot. This is why a calendar drifts: the statuses that need a human are the ones nobody has time for on a busy afternoon.
Confirmed is not the same as booked
A slot held by someone filling a form is a hypothesis. A slot the customer has actively confirmed is an agreement, and the two convert at noticeably different rates. Keeping them separate is what makes an automated reminder system worth building — the reminder can escalate for an unconfirmed booking and simply inform for a confirmed one, which is a better use of the customer’s attention than sending everyone the same three messages.
It also changes what the day looks like from the inside. A morning of four confirmed appointments and a morning of four unconfirmed ones need different preparation, and only the status distinguishes them.
No-show and cancelled are different events with different fixes
Collapsing these is the most expensive habit in calendar hygiene. A cancellation is a customer telling you in advance, which costs a slot and nothing else, and can often be rebooked in the same conversation. A no-show is a slot consumed with nobody in it, and it is the one that reducing no-shows is about.
Recording them the same way makes the number useless: a business with a healthy cancellation rate and a bad no-show rate looks identical to one with the reverse, and the two need opposite responses. Record who cancelled, too. A cancellation initiated by the business is a different signal from one initiated by the customer, and if both are logged the same way the resulting rate measures nothing about either.
Statuses drive automations, so a wrong one is a wrong message
Once follow-up is automated, an unset status becomes an active problem rather than a gap in reporting. A booking still marked confirmed after the time has passed can trigger a post-appointment sequence to someone who never attended, which reads as carelessness. review request timing is the sharpest example — asking for feedback on a visit that did not happen is worse than not asking.
Two practical guards. Make the status update part of the appointment rather than a separate task: the person closing the visit sets it, in the same minute. And put a safety net behind it — a stale opportunity trigger is the same idea applied to opportunities, and a daily prompt listing yesterday’s unset appointments takes a minute to clear.
Where the calendar meets the pipeline
An appointment and an opportunity are separate records, and the status of one should move the other. A showed appointment normally advances a stage; a no-show usually does not, and a cancellation may move it back. pipeline stages and exit criteria is where those rules belong, written down rather than assumed, and creating an opportunity from a survey is where the record was created in the first place.
This is also what makes measuring pipeline conversion answerable. Booked-to-showed and showed-to-won are two different conversion rates with two different causes, and you can only separate them if the statuses were maintained. A business that knows only its close rate cannot tell whether its problem is attendance or sales.
Timing details that change the numbers
Decide when a booking becomes a no-show rather than leaving it to whoever looks. Fifteen minutes past the start is a common rule and any consistent one works; an inconsistent one produces a rate that moves when nothing has changed. counting available days only is the related question for anything measured in days, where weekends quietly distort the figure.
Late cancellations deserve their own treatment. A cancellation an hour before costs the slot as completely as a no-show does, and if your policy treats them differently the status should too. And where a reminder or a rebooking message goes out automatically, quiet hours and local time governs when it is allowed to arrive — a 6am message about a cancelled appointment is technically correct and still a bad experience.
Getting the statuses maintained at all
- Make setting the status the last step of the appointment, not an admin task for later.
- Keep the list short. Six statuses people use beat twelve nobody does.
- Define each one in a sentence and put the definitions where staff can see them, since “cancelled” means different things to different people.
- Review yesterday’s unset appointments daily while the memory is fresh.
- Check the automations that depend on each status actually behave as intended before relying on the data.
- Keep a periodic snapshot — a log kept outside the platform is enough — so you can see whether maintenance is improving rather than guessing.
Two supporting pieces make the whole thing easier: a calendar clients can book into that does not produce bookings nobody wanted, and missed call text back so a customer who tried to reach you about an appointment is answered rather than becoming a no-show by accident. a conversation sla sets the expectation for that response.
Frequently Asked Questions
What is the difference between a booked and a confirmed appointment?
A booked slot is held by someone who filled a form; a confirmed one has been actively agreed by the customer. They attend at noticeably different rates, so keeping them apart lets reminders escalate for the unconfirmed and merely inform for the confirmed.
Should no-shows and cancellations be recorded the same way?
No, and collapsing them is the most expensive habit in calendar hygiene. A cancellation warns you in advance and can often be rebooked; a no-show consumes the slot with nobody in it. A business with a high cancellation rate and one with a high no-show rate need opposite responses.
When should an appointment be marked as a no-show?
At a consistent point you decide in advance — fifteen minutes past the start is a common rule and any consistent one works. Leaving it to whoever looks produces a rate that moves when nothing about the business has changed, which makes the number unusable for spotting a real trend.
Why do statuses matter if we know what happened anyway?
Because automations read them. A booking still marked confirmed after the time has passed can trigger a post-appointment sequence to someone who never attended, and asking for feedback on a visit that did not happen is worse than not asking at all.
Should an appointment status change the opportunity stage?
Usually yes, and the rules should be written down rather than assumed. A showed appointment normally advances a stage, a no-show usually does not, and a cancellation may move it back. Without that link, booked-to-showed and showed-to-won cannot be measured separately.
How many statuses should we use?
Few enough that staff actually use them. Six that get set beat twelve that do not, because an unset status is worse than a coarse one. Define each in a sentence and put the definitions somewhere visible, since words like cancelled mean different things to different people.
How do we stop statuses being left unset?
Make setting one the last step of the appointment rather than an admin task for later, then review yesterday’s unset bookings daily while it is still easy to remember what happened. A short daily list is far more effective than a monthly clean-up nobody enjoys.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.