Taking bookings without the back-and-forth

Someone visits your site on a Sunday evening, decides they want an appointment, and finds a phone number. They can't ring on a Sunday evening, so they send an email instead. You answer Monday lunchtime with three possible times. They reply Tuesday with a fourth. You confirm on Wednesday.

Four messages and three days for something that took ninety seconds of actual decision-making. And that's the version where it works — the more common ending is that the enquiry goes quiet somewhere around Tuesday, because by then the moment has passed.

The cost of taking bookings by hand isn't the time it takes you. It's the bookings that never happen. Here's how to set up online booking properly, in an afternoon, and what each decision actually changes.

Start with the services, not the calendar

Everything else follows from this, so it's worth ten minutes of thought. A service is a visit type — one kind of appointment, with a length. "Exam and cleaning." "Emergency — in pain." "Consultation, thirty minutes." "Puppy first visit."

Two things matter when you name them.

Use the customer's words, not your trade's. The person booking is choosing from a short list of chips on a page, with no one to ask. "Initial assessment" makes them hesitate; "first visit" doesn't.

Keep the list short. Three to six visit types is almost always right. Every service you can technically perform does not need to be bookable — the temptation is to list your whole capability and the effect is a wall of options that stalls people. If two visit types run the same length and the same preparation, they're one service with a note in the form.

The length you set does real work: it spaces the openings and sizes the block on your calendar. Set it to the honest length including the writing-up afterwards, not the optimistic one.

Your hours are a pattern, not a diary

This is the part people expect to be laborious and it isn't. You don't type in individual appointment times. You describe the shape of your week once — the start times you offer on each weekday — and the openings are generated from it, rolling forward, for as far ahead as you've said the diary is open.

Four settings do the rest, and they're the difference between a booking system that helps and one you end up fighting.

• Seats. How many people can take each opening. One for a one-to-one; six for a class or a group session. This is how a studio runs a Thursday evening workshop through the same system as its private sessions.
• Lead time. How much notice you need. Set it to twenty-four hours and nothing inside tomorrow can be booked. This is the single setting that stops you being ambushed at 8am by a booking made at 7:40.
• Window. How far ahead people can book. Sixty days is a sensible default. It stops someone reserving a slot next March that you'd rather decide about nearer the time.
• Closed dates. One-off exceptions — holidays, the week you're away — taken out without disturbing the weekly pattern underneath.

Because it's a pattern, changing your Thursdays updates every future Thursday at once. And a single opening can still be closed by hand for a day off, or when you've taken a booking over the phone and want the seat off the site.

Set the time zone while you're there. Times are stored in universal time underneath, so someone booking from another country sees the right hour rather than yours.

Confirm now, or confirm later

This is the most consequential setting in the whole feature, and it lives on the booking form rather than the service. When someone submits, one of two things happens.

Instant

The slot is taken there and then. The booking arrives already confirmed, and the visitor leaves knowing they have an appointment.

Request

The time is held, but the booking lands as a request, waiting for your say-so. Nobody has an appointment until you confirm it.

Choose instant when any customer at any published time is fine — a barber, a class, a nail bar, a standard service call. Choose request when you genuinely need a say: a first consultation you might need to triage, a home visit whose travel you have to check, anything where the wrong booking costs you a chunk of the day.

Request mode is a promise to reply. If you can't answer the same day, instant booking is the kinder setting — for both of you.

There's a third shape worth knowing: a simple form, which takes no time slot at all. It's the "get in touch and we'll sort out a time" version, for enquiries that aren't ready to be appointments. Plenty of sites run both — a short enquiry form on the contact page, a full booking form on its own page.

Ask less than you think you need

Every additional field costs you bookings. Not many each — a few percent — but they compound, and the fields that cost the most are the ones a person can't answer confidently on a phone at 10pm.

The floor is: name, email, phone, which service, which time, and one open box for "anything we should know". That's a complete booking. Everything beyond it should have to justify itself with a sentence starting because otherwise on the day we…

Some things genuinely clear that bar — insurance, the make of the thing you're servicing, whether there's parking. Offer those as a short list to pick from rather than a blank box; a dropdown of five options is faster to answer and infinitely easier for you to read later. Whatever you ask is stored on the booking and shown when you open it, so you're reading answers, not hunting through an email thread.

Two extras earn their place on most forms. A new or returning switch, which tells you how much time to allow. And an urgent-cases box — the short "in pain today? call us on…" notice, for the people who shouldn't be waiting on a form at all.

One more, quietly the most valuable: the newsletter opt-in. A booking is the single best moment you will ever get to ask for permission to write to someone — they've just chosen you. Leave it unticked, say plainly what you'll send, and let it work for a year.

You don't need to add a captcha or a "prove you're human" puzzle. Bots are handled underneath, with a hidden field they fall for and a limit on how fast the form can be submitted from one place. Adding a puzzle on top costs real customers and catches nothing extra.

The two emails that do the work

A confirmation goes out immediately, carrying the reference, the time and the place, and wearing your site's colours and logo rather than looking like machinery.

Then there's the reminder, sent a set number of days before the visit. If you change one setting after reading this article, make it this one. No-shows are the tax on running a diary, and a reminder a day or two ahead removes most of them for no ongoing effort. It's the highest return available anywhere in the feature.

Keep it short. The visit, the time, the address, and what to bring. It's read on a phone, usually while walking.

Cancelling a booking from your end tidies up after itself: the seat goes back into the pool for someone else, and the pending reminder is voided, so nobody is reminded about an appointment that isn't happening.

Where the visit happens

After "when", the most-asked question is "where" — and it's set per service, which is more useful than it sounds. An address for the ones you do in the studio, a join link for the ones you do online, plus a line for the thing that isn't on the map: Suite 200, ring the bell — the door on the alley isn't ours.

It's copied onto each booking it makes, and you can change it on one booking without touching the service. The house call on Thursday gets the customer's address; every other Thursday booking is unaffected.

Getting the diary into the life you actually live

Bookings that live only in a browser tab you have to remember to open are not much better than an email thread. Two things fix that.

The calendar lays the week out the way you think about it. And the subscription feed puts the same bookings into the calendar app you already use — Apple, Google or Outlook — where they keep themselves up to date, appear on your phone, and drop off again when something is cancelled. It's a private link, and you can regenerate it if a phone goes missing or someone leaves, without disturbing anything else.

Two habits are worth building alongside it. Work the requests queue daily, in one sitting. And mark visits completed or no-show as you go — it takes a second, and after a couple of months it's the only honest picture you'll have of how often people don't turn up, which is the number that tells you whether your reminder timing is right.

What it won't do, said plainly

Three limits, so you can plan around them rather than discover them.

Bookings don't take payment. There's no deposit at the point of booking. For most service businesses that's fine — you charge at the visit — but if deposits are how your trade protects itself against no-shows, know that before you build your page around this.

Customers can't reschedule themselves. Someone who needs to move will ring or email, and you'll change the booking. Which makes one small thing worth doing well: put your phone number in the message shown after booking, and in the confirmation. A customer who can't find how to change an appointment simply doesn't come.

Reminders are counted in days, not hours. One day before suits most trades. If your business genuinely needs "three hours before", it isn't there yet.

The record you're keeping

Worth a paragraph, because a booking is not just a diary entry. Each one creates or updates a customer record, which is how a year of appointments quietly becomes a list of people you can write to. It also keeps a snapshot of the details as they were on the day, so editing someone's record later never rewrites history, and a timeline of everything that happened to it.

And because the answers people give a booking form are often personal — a symptom, an insurance number, a reason for the visit — old bookings don't keep that detail forever. After the retention period the personal content is stripped and the record itself stays: who came, when, for what service. If someone asks you to erase them entirely, that's a separate tool, and it does what it says.

---

An afternoon, then five minutes a week

In order, none of it clever:

• Write down your three to six visit types and an honest length for each.
• Set your weekly start times, your seats, a lead time you can live with, and your holidays.
• Build one booking form. Decide instant or request. Five fields, not twelve.
• Turn the reminder on at one day, and put your phone number in the confirmation.
• Place it on a page, then book yourself an appointment from your phone, as a stranger would.
• Subscribe your own calendar to the feed, and cancel the test booking.

That last step is the one people skip and the one that finds everything: the service named in language nobody uses, the required field you can't answer standing up, the confirmation that doesn't say where to park. Ten minutes as your own customer is worth an afternoon of adjusting settings.

Then leave it alone. The point of this is not to give you a new thing to manage — it's that Sunday evening, when someone decides they want an appointment, and the answer is already yes.