Bookings, menus, online ordering, search. Written by the people building the product, between services.
When the booking page, the email and the phone answer each describe the deposit differently, a late cancellation turns into an argument over wording.
When a restaurant's photos live on other people's pages, the first look at the room is out of its hands and often stale. A gallery on its own website puts it back.
When the table plan lives on a whiteboard, a party of six can arrive to the wrong tables. Draw the room once, set each table's seats and count bookings by table.
Guest details spread across a diary, a notebook and a spreadsheet drift apart and go stale. One searchable list, built from bookings, keeps regulars, notes and VIPs together.
Sign-ups that sit unused cost repeat visits, and a Christmas email with every address in CC can leak the whole list. Write, test and send it to consented guests instead.
A menu link on an address the restaurant does not control is a quiet risk. On Growth, buying its own name takes a search, an owner form and a card payment, with no DNS.
A handwritten order can miss a required choice, lose a kitchen note or sell a dish that has run out. Ring it at the table on the screen that holds its bill.
Guests check the wine list on a phone before they book. When it is a photo or a PDF, the glass and bottle prices are the first thing to go missing.
Questions a confirmation never answers become calls during service and wrong assumptions at the door. Rewrite it, restyle it and send it in the restaurant's own name.
A phone-only diary costs paid time and leaves allergies on scraps of paper. Set the service rules, add the form, publish, then find the first booking in the Inbox or diary.
A guest who has already chosen you can lose the way to a listing full of other restaurants. Check your details once, add a map, publish, then watch the calls and directions counts.
A paper stamp card gets lost and a regular rebooks through someone else's app. Build a guests' app on your own site, section by section, and publish it when it reads right.
