Choose the booking method your team can keep accurate during a busy service. A phone number can work well when someone can answer it; an enquiry form suits bookings that staff need to check; live availability suits a venue that can keep its whole reservation record up to date.
For a restaurant or café in Formby or Freshfield, the brief should start with the dining room. How do you allocate tables, handle walk-ins and decide whether a group will fit? Those answers should determine the website journey. The broader restaurant and café website guide covers the other information customers need before deciding to visit.
Start with the tables you can actually offer
A room with spare chairs may still be unable to accept the party asking to book. Four empty seats on separate tables will not necessarily suit a group of four. Combining tables may affect another booking, and an arrival late in a sitting can leave less time before the room needs to be ready again.
Write down how those decisions are made now. Include which tables can be combined, which party sizes need approval and whether bookings cover a whole sitting or a defined period. Where a venue offers both indoor and outdoor seating, establish how each is allocated and what happens if the outdoor area cannot be used.
Then account for every way a table can be taken: the website, telephone, staff entering a reservation, and a customer arriving at the door. If online availability is meant to be current, those routes need to feed a reservation record that staff can keep accurate. Holding back some tables for walk-ins is a separate operating decision; decide who controls that allocation and what the website should say about it.
Choose between a call, a request and live availability
Phone bookings
A call is useful when staff need to discuss arrangements before accepting a reservation. It can also be the simplest route for a small venue that takes relatively few bookings and has someone available to answer. Make the number easy to tap on a phone and state when booking calls can be taken if this differs from opening hours.
Consider the service itself. If the person answering also serves customers, a telephone-only route may be difficult to maintain at busy times. Agree what a caller should do when the phone is unanswered. A request form can provide another route, provided someone is assigned to read and answer it.
A booking request checked by staff
A request form lets the customer send a preferred date, time, party size and contact details for staff to review. It suits arrangements that need a human decision, such as a larger party or a particular table layout. Ask for the information needed to make that decision; a long general enquiry form creates more work for the customer and the person reading it.
Use wording such as “Request a table” and explain that the reservation is confirmed when staff accept it. Set a response expectation the venue can reliably meet. If requests are not monitored during service, make that clear before someone sends a same-day request.
Delivery to an inbox is only part of the workflow. Allocate responsibility for checking the request, recording an accepted booking and sending the answer. The guide to contact-form enquiries not arriving covers delivery faults when submitted messages fail to reach the intended inbox.
Live availability and immediate confirmation
Live availability can let customers choose from the dates and times the venue has released for booking. It suits a team able to maintain availability and use the reservation system consistently, including for calls and changes accepted by staff.
Before choosing this route, establish who can adjust the booking rules, close a sitting and correct a mistake. Ask the supplier to demonstrate how your party sizes, table combinations and booking rules will work.
A live system may handle ordinary reservations while directing larger groups to an enquiry. Make the boundary clear at the point where a customer chooses a party size, rather than allowing them to finish a form that staff cannot accept through that route.
Make the outcome clear at each stage
Customers should be able to tell whether they have sent a request or secured a table. Use different wording for those outcomes. For example, “Your request has been received; we will contact you to confirm availability” suits a manual review. “Your table is confirmed” should appear only when the booking process has actually confirmed the reservation.
A confirmation should give the customer enough detail to check the arrangement: venue, date, arrival time, party size and any agreed sitting duration. Explain how to correct an error or ask for a change. If the booking is held under a reference, show it in the confirmation and use it consistently in the change process.
Plan the unsuccessful routes too. If no online time is available, explain whether the venue welcomes a call about alternatives or whether there is genuinely no availability. An empty online calendar does not, by itself, tell a customer whether walk-ins are possible. Any walk-in message should describe the venue’s actual policy and avoid implying that a table will be waiting.
When a form contains an error, identify the field and explain what needs changing. After a successful submission, give a clear acknowledgement. This follows W3C guidance on form feedback; a customer should not have to guess whether pressing the button worked.
Agree how changes, cancellations and groups will be handled
A change from two guests to six can require a different table arrangement. Decide whether customers can make that change themselves, whether it needs staff approval and how the original reservation is treated while approval is pending. The same question applies to moving a booking to another time.
For cancellations, establish how the customer cancels, where the cancellation appears for staff and when the released capacity becomes available again. If the venue asks customers to telephone for late changes, put that instruction where they will look for it, including the confirmation.
State a sitting duration before the customer confirms if one applies. Agree how the site handles bookings close to the end of a service, and distinguish the last booking time from closing time. These details should come from the venue’s operating policy.
Group meals and private dining often need a separate conversation about the date, numbers, space and arrangements. A short enquiry can collect those starting details and tell the organiser what happens next. Avoid making a general group enquiry look like an accepted table reservation.
If a group pre-orders food, plan the venue’s follow-up as well. FSA best-practice guidance recommends discussing allergen information with individuals on the day; ingredients may have changed or advance details may have been missed.
Separate the website work from reservation management
The website designer can make the booking route visible, explain the choices, style the surrounding page and integrate the selected route within the agreed scope. A reservation system may control availability, table rules, confirmations and booking records. Specify which parts each supplier can change, especially when the booking screen opens on another service.
Choose who owns the account and who receives operational notices. Staff should know where to change opening arrangements and availability without needing an urgent website edit for every adjustment. Agree who investigates a problem when the website button works but the external booking screen fails.
Check the customer journey from the menu as well as the homepage. Someone who has decided what to eat should be able to find the booking route without starting again. The guide to putting a restaurant menu online covers the menu’s layout and update process.
If you display a reservation link on your Google Business Profile, include that route in the handover. Google’s business-link guidance explains that reservation links and third-party provider links can appear there. Check that the public route leads to the intended venue and booking process, particularly after changing suppliers.
Ask for a demonstration of the whole journey
Before launch, agree a controlled demonstration with the supplier, using a test or staging arrangement where available. It should avoid creating real customer reservations or sending messages to unsuspecting people. Ask the designer or reservation provider to show the following cases with the venue’s intended rules:
- An ordinary table booking with the correct date, time and party size carried through to confirmation.
- A request that needs staff approval, with wording that makes its pending status clear.
- A full or closed sitting, including the explanation shown when no time can be selected.
- A party too large for the standard route, directed to the agreed group-enquiry process.
- A change and a cancellation, including the resulting staff record and customer acknowledgement.
- A phone or staff-entered booking, showing how it affects the availability offered online.
Repeat the customer journey on a small phone screen. Read the field labels, select a date and time, correct an error and check the final message. Also ask for a keyboard demonstration of the booking controls; W3C’s keyboard guidance supports making functionality operable without a mouse. A booking widget needs this attention even when the restaurant page around it is easy to use.
Keep the demonstrated cases in the handover, together with the account owner, staff responsibilities and support route. If the booking rules change later, those cases give the team a practical starting point for checking the revised journey.
What to bring to the website brief
Bring your current booking process, table and party-size rules, sitting arrangements, walk-in policy and examples of the messages customers receive. Add the route for group enquiries and the person responsible for maintaining availability. This gives a designer enough detail to scope the website integration and identify the questions a reservation provider needs to answer.
If you run a restaurant or café in Formby, Freshfield or L37, contact Formby Web Design with the booking route you use now and the part you want to improve.
