Tracing seasonal dining menus inquiries to their pages

Day to day with seasonal dining menus, decisions about pages can follow the data the site actually collects. The walkthrough shows measurement being established, not results being promised.

Client
Family-owned Italian restaurant
Region
Savannah, Georgia
Size
9 staff, one locally managed operation
Timeline
15 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

    Inquiries about seasonal dining menus arrived with no hint of their origin. Discussions about what to improve drew on memory rather than evidence.

  2. 02 · What was going wrong

    For seasonal dining menus, content reviews ran on recollection and seniority. The most-read page and the most persuasive page were assumed, wrongly, to be the same.

  3. 03 · What we built

    Each inquiry now records its originating page and service category alongside visit date, party size and menu interest. A basic report separates submitted inquiries from raw visits and keeps reporting apart from sensitive message content.

  4. 04 · What changed

    Day to day with seasonal dining menus, decisions about pages can follow the data the site actually collects. The walkthrough shows measurement being established, not results being promised.

What went into it

  • Originating-page field
  • Service category
  • Inquiry reporting
  • Exclusion of sensitive message text

15working 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

I asked for one number: which page prompts seasonal dining menus contact. We finally have it, and it settled several long-running arguments.

Percy BollingerReservations manager, family-owned Italian restaurantSavannah, Georgia

Questions about this project

How long did this project take?

15 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?

Originating-page field, Service category, Inquiry reporting, Exclusion of sensitive message text. 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 family-owned Italian restaurant in Savannah, Georgia, 9 staff; one locally managed operation. The quote is credited to Percy Bollinger, reservations manager. 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.