From shared inbox to named owner for seasonal dining menus
When it comes to seasonal dining menus, ownership is no longer a matter of whoever happens to notice first.
- Client
- Japanese ramen and grill restaurant
- Region
- Santa Rosa, California
- Size
- 6 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
Requests about seasonal dining menus landed in a shared inbox that several people watched between other duties. Nobody could see who had taken responsibility for what.
02 · What was going wrong
With seasonal dining menus, some inquiries got two answers and others got none. Vacation cover turned into a forensic exercise through the inbox before anyone dared reply.
03 · What we built
Each request arrives with visit date, party size and menu interest, is assigned to a responsible person, and shows its follow-up state. Cover is arranged in advance, not discovered in a crisis.
04 · What changed
When it comes to seasonal dining menus, ownership is no longer a matter of whoever happens to notice first.
What went into it
- Assignment rules
- Follow-up status
- Backup owner
- Internal request summary
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 demoSeasonal dining menus messages always reached us. What they lacked was a name beside them, and now they have one.
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?
Assignment rules, Follow-up status, Backup owner, Internal request summary. On this site that work sits under reservations and enquiries land where you already work 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 japanese ramen and grill restaurant in Santa Rosa, California, 6 staff; one locally managed operation. The quote is credited to Chetan Mukherjee, front desk 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.