An FAQ built from real seasonal dining menus conversations
When it comes to seasonal dining menus, there is one place to check how something works, for customers and colleagues alike. Everyday queries are answered on the page; anything specific is still settled person to person.
- Client
- Steakhouse and grill restaurant
- Region
- Tacoma, Washington
- Size
- 9 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
Replies to seasonal dining menus questions lived in individual inboxes and habits. The explanation a caller received depended on who happened to pick up.
02 · What was going wrong
With seasonal dining menus, customers called for details a paragraph could have settled, and new colleagues learned by trial and error. The same explanation was rewritten weekly, never identically.
03 · What we built
Recurring questions were gathered into a focused FAQ covering the current menu and staff-reviewed dietary guidance. The staff member responsible for each subject checked its answer, and anything needing individual advice is directed to a conversation instead.
04 · What changed
When it comes to seasonal dining menus, there is one place to check how something works, for customers and colleagues alike. Everyday queries are answered on the page; anything specific is still settled person to person.
What went into it
- Staff-reviewed FAQ
- Topic grouping
- Named content owner
- Contact links for individual questions
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 demoEvery answer on the seasonal dining menus page was checked by the person who owns that subject here. It reads like us because it is us.
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?
Staff-reviewed FAQ, Topic grouping, Named content owner, Contact links for individual questions. On this site that work sits under menu pages set like a printed menu and revisions built for a menu that changes, 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 steakhouse and grill restaurant in Tacoma, Washington, 9 staff; one locally managed operation. The quote is credited to Miriam Montgomery, host team lead. 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.