Skip to main content

Cremona Bistro

The Menu Online, And A Phone That Answers While The Floor Is Busy

Two systems delivered to an Italian restaurant: a website designed, built and launched, and a voice agent taking the calls so the floor staff can work the floor.

Industry
Restaurants + food
2Systems delivered: the website and the voice agent on the phone
LiveStatus of the site, designed, built and launched
Delivered

The challenge

Cremona Bistro is an Italian restaurant. Two things were working against it, and they look unrelated until you watch a full service.

The first is the menu. A diner choosing where to eat tonight is reading dishes, and a menu that arrives as a scanned document or a cramped listing inside somebody else’s platform is asking that person to do the imagining themselves. Most of them will not.

The second is the phone. A restaurant phone rings hardest during service, which is precisely when nobody can stand still to answer it. Every call taken is a table neglected, and every call missed is a booking or an order that went somewhere else. The staff are not doing anything wrong. They are being asked to be in two places at the same time.

What we built

The website. A restaurant-appropriate site, designed, built and launched, with the menu presented the way the food deserves rather than as a text dump. The menu is the reason people open a restaurant’s website at all, so it is treated as the main event rather than as a page buried behind the story of the family.

The voice agent. An agent that answers the phone, so the floor staff can work the floor. That is the whole brief and it is deliberately narrow. The value is not that a machine talks. It is that a server is no longer choosing between the guest in front of them and the caller on hold.

One thing belongs on this page in plain type. Nothing in this engagement

was instrumented against a baseline, so there is no call volume, no booking count and no traffic figure to report for Cremona Bistro. Two systems were delivered and the site is live. That is the honest extent of it, and padding it out with numbers nobody measured would make the rest of this portfolio worth less.

The deliverables

  • A restaurant-appropriate website, designed and built
  • The menu presented the way the food deserves rather than as a text list or a PDF
  • The launch itself, shipped and live
  • A voice agent answering the restaurant's phone

The results

2
Systems delivered: the website and the voice agent on the phoneMeasured 2026
Live
Status of the site, designed, built and launchedMeasured 2026

Why it worked

Because the two systems fix the same problem at two different moments.

Someone deciding where to eat reads the menu first, and a menu presented badly costs the restaurant that decision before anyone has picked up a phone. Someone who has already decided then calls, usually at the exact hour the room is at its busiest and nobody can afford to stand still holding a handset. One is a presentation problem and the other is a staffing problem, and a restaurant that solves only one keeps losing the other.

Neither of them is a kitchen problem, which is the point. Nothing here touches the food or the service, and both were left alone deliberately.

The takeaway

If you run a restaurant, do two checks this week. Open your own menu on a phone, the way a stranger would at seven in the evening, and see whether it reads like your food or like a document. Then call your own number during your busiest hour and count how long it rings.

Those two checks cost nothing and they tell you exactly where you are losing tables. The fix is ordinary and it is the same fix Cremona Bistro got: put the menu somewhere it can be read, and put something on the phone that answers when the room cannot.

Questions people actually ask

Why does a restaurant need a website when it is already on delivery apps and maps?

Because the menu is what people came to read. Cremona Bistro's site was built to present the menu the way the food deserves, on a page the restaurant controls, rather than as a scanned PDF or a listing squeezed into someone else's template. A diner deciding where to eat tonight is reading dishes, not a profile.

What happens to the phone when a voice agent is on it?

It stops competing with the dining room. At Cremona Bistro the agent answers, which means the floor staff can work the floor instead of choosing between the person at the table and the person on the line. A restaurant phone rings hardest exactly when the room is fullest, which is the worst possible moment to ask a server to pick up.

Was any of this measured?

No, and the page says so rather than filling the gap. Nothing on this engagement was instrumented against a baseline, so there is no call count, no booking count and no traffic figure for Cremona Bistro. Two systems were delivered, the site is launched, and that is the whole of what can be honestly claimed here.