A guide for clinic operations

How to organize an aesthetic clinic schedule?

Organize a schedule around service, duration, professional, time zone, availability, resources and blocks; Bia checks conflicts and waitlist criteria, but it does not offer an unrestricted public self-booking calendar.

An aesthetic clinic schedule is not just a grid of times. Each interval depends on the service, the time it occupies, the professional, the room or equipment and the pauses the clinic has chosen to respect. When those facts live in separate calendars, reception sees an apparently empty slot and discovers the conflict too late. Bia connects the appointment to the client, service and operation, calculates dates in the configured time zone and checks the interval again when someone creates or reschedules an appointment. This guide turns that real behavior into a routine without promising public self-booking, automatic staffing or availability that was never configured.

Published: 2026-08-14Updated: 2026-08-14

A seven-day view filtered by the clinic's local day
Service, duration and professional checked before booking
Recurring availability rules and point-in-time blocks
Rooms and equipment preserved when an appointment uses a resource
Rescheduling, cancellation, completion and no-show states
A waitlist with service, professional and desired period

1. Start with one source of truth

Choose the clinic schedule as the place where an appointment is created and changed. The web screen shows a seven-day week, lets the team select a day and lists appointments with time, client, service, professional and state. A WhatsApp conversation may start a request, but the time should be treated as real only after the operation records the appointment. Paper, spreadsheets and personal calendars can help with review, but they should not compete for the same slot as independent sources.

One source also makes a shift handoff possible. The person opening the clinic can see what is confirmed, cancelled, completed or marked as a no-show without joining messages from several places. If a rule exists only in a note, put it in the matching configuration before occupying the grid. The schedule cannot infer a room, professional or pause that was never entered.

Open and close the day in the same schedule that records appointments.
Keep an auxiliary note separate from the operational source.
Checking configuration is safer than repairing a conflict later.

2. Register service, duration and professional together

The catalog stores a service name, price, duration in minutes and active state. Duration determines when the appointment ends; it is not just a label on a card. A thirty-minute procedure and a ninety-minute session cannot occupy the same interval. Link the service to the professionals who can perform it, because the schedule needs to know who is responsible before it can offer an option.

Bia keeps the service name and price as an appointment snapshot while the catalog can change for future sales. An inactive professional does not receive a new appointment, although older history still points to that record. When reception chooses a professional, review the service link and duration before offering the time. This prevents a fit-in that looks possible on screen but runs into the next client.

Service duration determines the appointment end.
The service–professional link is a capacity rule.
Deactivating a professional does not erase existing history.

3. Write availability in the clinic time zone

Recurring availability is stored per professional, weekday and start/end window. The editor uses weekdays 0 through 6 and rejects a window whose end is not after its start. Instead of copying times into every week, keep the weekly rule and use a point-in-time block for vacation, holidays, lunch or an exception. A clinic with multiple locations still needs to confirm which rule belongs to the operation being planned.

The tenant chooses an IANA time zone, and the schedule converts the civil date and clock in that zone before comparing an appointment. Minimum notice and the safety buffer between appointments also participate; the AI flow defaults to 180 minutes of notice and a ten-minute buffer when the clinic has not configured other values. Do not compare a computer clock with server UTC without applying the configured zone.

Register weekly windows per professional, not per device.
Use the clinic zone for dates, times and filters.
Notice and buffer can block a slot that looks empty.

4. Treat rooms, equipment and blocks as capacity

Rooms and equipment are resources registered inside the clinic with a name, kind and active state. When an appointment carries a resource, creation and rescheduling check whether that resource is already occupied in the interval. The data layer uses a concurrent lock and an overlap constraint so two confirmed appointments cannot use the same resource at once. Registering a resource does not mean every service requires it; that decision belongs to the real operation.

Point-in-time blocks can apply to one professional or to the whole clinic. The end must be after the start, and the check happens before the appointment is stored. Vacation, a break, equipment maintenance and a meeting stop being a loose message when they become a block with time and reason. If the pause repeats every week, change availability; if it is exceptional, do not falsify the weekly grid.

An active resource and the right professional must fit the interval.
A clinic-wide block applies even when an individual is available.
A block reason explains why a slot was not offered.

5. Create the appointment and check the fit-in

During creation, the team supplies a client by record or phone, service, professional, date, time and duration; it may mark a fit-in. The server validates the tenant, client, service, professional and resource before inserting. It also checks conflicts, blocks and availability. A fit-in records an exception, not permission to ignore a professional or resource conflict and not a promise of unlimited capacity.

The AI flow is stricter: it considers active, bookable services, respects notice and offers only options that passed the rules. If availability is missing or a service requires an assessment, the response must ask for the missing fact or hand the decision to staff. The public page describes what the system validates; it does not sell an open calendar where anyone can choose a time without that contract.

Confirm client, service, professional and interval before saving.
A fit-in records an exception but does not remove conflict protection.
A non-bookable service or pending assessment needs human guidance.

6. Reschedule, cancel and complete without erasing history

A change goes through the same rules as creation. Rescheduling checks notice, reschedule limits, availability, blocks, professional and resource before updating the time. Pending reminders for the old time are cancelled and new ones calculated. Cancellation writes its own state, keeps a reason when supplied and stops jobs that no longer make sense. An old message therefore cannot continue to look like a current appointment.

Completing an appointment and recording a no-show are different operations. Completion can consume supplies inside a protected transaction and leaves the time in history; a no-show is only recorded after the start according to the module rules. The status field remains used by reports, NPS and old constraints. Organizing a schedule means choosing the correct event, not changing a state meaning to make the screen simpler.

Rescheduling cancels old reminders and calculates new ones.
Cancellation, completion and no-show have different effects.
Do not delete history to make the week look tidy.

7. Use the waitlist and reminders with judgment

A waitlist entry stores a client, optional service, optional professional, desired period and notes. Its states are waiting, notified, booked and cancelled. When an opening appears, the engine finds a compatible entry and sends an alert; it does not reserve the opening automatically or turn the person into a booked client without a later action. If an offer expires or becomes unavailable, the entry can return to waiting for another attempt.

Twenty-four-hour and two-hour reminders are independent configuration choices. Jobs have an idempotency key and can be pending, sent, suppressed by quiet hours, skipped because they are late, ineligible or cancelled by a reschedule/cancellation. Use the state to explain what happened and do not count a sent message as attendance. A waitlist opens an opportunity; a reminder communicates an appointment; neither replaces reception's decision.

Period, service and professional make a waitlist matchable.
Alerting an opening is not reserving or confirming it automatically.
A job state is better evidence than an impression in an outbox.

8. Finish the week with a reproducible routine

At the start of the week, review active professionals, service links, duration, time zone, availability and known blocks. Before each day, compare the grid with rooms and equipment that will actually be available. During appointments, operate through the schedule so rescheduling, cancellation, completion, no-show, waitlist and reminders share one history. At the end of the day, separate states instead of adding everything as generic activity.

Choose reproducible measures: confirmed appointments, cancellations, reschedules, no-shows, completions, waitlist offers and sent jobs. State the period, time zone and denominator before comparing weeks. Bia does not guarantee automatic staffing, universal availability or financial results; it supplies checks and trails for the clinic to learn from its own data. When a rule is not in the code, register it as an opportunity instead of promising it on the page.

A weekly review prevents capacity surprises on the appointment day.
A metric needs a period, zone and state definition.
The team remains responsible for exceptions and clinical decisions.

What this organization does — and does not promise

This guide describes existing scheduling, availability, capacity and waitlist rules. It does not invent public self-booking, automatic staffing or availability that the clinic never configured.

The schedule validates professionals, services, duration, time zone, conflicts, resources and registered blocks.
A fit-in can allow an availability exception, but it does not remove professional, resource or block conflicts.
The waitlist alerts a compatible opening; it does not reserve it automatically or guarantee an answer.
Reminders depend on configuration, quiet hours, eligibility, phone and the connected provider.
Nothing on this page guarantees attendance, revenue, staffing or clinical outcomes.

Frequently asked questions

Questions about organizing a schedule

What should I organize first?

Use one schedule as the operational source and register service, duration, professional, availability, time zone, resources and blocks before offering a slot.

Does service duration block the schedule?

Yes. The server calculates the end from the duration and checks availability, buffer, conflicts and blocks before saving.

Can I book outside availability?

A fit-in can record an availability exception when allowed, but professional, resource and block conflicts are still rejected.

Does the waitlist reserve an opening by itself?

No. It selects a compatible entry and sends an alert. The appointment exists only after an authorized action records it.

Does Bia offer public self-booking?

The public page does not promise that. Staff or the receptionist in WhatsApp can operate the schedule according to existing services, policies and permissions.

Test the organization with your clinic's real routine

Create my account