Case study No. 10
Three doors instead of one for restaurant reservations
For restaurant reservations, messages arrive pre-sorted by the person best placed to sort them: the sender. New business and existing conversations no longer compete for attention in one queue.
Case docket
- Restaurant Steakhouse and grill restaurant, Roanoke, Virginia
- The team 9 staff; one locally managed operation
- Built with Contact categories, Separate follow-up route, Relevant form fields, Clear button labels 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
Everyone interested in restaurant reservations was funneled to one general contact page, whether they had a brand-new request or a question about an existing one.
What it cost the team
Day to day with restaurant reservations, subjects told staff nothing. Separating a fresh inquiry from an existing conversation required reading everything, every time.
What we built
The fix, in plain terms
The contact page opens with a plain three-way choice and routes each selection appropriately. New inquiries gather visit date, party size and preferred sitting; follow-ups take a shorter form.
The parts that went in
- Contact categories
- Separate follow-up route
- Relevant form fields
- Clear button labels
Timeline
15 working days, from sign-off to handover
Content approved
The working-day count starts once the restaurant has signed off the content that goes on the page.
Built
The contact page opens with a plain three-way choice and routes each selection appropriately.
Staff review
The restaurant's own team checked the work against how they actually take inquiries before anything went live.
Handed over
Live and handed over 15 working days after content approval.
After
What changed
For restaurant reservations, messages arrive pre-sorted by the person best placed to sort them: the sender.
New business and existing conversations no longer compete for attention in one queue.
The restaurant reservations routes mirror the reasons people actually contact us. Our inbox finally reflects reality instead of hiding it.
Is your inquiry form costing you mornings too?
Show us your current site on a live walk-through and we will point at the first thing we would fix, and say so if it is not the website at all.
Questions about this project
How long did this project take?
15 working days after content approval, including staff review and handover. On our plans a new site goes live in 7 days on The Daily Menu, 10 on The Full Menu and 15 on The Tasting Menu, counted from the onboarding call.
What exactly did the steakhouse and grill restaurant get?
The contact page opens with a plain three-way choice and routes each selection appropriately. New inquiries gather visit date, party size and preferred sitting; follow-ups take a shorter form. The pieces, in the restaurant's own list: contact categories, separate follow-up route, relevant form fields, clear button labels.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: Everyone interested in restaurant reservations was funneled to one general contact page, whether they had a brand-new request or a question about an existing one. The quickest way to tell is a demo call, where we look at your current site and say plainly whether this is the fix it needs or whether something else matters more.
Is this part of a plan, or an extra?
It is part of building and running the site. The site features this project used: reservation and ordering links that just work (on every plan). Plans start at $117 a month, the $647 build fee is invoiced only after launch, and 5 revisions a month are included.
More case files
Related case studies
More projects for fine dining and restaurants that had the same problem.
- Modern British restaurant, Billings, MontanaRepairing the opening step of restaurant reservationsWhen it comes to restaurant reservations, staff can act on the first message instead of the third.Read the case study
- Indian restaurant with private dining, Worcester, MassachusettsWhat restaurant reservations covers, and what it does notFor restaurant reservations, the distinction between asking and agreeing is now explicit.Read the case study
- French provincial restaurant, Billings, MontanaOut-of-hours restaurant reservations, handled honestlyWhen it comes to restaurant reservations, the day now starts with structured requests.Read the case study
Related services
See the site you would get
About 30 minutes, on your screen, built around your menu and how your team takes bookings. Plans from $117 a month, with the $647 build fee invoiced only after launch.