What your customers see

Booking online

The booking page shows a customer the times they can actually have. Everything on it is worked out from your services, your resources and your opening hours, so a slot being offered means it is genuinely free.

The address

/book/your-branch for one location, or /book/your-business, which resolves to your only branch or sends a chain's customer to the directory to pick one.

What the customer does

  1. Picks a service. This is what sets the length of the appointment, so it has to come first.
  2. Picks a date. Only days with something available are offered.
  3. Picks a time from the slots that exist for that service on that day.
  4. Gives their details — the same configurable set of fields as the join form, and you can ask different things of somebody booking than of somebody walking in.
  5. Confirms, and lands on a confirmation page with everything on it.

Where the slots come from

A slot has to survive several filters before a customer is offered it:

  • The branch's booking hours. Nothing outside the working day, and nothing on a day the branch is closed.
  • The service's length— and any buffer after it, so back-to-back bookings do not leave you with no time to reset between them.
  • Notice rules. How soon something can be booked from now, and how far ahead. A service can be stricter than the branch, never looser.
  • Resource availability. Where you use resources, a slot only exists if something that can perform that service is working then and not already claimed.
  • What is already booked. Existing appointments take their resources out of circulation for their duration.

No resources means no double-booking protection

Without resources defined, nothing limits how many bookings can exist at the same time. If two people at eleven o'clock is a problem for you, define your resources — see resources.

Which time zone the customer sees

Slots are shown in the branch's local time, because that is where the customer has to physically be. Somebody booking from abroad sees the time the appointment will happen locally rather than a translation into their own zone, which would tell them the wrong thing to write in their diary.

After they book

The confirmation page carries the date, time, branch and service, and a link the customer can come back to. From there — where you allow it — they can confirm, reschedule, tell you they have arrived or are running late, cancel, or correct their details. Rescheduling re-checks availability the same way the original booking did.

A reminder goes out ahead of the appointment and a follow-up after it, both driven by the clock. Switch them on and word them under customer messages.

Bookings and walk-ins together

Both flows can run at the same branch at the same time. What keeps them from colliding is resources — a booked stylist is not available to the waitlist, and the waitlist's throughput accounts for the ones that are busy. See waitlist and bookings.