Appointment Request Forms That Look Like Bookings

Booked, as far as they know

The form has a date picker, a time picker and a button that says Book now. The customer chooses Saturday at two, presses it, and reads: thank you for your booking.

They put it in their calendar. As far as they know, Saturday at two is theirs.

At the business, an email has arrived in an inbox, to be read when someone has a moment. Saturday at two may already be taken. Nobody has agreed to anything yet.

Where the wording promises too much

• Book now on a button that only sends an email.
• Date and time pickers that accept any slot, including full ones.
• A thank-you page saying the booking has been received.
• An automatic email with confirmation in its subject line.
• No reply time, so silence looks like a yes.

The fourth does the most damage. An email titled confirmation is what people search for the night before, and it tells them they are expected.

Why forms end up like this

Book is the word customers use, so it goes on the button. The form came from a template or plugin written for businesses that take real bookings.

The owner knows it is a request, because the owner reads the emails. The customer only sees the screens, and every screen says booked.

Nobody set out to mislead anyone. The words were simply chosen for the system the owner hopes to have, not the one that exists.

Say it is a request

Call the form what it is. Request a time on the heading, Send request on the button, and one line above the date field: this is a request, and we will confirm by phone or email.

The thank-you page says the same in plain words: your request has been sent, and it is not confirmed yet.

The automatic email follows suit, with a subject such as we have your request, rather than anything containing the word confirmation.

A date field is not a calendar

A date picker suggests the business's calendar sits behind it. In a request form it does not: a fully booked Saturday can be chosen as easily as a quiet Tuesday.

If the form keeps a date field, label it preferred date and time. If your busy times are predictable, say so beside it: Friday and Saturday evenings fill first.

That one line sets expectations before the request is sent, which is cheaper than correcting them afterwards.

Say when they will hear back

A request with no reply time leaves the customer guessing, and most guess that no news means yes.

Promise a window you can keep with the staff you have: within two hours during opening hours, for example, and by ten the next morning for requests sent at night.

Then keep it. A promised reply time that is missed is worse than none, and a same-day request is better handled by phone, so say that too.

Say what happens if the time is taken

Ask for a second choice on the form, or how flexible the customer is: mornings only, any weekday, this week or next.

When the first choice is gone, the second lets you confirm in one message instead of three. When both are gone, offer the nearest times you have.

Every request gets an answer, including the ones you cannot fit in. A customer told no today can book next week; one who hears nothing books elsewhere.

A worked example

A golf simulator lounge with four bays and a small bar takes most of its weekend business from groups: birthdays, office outings, friends after work.

Its website had a Book a bay form with a date, a time, the number of players and a Book button. The thank-you page said thanks for booking, and an automatic email titled booking confirmation repeated the details.

The requests went to the owner's email, read between pouring drinks and resetting bays. On busy Fridays, groups arrived expecting a bay that had gone to a phone booking an hour before.

The mechanism was the wording. Every screen after the button told the customer the job was done, and nothing told the lounge it had a promise to keep.

The button now says Request a bay, the form asks for a second choice, and the thank-you page and automatic email both say the request is not confirmed yet.

They also say when to expect an answer, and requests go to a shared inbox on the tablet behind the counter. Confirmations go out with Confirmed in the subject line.

The confirmation itself

Make the real confirmation unmistakable. Confirmed in the subject, then the date, the time, the address and parking, what to bring and how to change or cancel.

Send it as a separate message, so the customer can tell the request from the answer in their inbox at a glance.

Until it arrives, the customer is not booked, and every screen before it should say so.

Requests in the right inbox

A request is only as good as the speed of its answer, and the speed depends on who sees it.

Send requests to whoever runs the schedule, not a general inbox the whole office skims. Check that they arrive, including on weekends, and look in the spam folder once a month.

Submit a test request yourself every so often. Forms stop sending quietly when a plugin updates or an email setting changes.

The counter-case

A request form is the right tool for plenty of businesses: work that needs assessing first, appointments of varying length, or a schedule that cannot be shown accurately online.

Where appointments are predictable, real online booking may serve customers better, since they see actual availability and leave with a confirmed time.

Some businesses run both: online booking for standard appointments, and a request form for anything unusual. Each needs its own clear label.

Either is fine. What fails is a request form dressed as a booking system. Call it a request, say when you will answer, and confirm separately.

Before the next request

1. Change the button to Send request.
2. Add a line saying the time is not yet confirmed.
3. Ask for a second choice of time.
4. State your reply time on the thank-you page.
5. Retitle the automatic email as a request received.
6. Send confirmations with Confirmed in the subject.
7. Route requests to whoever runs the schedule.

Step four is the promise that makes the rest work. A customer who knows when to expect an answer waits for it; one who does not takes silence for a yes.

When booking happens on another site, making the hand-off clear is covered in a booking button that opens someone else's website.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.