Case study No. 07
Every restaurant reservations request has an owner
With restaurant reservations, every inquiry has a name and a state attached to it.
Case docket
- Restaurant Gastropub with dining room, Chandler, Arizona
- The team 15 staff; one locally managed operation
- Built with Assignment rules, Follow-up status, Backup owner, Internal request summary 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
The restaurant reservations inbox belonged to everyone and no one. Messages were monitored between other tasks, with no record of who was handling each one.
What it cost the team
When it comes to restaurant reservations, the inbox rewarded the conscientious and hid the overdue. Nobody could answer the simplest management question: what is still open?
What we built
The fix, in plain terms
Each submission collects visit date, party size and preferred sitting and is assigned to a responsible staff member with a visible follow-up status. A backup contact is named for every request in case the owner is unavailable.
The parts that went in
- Assignment rules
- Follow-up status
- Backup owner
- Internal request summary
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
Each submission collects visit date, party size and preferred sitting and is assigned to a responsible staff member with a visible follow-up status.
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, every inquiry has a name and a state attached to it.
With restaurant reservations, the problem was never receiving the message. It was knowing whose job it was to answer. That part is unambiguous now.
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 gastropub with dining room get?
Each submission collects visit date, party size and preferred sitting and is assigned to a responsible staff member with a visible follow-up status. A backup contact is named for every request in case the owner is unavailable. The pieces, in the restaurant's own list: assignment rules, follow-up status, backup owner, internal request summary.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: The restaurant reservations inbox belonged to everyone and no 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); hosting, security and uptime, handled (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 bars and gastropubs and restaurants that had the same problem.
- Caribbean family restaurant, Chandler, ArizonaResilient contact routes for restaurant reservationsWith restaurant reservations, the new setup gives visitors another way through and gives staff a repeatable check.Read the case study
- Tapas and wine restaurant, Savannah, GeorgiaInstructions included: restaurant reservations after launchDay to day with restaurant reservations, maintenance no longer depends on memory or on any single individual.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
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.