A booking page should ask what the job occupies, not whether the day is free
A day is not full or empty on its own — it is full for one kind of job and free for another, because different jobs occupy different resources. A calendar that shows one availability for everything either turns away work it could have taken or accepts work it cannot deliver.
Most booking pages show a single calendar: green days and grey days. That works when every job is the same size and uses the same thing. Almost no service business is like that.
In the detailing prototype we built, a full-body paint protection job takes a bay for three days. A wash takes a different bay for two hours. Pick the paint job and half the week goes red. Switch to the wash and the same days are open again — nothing changed except which resource the question is about.
The three things a slot is made of
| What the job needs | Example | What happens if the calendar ignores it |
|---|---|---|
| A person with a specific skill | A chef who cooks a particular cuisine | You book someone who cannot do the job |
| A place or piece of equipment | A spray bay, a lift, a kitchen | Two jobs are booked into one bay |
| A duration that is not one slot | Three days, not an hour | A three-day job is booked into a one-day gap |
A calendar that models only the third one — duration — is the common half-solution. It stops double-booking the clock but not the bay, and the failure shows up on the morning of the job, in front of the customer.
A full day is a waitlist, not a wall
When a customer clicks a day that is fully booked, the usual response is nothing: the day is grey and he is expected to guess again. That is the moment you lose him, because guessing is work and he came here to stop working.
In the prototype, clicking a full day names the resource that ran out and gives the next date that can take this job. Both halves matter. The reason tells him it is not arbitrary; the next date gives him something to accept without going back to the calendar.
What this changes about the enquiry
Once the calendar knows what each job occupies, the booking form stops needing to ask "when would suit you" as an open question. It asks what the job is, and the dates that remain are all real. Every date the customer can pick is a date you can actually deliver — which is the only promise a booking page makes.
For a service that travels — a chef, an installer, a technician — the resource includes the journey. A booking two hours away occupies more of the day than the job itself takes, and a calendar that does not know the travel radius will sell a day twice.
Part of
Location pages for a local service business, without the doorway problemHow to build city pages for a service business that operates in dozens of places, and the line between a useful location page and a doorway page.