A stronger opening exchange for seasonal dining menus
With seasonal dining menus, the team reading the inbox gets the essentials in the first message and can decide the right follow-up immediately.
- Client
- Modern British restaurant
- Region
- Harrisburg, Pennsylvania
- Size
- 18 staff, one locally managed operation
- Timeline
- 10 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 modern British restaurant had a contact page for seasonal dining menus that amounted to an email link. What arrived depended entirely on what the sender thought to include.
02 · What was going wrong
When it comes to seasonal dining menus, every reply began with the same round of questions just to establish the basics. When the phones were busy, that exchange routinely slipped a full day.
03 · What we built
The inquiry form was rebuilt to collect visit date, party size and menu interest before sending. Arrivals follow a fixed, readable format, carry a category label and set expectations by naming a reservation discussion with the host team as the next step.
04 · What changed
With seasonal dining menus, the team reading the inbox gets the essentials in the first message and can decide the right follow-up immediately.
What went into it
- Purpose-specific fields
- Readable notifications
- Clear response expectations
10working 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 demoThe first message about seasonal dining menus finally tells me why someone is getting in touch. It is basic, and it was exactly what we were missing.
Questions about this project
How long did this project take?
10 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?
Purpose-specific fields, Readable notifications, Clear response expectations. On this site that work sits under reservations and enquiries land where you already work, which is 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 modern British restaurant in Harrisburg, Pennsylvania, 18 staff; one locally managed operation. The quote is credited to Vijay Kulkarni, front of house supervisor. 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.