A side door for seasonal dining menus follow-ups

With seasonal dining menus, subjects now announce what a message is. Follow-ups reach the right thread quickly, and existing customers stop re-introducing themselves.

Client
Thai family restaurant
Region
Chandler, Arizona
Size
6 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.

  1. 01 · Where they started

    The website offered the same inquiry form to first-time visitors and to people chasing an existing seasonal dining menus request.

  2. 02 · What was going wrong

    When it comes to seasonal dining menus, every follow-up created a small mystery: who is this, and what were we discussing? The answers lived somewhere in the inbox, and finding them took time.

  3. 03 · What we built

    Returning contacts now have a short path: reference if available, then the question. New inquiries still gather visit date, party size and menu interest on their own route, and subjects keep the streams apart.

  4. 04 · What changed

    With seasonal dining menus, subjects now announce what a message is. Follow-ups reach the right thread quickly, and existing customers stop re-introducing themselves.

What went into it

  • Existing-request contact route
  • Optional reference field
  • Separate email subjects
  • New-inquiry form

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 demo

Our seasonal dining menus customers have a history with us; the site finally acknowledges it. The follow-up route treats them like the returning contacts they are.

Martha StantonDining room supervisor, thai family restaurantChandler, Arizona

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?

Existing-request contact route, Optional reference field, Separate email subjects, New-inquiry form. 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 thai family restaurant in Chandler, Arizona, 6 staff; one locally managed operation. The quote is credited to Martha Stanton, dining room 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.