Case study No. 02
Restaurant reservations within easy reach on a phone
For restaurant reservations, phone visitors complete the journey the site always intended. Staff share one link during calls instead of describing a route through menus.
Case docket
- Restaurant Mexican cantina restaurant, Tulsa, Oklahoma
- The team 15 staff; one locally managed operation
- Built with Mobile navigation, Short page sections, Visible contact action, Readable text sizing 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
On a desktop the restaurant reservations section was easy enough to browse. On a phone it collapsed into a deep menu, and the contact link hid well below the fold.
What it cost the team
Day to day with restaurant reservations, visitors abandoned the menu halfway and called instead, doubling the work: they browsed, failed, and then called to be guided.
What we built
The fix, in plain terms
The mobile layout was rebuilt around a short navigation path covering an overview, reservation guidance and the current food menu, and a prominent inquiry button. Content blocks were rearranged to match the order visitors actually ask about things.
The parts that went in
- Mobile navigation
- Short page sections
- Visible contact action
- Readable text sizing
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 mobile layout was rebuilt around a short navigation path covering an overview, reservation guidance and the current food menu, and a prominent inquiry button.
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, phone visitors complete the journey the site always intended.
Staff share one link during calls instead of describing a route through menus.
When somebody calls about restaurant reservations, I send one link and tell them exactly where to tap. The guided tour of our menu is no longer part of the call.
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 Mexican cantina restaurant get?
The mobile layout was rebuilt around a short navigation path covering an overview, reservation guidance and the current food menu, and a prominent inquiry button. Content blocks were rearranged to match the order visitors actually ask about things. The pieces, in the restaurant's own list: mobile navigation, short page sections, visible contact action, readable text sizing.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: On a desktop the restaurant reservations section was easy enough to browse. 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: pages that open instantly (on every plan); menu pages built to be read, not downloaded (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.
- Family-owned Italian restaurant, Savannah, GeorgiaFrom printout to page: restaurant reservations made legibleDay to day with restaurant reservations, staff reply with a precise link instead of an attachment.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
- Neighborhood bistro restaurant, Newark, DelawareShowing the working behind restaurant reservationsDay to day with restaurant reservations, the site now argues with evidence the business chose to publish.Read the case study
Related services
- Online menu page designOnline menu page design with sections, prices, dietary marks and daypart availability laid out for a phone, never a PDF or a photo.
- Restaurant website designRestaurant website design built around the menu page, mobile legibility and your own photography, on three managed plans from $117 a month.
- Websites for casual and family restaurantsA website for a casual or family restaurant that keeps hours, kids menus and specials current
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.