A visitor who wants an appointment, a site visit or a consultation has already decided something. They now want the smallest possible step to a date in the calendar. If the only option is a phone number that nobody answers at lunchtime, many of them will try the next company.
You do not need a booking platform to fix this. For most small companies a plain request form and a clear routine are enough.
Request, not booking
There is a difference worth stating on the page. A live calendar lets the visitor book a slot directly. A request form lets the visitor propose times, and your team confirms one. Direct booking suits companies with standard slots, such as a fixed 30-minute consultation. A request form suits companies where the time depends on a person, a vehicle, a place or the size of the job.
Both work. What matters is that the visitor knows which one they are using. Write "Request an appointment. We confirm by email within one working day." rather than "Book now" if a person still has to agree.
What to ask
Every extra field lowers the number of finished forms. Ask for what you need to propose a time and prepare for the visit, and no more:
- Name.
- Email and, if you may call, a phone number. Say which one you will use.
- What the appointment is for. A short list of your services works better than free text.
- Two or three preferred days or time windows.
- One free-text line for anything we should know, such as the address for a site visit.
- Consent line for storing the data, in the wording your country requires.
Leave out company size, budget, how they found you and anything else you will not use for the first reply. You can ask in the confirmation email. The W3C guidance on forms covers labels, required fields and error messages, which decide whether people on a phone finish the form.
What the visitor sees next
After sending, show a confirmation message on the page and send the same text by email. It should say three things: the request was received, who will answer, and by when. The GOV.UK guidance on confirmation pages gives a good model for this. An example:
"Thank you, Anna. We have your request for Tuesday or Wednesday morning. Martin from our office will confirm a time by email by the end of the next working day."
If the form fails, the visitor must see an error, not a blank page. Test this once.
Who confirms, and how fast
This is the part that most often goes wrong. A form that sends mail to a general inbox is read when someone has time.
- Name one person who confirms requests, and one backup for holidays and sick days.
- Set a reply time you can keep, for example the end of the next working day. Publish it only if you meet it.
- Reply with a concrete slot, not a question. "Tuesday at 10:00 works. Reply OK to confirm" is easier to answer than "When are you free?".
- Send a calendar entry after the visitor agrees, and a reminder the day before. Reminders reduce no-shows.
- Mark the request as done where your team can see it, whether that is a ticket, a shared sheet or a labelled mailbox folder. Our article on a shared mailbox as a ticket queue shows one simple way.
Requests that arrive outside office hours are normal. The routine above handles them if the reply time counts working days.
When the requested time does not work
Offer two alternatives in the first reply. If the visitor does not answer within two working days, send one short reminder and then close the request. Do not hold slots open for people who have gone quiet.
Check it once a month
Count three numbers: requests received, requests confirmed and the typical time from request to first reply. If the third number is longer than you promised, the fix is usually a backup person or a clearer owner, not a new tool. If many requests are not confirmed, look at which times were requested and whether you can offer more of them.
For general contact enquiries that are not bookings, see a website contact form that gets answered and handling website enquiries in one working day.
A first step
Open your own website on a phone and try to request an appointment. Count the taps and fields. Then write down who would see that request and when. If you cannot answer the second question, that is the first thing to fix.
If your website, forms and follow-up are not yet working together, see our marketing systems service.
