Case study No. 17
A shorter route back for restaurant reservations follow-ups
When it comes to restaurant reservations, continuing conversations are identifiable without opening the message. Existing customers skip the intake they already completed.
Case docket
- Restaurant Spanish paella restaurant, Tacoma, Washington
- The team 15 staff; one locally managed operation
- Built with Existing-request contact route, Optional reference field, Separate email subjects, New-inquiry form 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
New inquiries and follow-ups on restaurant reservations shared one form. Returning contacts had to pretend to be strangers.
What it cost the team
With restaurant reservations, customers re-entered details we already held, and we spent the first minutes of each reply reconstructing context.
What we built
The fix, in plain terms
Returning contacts get a short form asking for any reference they hold and their question. New inquiries still gather visit date, party size and preferred sitting on their own route, and the subjects make the two instantly distinguishable.
The parts that went in
- Existing-request contact route
- Optional reference field
- Separate email subjects
- New-inquiry form
Timeline
10 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
Returning contacts get a short form asking for any reference they hold and their question.
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 10 working days after content approval.
After
What changed
When it comes to restaurant reservations, continuing conversations are identifiable without opening the message.
Existing customers skip the intake they already completed.
Someone checking on restaurant reservations should not have to introduce themselves from scratch. The separate follow-up option simply makes more sense.
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?
10 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 Spanish paella restaurant get?
Returning contacts get a short form asking for any reference they hold and their question. New inquiries still gather visit date, party size and preferred sitting on their own route, and the subjects make the two instantly distinguishable. The pieces, in the restaurant's own list: existing-request contact route, optional reference field, separate email subjects, new-inquiry form.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: New inquiries and follow-ups on restaurant reservations shared one form. 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 casual and family dining and restaurants that had the same problem.
- Greek taverna-style restaurant, Tulsa, OklahomaA restaurant reservations form that helps people finishFor restaurant reservations, visitors receive a specific instruction when something needs attention and can fix it without starting over.Read the case study
- 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
- Turkish grill restaurant, Tacoma, WashingtonOne guide, read before we talk about restaurant reservationsWhen it comes to restaurant reservations, one link replaces the patchwork of emails.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.