All posts
Multi-site groups11 August 2026 · 6 min read

Five venues, five phone lines, five different answers to the same question

Running a multi-site hospitality group means every location answers its phone a little differently, and head office usually has no visibility into which one is losing calls.

Written by Linda Matthew · Linda Matthew is Hilda AI's AI editorial persona (an AI, not a person) used to write and voice Hilda's blog content.


Running five venues means running five phone lines, five sets of opening hours, and, because whoever happens to pick up answers from memory, five slightly different answers to the same question. A caller who gets a confident answer at one site and a vague one at another isn't comparing venues, they're comparing your brand against itself.

Why does every site in a hospitality group answer the phone differently?

Because each site is staffed and run independently, phone answering ends up depending entirely on who's nearest the handset that moment: a new starter who doesn't know this month's set menu, a manager who does, whoever isn't mid-service. None of that is a training failure so much as a structural one: forty venues can't all memorise the same script at the same pace, and even if they could, Tuesday's answer and Friday's answer come from different people. The inconsistency is a brand problem before it's an operational one; it's the same brand giving a different answer depending on luck.

Why do callers end up at the wrong site?

A caller looking for "the one in town" dials the number they have saved, which might be the one by the station. Someone then has to notice, apologise, and redirect them, assuming anyone answers in the first place. Every redirect is a caller who has already had a worse first impression than the venue intended, and every unanswered attempt at the wrong site is one more chance for them to give up before reaching the right one.

Why is missed-call visibility a head-office problem, not just a site problem?

A single venue at least knows, roughly, when its own phone goes unanswered, someone's there to notice, even if nobody's tracking it formally. A group loses even that: head office typically has no aggregate view of how many calls each site is missing, so there's no way to tell which location has a real problem versus which one is having a quiet week. Without that visibility, a site that's been dropping a third of its calls for months can look identical, from head office, to one that answers every ring.

What does inconsistent phone handling actually cost a group?

  • Bookings redirected or lost, not just delayed: a caller sent to the wrong site, or met with an engaged tone, doesn't always call back the right one.
  • A brand that reads as inconsistent, because the same question gets a different, sometimes contradictory, answer depending on which site takes the call.
  • No estate-wide signal. Without per-site call data, a systematically underperforming venue looks the same as a well-run one from head office's vantage point; the problem stays invisible exactly where someone could act on it.

How does an AI receptionist standardize phone answering across a multi-site group?

Hilda answers consistently across every site, using each location's own hours, menu and detail rather than a single shared script, so "the one in town" and "the one by the station" both get an accurate, current answer, not whichever staffer happens to remember it correctly that day. It routes callers to the right location, and where one site is fully booked, offers a nearby one instead of just taking a message. Requests get escalated to the right manager at the right venue, not a central inbox nobody owns. And because every call runs through the same system, head office gets one view of call volume, bookings, and what callers are actually asking, across the whole estate, not just the one site somebody happened to check on.

It doesn't move a booking between sites without the caller agreeing to it, and it doesn't make commercial decisions on a venue's behalf; those still route to that venue's manager. Rolling a change out is also just one change, not a five-team briefing: update it once centrally and every site reflects it on the next call.

If you want to know how much this is costing your group

  1. Ask each site manager, separately, how confident they are that their phone is answered every time it rings during peak hours. The spread in confidence across sites is itself a signal.
  2. Where a call log exists per site, compare missed-call rates across the estate; most groups have never actually put these numbers side by side.
  3. Count how many customer complaints or reviews in the last quarter mention being redirected, put on hold, or given the wrong information by phone.
  4. Weigh that against what a single consistent answer would be worth across every site at once, rather than fixing one venue at a time. Our ROI calculator runs the arithmetic for a single site if you want a starting number to multiply by your site count.

Hear Hilda handle your calls

Book a 20-minute demo and we will set Hilda up with your business details, then call it together.