Double bookings in salons, studios, clinics and restaurants usually have the same cause. A contact form was used for something that was not a message — it was a specific hour of the day — and the check that would have prevented the clash was left to a person to do between appointments.
The two form types are easy to confuse because they look identical on the page: some fields, a button, an email arrives. The difference is in what the visitor believes afterwards, and in what has to be true for that belief to hold.
This post sets out what a booking form has to do, how an inbox-run booking fails, and how to tell which of the two a business needs. Most of it applies whichever tool is used to build the site.
A contact form carries a message; a booking reserves a slot
When somebody sends an enquiry, nothing has been agreed. The reply can come this evening or tomorrow, and the sender knows they are waiting for an answer. The form's job was to carry some words without losing them.
When somebody books the three o'clock, an agreement has been made at the moment the button was pressed. The visitor now expects to have three o'clock, and will plan the afternoon around it.
That expectation is what the rest of the requirements follow from. Each failure below is a version of the same thing: creating the expectation and then not being able to honour it.
The four things a booking form has to get right
These requirements hold whatever the form is built with, and they are worth knowing even where none of it is automated — they are also the four ways an inbox-run booking comes apart.
1. It has to know the capacity
A slot is not simply free or taken. It has a number attached: one chair, two therapists, four tables at seven, twelve places in a class, six dogs in a day. A form that treats a time as yes or no describes only the single-operator case.
This is the requirement that sounds like an edge case and is not. As soon as there are two chairs, "is three o'clock free" cannot be answered without counting.
2. It has to be able to refuse
When a slot is full, the form has to stop accepting at the moment of submission, on the visitor's screen, while they are still there and can choose another time.
The alternative is that everything is accepted and sorted out afterwards, which means someone is told later that the time they arranged their day around is not available. A refusal at the moment of booking is a minor inconvenience; a refusal the next morning is a cancellation the customer did not make.
3. The reservation has to be atomic
Two people submitting within the same second for the last place is an ordinary case rather than an unusual one — it is what happens when a timetable is posted and several people open it at once.
One of the two can have the place, and which one has to be decided by the system rather than by the order two emails happen to arrive in. This requirement is invisible until it occurs, and it is not one that being organised can compensate for.
4. It has to reach the business, and stay findable
A booking that arrives somewhere nobody looks is not yet a booking.
Email on its own is weaker than it appears here: it is a stream, it moves down the inbox as other mail arrives, and searching it six weeks later for a booking time is unreliable. The booking is more useful as a record that can be looked up, alongside the email that announces it.
How an inbox-run booking fails
Running bookings through a contact form makes a person the capacity check. Every submission arrives, none are refused, and somewhere between them somebody decides whether the day still works.
On a quiet week that is workable. On a busy week it tends to look like this:
- Two enquiries arrive while the business is with a customer. Both ask for four o'clock. Neither was refused, because nothing was in a position to refuse.
- The first is confirmed. The second is answered an hour later, and that answer is an apology rather than a confirmation.
- Somebody cancels by replying to their own email. The cancellation is a message in a thread rather than a slot going back on sale, so the time stays unavailable.
- The business closes for a week. The form keeps accepting bookings for that week, because the form holds no information about it.
- In March, somebody asks to move an appointment made in January. The original is hard to find, because it is an email with the subject line "Website enquiry".
Where the cost lands
None of these failures loses the booking. They affect the relationship, and they do so on the days when there is least time available to repair it.
That is why the problem is worth attention even at a handful of bookings a week: the failure rate is low and the cost of each failure is high, which is the profile of problem that tends to be left alone until it happens.
What to ask for on the form
A booking form's field list trades what the business would like to know against how many visitors finish it. Longer forms are completed less often, and the people who abandon them are disproportionately those in a hurry.
A workable rule: ask for what is needed to hold the slot and make contact. The rest can be asked in the conversation that follows.
- The service, picked from a list rather than typed, so it cannot be something the business stopped offering in January.
- The date and time, chosen from what is actually available rather than entered as free text.
- A name and one way to make contact, which for many trades is a phone number rather than an email address.
- Anything that changes the length or the price of the slot — the size of the dog, the number of people, whether it is a first visit.
Picked from a list rather than typed
A text box asking what the visitor would like produces bookings for services that are no longer offered, at lengths that were not planned for, and each one takes a phone call to correct. A list offers only what is currently sold.
A list also lets the slot length follow the service, so a thirty-minute treatment and a ninety-minute one do not occupy the same amount of the day.
What happens after the button is pressed
The booking existing is half of the job. Three things follow it, and the second is the one most arrangements leave out.
The customer gets a confirmation
On screen immediately, and then again in writing. The on-screen confirmation does more work than it appears to: without it, a visitor who is unsure whether the submission worked will phone to check, which is the call the form was there to prevent.
The business gets a record, not only an email
The email reports that a booking happened. The record is what gets consulted on Tuesday morning to find out what Tuesday looks like.
This is a useful thing to check when choosing a tool, because it determines whether the arrangement is still workable in six months. A set of notification emails is not a diary.
A cancellation puts the slot back
If cancelling produces a message rather than a change to the booking, every cancellation becomes a manual task, and the slot stays sold until somebody performs it.
This is also the practical difference between a booking system and a well-organised inbox: the state of the day is held in one place, and everything that changes the day changes that place.
Time zones and the clocks changing
One specific trap, because it catches otherwise careful setups. A time means little without a zone attached, and the clocks change twice a year.
If a booking is stored as "3pm" with no zone, then when the clocks change every future booking in the system shifts by an hour. The discrepancy usually surfaces when somebody arrives at what they were told was the right time.
This does not have to be solved by the business itself, but it is worth knowing about, because it makes a good question to ask of any tool under consideration: what happens to existing bookings when the clocks change?
When a booking form is not the right tool
Many businesses do not need a booking form, and adding one has its own costs.
Where what is sold is a job rather than an hour — a roof, a rewire, a house move, a piece of legal work — the visitor is not taking a slot. They are starting a conversation that ends in a price. A contact form fits that, and a calendar in front of it adds a step without adding information.
A rough test: can the price and the duration be stated in advance? If so, it is a slot. If the honest answer is that it depends on what the job turns out to involve, it is an enquiry.
How this works on a Sitemo site
A booking section holds the slot against the capacity set for it and refuses once that capacity is reached, rather than accepting a booking that would have to be cancelled by phone. The reservation is made atomically, so two submissions at the same moment cannot both take the last place.
The service list on the form is filled from the site's own services, so it cannot offer something that has been removed. Each booking is emailed and also kept as a record that can be looked up later.
Where a trade quotes jobs rather than selling time, the same site provides a short enquiry form instead, which arrives as an email and as a record in the same way.
The bottom line
A contact form has one job: carry a message without losing it. A booking form has four, and three of them are about refusing — knowing the capacity, stopping when it is reached, and deciding between two people who want the same last place.
For a business that sells hours, those three are the difference between a system that reflects the state of the day and one that can sell the same hour twice.
For a business that sells jobs rather than hours, none of it applies, and a short enquiry form is the whole answer.
Frequently asked questions
- Can I use a contact form and manage bookings myself?
- Yes, and for a business taking two or three bookings a week it is often reasonable. The point at which it stops working is not a particular number of bookings; it is the moment two can arrive while nobody is able to look at them, because that is when the capacity check stops happening.
- What happens when two people book the last slot at the same time?
- That is the case a booking form has to answer and an inbox cannot. The reservation has to be atomic: one submission takes the place and the other is told immediately that it has gone, with other times offered, while the visitor is still on the page.
- How many fields should a booking form have?
- As few as are needed to hold the slot and make contact — typically the service, the time, a name and a phone number, plus anything that changes the length of the slot. Longer forms are completed less often, and the remaining detail is usually easier to collect in conversation.
- Should the booking take a deposit?
- It depends on the no-show rate and the trade. A deposit reduces no-shows and also adds friction at the moment somebody is deciding, so it is a trade-off worth making deliberately rather than because a tool offers it.
- Do I need a separate scheduling product?
- Not necessarily. A site that can hold a slot against a capacity, refuse when it is full and keep the booking as a record covers what a scheduling product is mainly used for. A separate product is worth it for staff rosters, resource allocation or taking payment.
- What about cancellations and changes?
- The thing to check is whether a cancellation returns the slot to sale on its own. If cancelling produces a message that somebody then acts on, every cancellation is a manual task, and on a busy week the slot is likely to stay sold.