A fallback for when the seasonal dining menus form fails
When it comes to seasonal dining menus, a bad day is now an inconvenience rather than a lost customer.
- Client
- Tapas and wine restaurant
- Region
- Santa Rosa, California
- Size
- 12 staff, one locally managed operation
- Timeline
- 20 working days
How it went, course by course
Four stages, in the order they happened, in the words the project was recorded in.
01 · Where they started
The seasonal dining menus inquiry route was a single point of failure. A broken form meant a lost customer and nobody the wiser.
02 · What was going wrong
With seasonal dining menus, failures were invisible from both sides: customers could not report them, and the team had no test that would reveal them.
03 · What we built
An alternative contact route now sits openly on the page, alongside errors that explain themselves and guidance for follow-up messages. A delivery check exercises the real form, including visit date, party size and menu interest, to confirm mail reaches its destination.
04 · What changed
When it comes to seasonal dining menus, a bad day is now an inconvenience rather than a lost customer.
What went into it
- Alternative contact method
- Useful failure message
- Form delivery check
- Staff escalation contact
20working days
The time it took
After content approval, including staff review and handover. A new site goes live in 7 days on The Folio; work like this runs through your monthly revisions or alongside the build.
Book a demoIf a seasonal dining menus request cannot go through, people can see another way to reach us. I am glad it was considered before we needed it.
Questions about this project
How long did this project take?
20 working days after content approval, including staff review and handover. The clock starts once the restaurant has approved the content, so the time is spent building and checking rather than waiting on copy.
Which parts of the offer did it use?
Alternative contact method, Useful failure message, Form delivery check, Staff escalation contact. On this site that work sits under reservations and enquiries land where you already work and hosting, security and uptime, handled, which are included on every plan from The Folio up.
Why is the restaurant not named?
We describe each client by the kind of restaurant it is and where it is: here, a tapas and wine restaurant in Santa Rosa, California, 12 staff; one locally managed operation. The quote is credited to Russell Millington, guest relations coordinator. We never publish a trading name, address, logo or photograph.
Could the same work fit our restaurant?
If guests read your pages or send you inquiries before they visit, most likely. Nothing here was a custom add-on: plans start at $117 a month, the $647 build fee is invoiced only after launch, and a walk-through on your own menu shows what the equivalent would look like for you.
See what this would look like on your menu
A live walk-through of the site you would get, in about 30 minutes. Plans from $117 a month, the $647 build fee invoiced only after launch, domain and hosting included.
Or compare the plans and pricing first.