A guide for clinic operations
How to reduce no-shows at an aesthetic clinic?
Reduce no-shows by separating them from cancellations, measuring the schedule, choosing up to five reminder lead times and offering released slots to a waitlist with human review.
A no-show is not just an empty hour. It interrupts the care sequence, changes the cash forecast and leaves a slot that could have been offered to another client. Before looking for a reduction promise, the clinic owner needs to see when someone did not arrive, when they cancelled and when the team filled the opening. This guide turns behaviors that already exist in Bia's schedule into a decision routine. It does not invent percentages, treat a reminder as confirmation or replace the team's judgement.
- Separate a recorded no-show from a cancellation made before the appointment
- Up to five configurable reminder lead times with deduplication
- Rescheduling and cancellation stop old messages
- A waitlist with service, professional and preferred date range
- Indicators calculated from the clinic's own history
- Clear limits so automation never becomes a promise of attendance
1. Measure no-shows and cancellations separately
A no-show should be recorded as a no-show, not a cancellation, so the clinic can see the real problem.
In the backend, a confirmed appointment can become a no-show only after its start time and while it is not completed. The operation changes the state to `no_show`, cancels pending jobs for that appointment, emits the no-show event and records an audit with before and after. That is different from a clinic cancellation: it changes the state to `cancelled_by_clinic`, can store a reason and may start a compatible waitlist offer. Collapsing those states makes the report answer the wrong question.
In practice, the team decides which fact happened before closing the day. Did the client tell you they would not come? Record the cancellation and available reason. Did the time start and nobody arrive? Record the no-show when the rule allows it. Rescheduling is not a no-show either: it creates a new time check and reorganizes reminders. The first gain is data quality, not a flattering number.
- No-show: confirmed appointment, start passed and not completed.
- Cancellation: explicit clinic action with an optional reason.
- Rescheduling: the new time is checked against conflict rules again.
2. Use the data the schedule already knows
A useful count starts with a consistent record. Each appointment connects a client, service and professional and stores start, end and state. A room or piece of equipment can also participate in availability. The web schedule organizes the week by day and uses the clinic's configured time zone, so compare civil days in that zone instead of copying times shown by another person's computer.
Separate at least four questions: how many appointments were confirmed, how many were completed, how many were cancelled and how many became no-shows. Then add service, professional and time of day. A first-slot no-show may have a different cause from a late-evening no-show; a new professional may need a different routine. The code supplies states and links; the clinic still interprets the cause.
Do not use a phone number or name as the counting key. Records can be merged, and the schedule uses tenant-scoped identifiers. If you keep a temporary worksheet, record the extraction date and counting rule. A small repeatable series is more useful than a broad market estimate. This page does not claim an average no-show rate because no figure has been verified for this clinic.
- Compare equivalent periods in the clinic time zone.
- Break the reading down by service and professional before changing policy.
- Record the counting rule with the result.
3. Configure reminders without calling them RSVP
When a confirmed appointment is created or rescheduled, the scheduling service considers the lead times chosen by the clinic: up to five from 72, 48, 24, 3, 2 and 1 hours. Each new job stores its lead time and an idempotency key, so repeating the operation does not duplicate the work. If the target is already past, the job is skipped; if quiet hours leave no valid time, it is not sent outside policy.
Processing checks again before preparing the message. The appointment must still be confirmed, and an opted-out or blocked client does not receive the reminder. The text uses the configured template and the clinic time zone. Rescheduling or cancellation disables pending jobs for the old time, so the team should not send a manual confirmation that contradicts the new schedule.
Reminders notify; they do not store a client's response. The product does not currently persist an RSVP state saying that someone accepted, declined or did not answer. That is a separately recorded product gap, not a promise on this page. The owner can invite a reply, but must still read the real schedule states and handle an absence under the clinic's rule.
- Choose up to five lead times, or turn them all off.
- Check WhatsApp and quiet hours before blaming the copy.
- A sent message is never proof of attendance.
4. Make cancellation and rescheduling easy before the time
A client who can give notice creates a better decision than a chair discovered empty too late. The team schedule has separate actions for cancellation, rescheduling, completion and no-show. Rescheduling receives a new date and time, checks notice, availability and conflicts and calculates new reminders. Cancellation can keep a reason, stops pending messages and may start an offer for a compatible opening.
In your communication, say which channel the client should use and when the team can still reorganize the slot. The product does not promise a public self-booking calendar; the team or WhatsApp receptionist can operate the booking. Do not offer a button the client cannot find or say that an opening was filled while it still depends on a waitlist response.
A readable policy also reduces reception disputes. Explain what happens when someone gives notice, cancels late or does not arrive. This guide supports the routine but does not decide deposits, penalties or charges; it assumes none of them. Align copy with the Terms and the real practice before publishing a campaign.
- Explain the difference between notice, rescheduling, cancellation and no-show.
- Use the date and time in the clinic time zone.
- Do not promise a public self-booking flow that does not exist.
5. Give the team a short daily routine
Automation works best when someone checks context. At the start of the day, the receptionist can review confirmed appointments, conflicts and blocks. Before each period, check the reminder policy and messaging connection. At the end, separate completed, cancelled and no-show visits; a no-show is valid only after the start time. This cycle prevents changing a state just to make a list look clean.
When a message fails, read the operational reason before trying again. Opt-out, block, quiet hours and an appointment that is no longer confirmed are different states. The backend records events and audits for cancellation and no-show, while the interface shows errors instead of pretending an empty list is success. The person in charge should record the exception and decide whether the next contact is human.
Choose one person to review the queue and another to cover absences, even in a small clinic. A two-minute procedure near the schedule is more dependable than memory. If the team changes a time, the new appointment must pass validation again. If it changes a state, note the reason. The product preserves the transaction; the clinic preserves the explanation.
- Before care: check schedule, blocks and messages.
- After care: complete, cancel or record no-show through the correct action.
- On error: preserve server information and escalate the human exception.
6. Use the waitlist for a real opening
The waitlist stores the client and can add a service, professional, acceptable range and notes. Service and professional can stay open when any compatible option works. Creation validates the client's link to the clinic, prevents two active waiting entries for the same client with a lock and keeps data in the right tenant. That is more actionable than a loose calendar note.
When the clinic cancels a confirmed appointment, the transaction looks for the oldest waiting entry compatible with service, professional and range. Under a lock it marks the entry `notified` and creates an idempotent offer job. Processing checks that the slot is still free, that the appointment remains cancelled and that the client can receive messages. If another booking occupies it, the entry returns to `waiting` instead of announcing a false opening.
The interface separates waiting, notified, booked and cancelled and lets the team mark the consequence after contact. Being notified does not mean the client accepted: there is no persisted RSVP. Confirm through the available channel, operate the appointment and only then mark the entry booked. If the client declines, close the entry without erasing the decision history.
- Record only the range and preferences the client gave.
- An offer depends on compatibility and the slot staying free.
- `notified` does not confirm a response by itself.
7. Track indicators your clinic can explain
A simple indicator can use real states: no-shows divided by appointments that were confirmed in the period, cancellations kept separate and reschedules observed separately. Define the denominator before comparing weeks. A cancelled appointment should not vanish because it did not become a no-show. If a no-show is corrected through an authorized action, keep the explanation so the change is not invisible.
Read the result with time, service, professional and notice. Compare reminder campaigns only when the selected lead times, quiet hours and channel are equivalent. A higher rate may mean that the team started recording better, not that reminders made things worse. The system provides states, jobs and audits; it does not provide an automatic cause or universal target.
Choose one question: reduce first-slot no-shows, fill late cancellations or understand a service with many reschedules. Record the answer, intervention and review date. Do not turn one small week into proof. This page offers a way to learn from the clinic's own routine, not an unsourced benchmark.
- Declare numerator, denominator, period and time zone.
- Compare equivalent operations, not different policies.
- Use a trend to decide and review after the change.
8. Know where automation ends
Reminders cannot control transport, health, emergencies or a client's decision. They depend on configuration, WhatsApp, sending windows and contact eligibility. A waitlist cannot manufacture an opening either: it offers a cancelled time when the criteria remain compatible. Describe the workflow and its limit together, without saying every clinic will see the same reduction.
Health data and contact preferences need the care required by internal flows. The schedule can show an allergy alert to the team, but that is not a diagnosis and does not replace intake, consent or clinical protocol. This guide does not ask a clinic to collect sensitive information in a public message. Use the proper client record and intake flow for care data.
If the clinic needs answered confirmation, a deposit policy or a new report, record it as a product opportunity rather than hiding it in copy. Appointment `status` already feeds reports and constraints; reusing it for RSVP would silently break an old reading. Until an evolution exists, use current states, check the channel and keep a human decision.
- Automation organizes signals; it does not guarantee attendance.
- An operational alert does not replace clinical assessment.
- A gap becomes a product record, never a sales promise.
What this guide does — and does not promise
It organizes a routine from behaviors that exist in Bia. There is no invented reduction percentage, client testimonial or RSVP confirmation.
- The schedule does not currently persist a client's confirmation response; a sent reminder is not acceptance.
- Messages depend on an operational WhatsApp connection, enabled policy, valid window and eligible contact.
- The waitlist offers a compatible slot, but the team confirms the reply and operates the booking.
- A no-show should be marked after the start and never replace cancellation or completion.
- No indicator on this page guarantees financial or clinical results.
Frequently asked questions
Questions about no-shows and scheduling
What is the difference between a no-show and a cancellation?
A no-show is recorded after a confirmed appointment has started and was not completed. A cancellation is a separate action with its own state and optional reason; combining them distorts the clinic's reading.
Do reminders confirm that a client will attend?
No. Bia schedules up to five lead times selected by the clinic and checks eligibility, but it does not currently store a persisted RSVP.
How does the waitlist receive an opening?
On cancellation, the system finds the oldest waiting entry compatible with service, professional and range. A job notifies the client; the team confirms and marks the next state.
Can I promise a percentage reduction?
Not without a clinic data series and a defined counting rule. This page offers a measurement method, not a universal result.
What should I do when a reminder does not arrive?
Check the selected lead times, time zone, quiet hours, WhatsApp connection and contact eligibility. If the appointment changed state, the old job may have been correctly cancelled.
Test the routine with your own schedule
Create an account, add services and professionals and observe how the schedule separates confirmation, cancellation, rescheduling and no-show.
Create my account