Case study No. 11
Local routing built into restaurant reservations
With restaurant reservations, staff no longer begin calls by discovering the caller belongs to another branch. The routing happens on the page, before anyone picks up a phone.
Case docket
- Restaurant Vegetarian and vegan restaurant, Reno, Nevada
- The team 12 staff; one locally managed operation
- Built with Local contact panel, Location selection, Location-aware notifications, Opening hours 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
A single page covered restaurant reservations for every location. Working out which phone number or inbox applied was the visitor's problem.
What it cost the team
When it comes to restaurant reservations, first-contact calls landed anywhere. Staff transferred politely, customers repeated themselves, and the form knew nothing of branches.
What we built
The fix, in plain terms
Local contact details now sit beside the service description they belong to. The inquiry carries the selected location into the staff notification, together with visit date, party size and preferred sitting.
The parts that went in
- Local contact panel
- Location selection
- Location-aware notifications
- Opening hours
Timeline
20 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
Local contact details now sit beside the service description they belong to.
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 20 working days after content approval.
After
What changed
With restaurant reservations, staff no longer begin calls by discovering the caller belongs to another branch.
The routing happens on the page, before anyone picks up a phone.
Our internal map used to be the customer's homework. The restaurant reservations page does that work for them.
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?
20 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 vegetarian and vegan restaurant get?
Local contact details now sit beside the service description they belong to. The inquiry carries the selected location into the staff notification, together with visit date, party size and preferred sitting. The pieces, in the restaurant's own list: local contact panel, location selection, location-aware notifications, opening hours.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: A single page covered restaurant reservations for every location. 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: a page for every location you run (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 multi location groups and restaurants that had the same problem.
- Seafood restaurant by the marina, Worcester, MassachusettsWhere restaurant reservations inquiries really come fromFor restaurant reservations, the team can now ask which pages persuade, not just which attract.Read the case study
- 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
- Mexican cantina restaurant, Tulsa, OklahomaRestaurant reservations within easy reach on a phoneFor restaurant reservations, phone visitors complete the journey the site always intended.Read the case study
Related services
- Multi location restaurant websitesMulti location restaurant websites with one page per address, shared and per-location menus, and consistent name, address and phone details.
- Local restaurant website designLocal restaurant website design built for the search someone runs standing nearby: hours, menu, directions and a way to book or order fast.
- Websites for multi location restaurant groupsA website for a multi location restaurant group where every address ranks on its own
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.