Key takeaways
- Centralise when sites keep missing calls at the same times, events enquiries are slow, or standards vary between venues.
- Start with overflow or event calls before moving every call to the centre; sites keep their own numbers.
- Size the team from your call logs: calls per hour, minutes per call and the answer rate you want.
- The handover to each site is the make-or-break part: daily availability, clear escalation and notes the floor can read.
When centralising makes sense
A single restaurant can usually manage its own phone with a good rota and voicemail. Once a business runs several sites, patterns appear that no single site can fix: the same peak-hour misses at every venue, event enquiries that wait days for a manager, and guests who get different answers depending on which site they ring.
Multi-site operators are a significant part of hospitality. ONS counted 36,015 pubs, bars and licensed clubs operating from 43,685 premises in the UK in 2026[1]. Managed groups are also trading reasonably: in September 2026 managed restaurant groups grew like-for-like sales by 2.6%, their best month since November 2024[2]. Growth makes the phone harder to cover, not easier.
Source: NIQ (CGA by NIQ) with RSM, 2026[2]
Show the data
| Item | Value |
|---|---|
| All managed groups | 2.7% |
| Restaurant groups | 2.6% |
| Pub groups | 3.8% |
These are the signs a central team would help.
- Every site misses calls in the same hours, usually evening service and Sunday lunch.
- Event and Christmas enquiries take more than a day to get a reply.
- Site managers spend hours a week on the phone instead of the floor.
- Guests get different answers on deposits, large parties or dogs depending on the site.
- You cannot see call volumes or missed calls across the group.
Choose a model
Centralising does not have to mean moving every call to a central team. Most groups do better starting small and expanding.
| Model | How calls flow | Good for | Risk |
|---|---|---|---|
| Site only | Each site answers its own calls | Small groups with strong site teams | Peak-hour misses and inconsistent answers |
| Overflow to centre | Site answers first; unanswered calls go to the centre after a few rings | Groups that want to keep the local feel | Central team must know every site well |
| Events to centre | Large parties, private hire and Christmas go straight to the centre | Groups with a big events trade | Hand-off to the site for the day itself |
| Central first | All booking calls go to the centre; sites get transfers | Larger groups with similar sites | Losing regulars and local knowledge |
A common path is to start with events to the centre and overflow from the sites, then decide after a few months whether a central-first model is worth it.
Size the team from your own data
Do not guess the number of people you need. Work it out from your call logs, by hour, for a typical week and a peak week.
Pull call logs for every site
Count inbound calls by hour for each day of the week, after removing repeats and supplier calls.
Decide which calls move
Overflow only, events only, or everything. Count only the calls the centre will take.
Measure minutes per call
Include the after-call work, such as entering the booking and sending the confirmation.
Work out workload
Calls in the hour multiplied by minutes per call, divided by 60, gives the number of people fully busy in that hour.
Add headroom
Calls do not arrive evenly. Staff above the workload figure so callers are not left waiting, and more so in peak hours.
Build the rota
Cover the busiest hours first, then decide how far into quieter hours to extend.
Example: a fictional group of five restaurants finds the centre would receive 48 overflow and event calls in its busiest evening hour, each taking about four minutes including the booking entry. That is 192 minutes of work in a 60-minute hour, so just over three people fully busy. With headroom for calls arriving in bursts, the group rosters four or five people for that hour and two in the quieter afternoon.
Recheck the sizing after the first month using the centre's own logs. Calls change once guests learn that someone always answers.
What it costs and who to hire
A central reservations agent needs to know the venues, the booking system and the group's terms, and to sound like they work at each site. For reference, ONS reported median hourly pay of £15.75 for restaurant and catering establishment managers and proprietors in April 2026[3]. Set reservations pay against your own front-of-house and supervisor rates, reflecting the responsibility for every site's bookings.
Recruitment is not easy. Payrolled hospitality employment fell by 72,000 in the twelve months to August 2025[4], and experienced front-of-house staff are in demand. Many groups recruit central agents from their own sites: people who already know the venues and the regulars, and who want a daytime or more predictable rota.
What the centre needs from each site
The central team is only as good as the information it has. Agree a daily rhythm with each site so the centre is never guessing.
- Live access to the site's booking system, with the correct table plan and limits.
- A fact sheet per site: hours, directions, parking, dogs, children, accessibility, set menus and events spaces.
- A daily note of anything unusual: private hire, closed sections, staff shortages, menu changes.
- Who to call at the site for allergen questions, complaints and regulars on each shift.
- Events capacity and the manager who confirms large bookings.
- A named contact at the site who owns the relationship with the centre.
The handover to each site
Most central reservations problems happen at the handover: a note the floor does not see, an allergy that never reaches the kitchen, a regular who feels passed around. Make the handover explicit.
- Write booking notes in a standard format so any site can read them at a glance.
- Flag allergies and dietary needs in a field the kitchen sees, not in free text.
- Pass complaints to the site manager the same day, with the guest's details and what was said.
- Transfer regulars who ask for someone they know, rather than insisting the centre handles it.
- For events, introduce the site manager to the organiser before the day, by email or a short call.
- Send each site a daily list of bookings and enquiries taken by the centre, so nothing surprises them.
Train the team on every venue
A central agent who has never eaten at the site they are selling will sound like it. Build venue knowledge into training from the first week, and keep refreshing it.
- Send each new agent to eat at every site, and to shadow a host during a busy service.
- Give them the same booking script as the sites, adapted for answering on behalf of several venues.
- Walk through each site's table plan, so they know which tables suit a wheelchair user, a pram or a group of eight.
- Agree how they answer: in the name of the site the guest rang, with the agent's first name.
- Practise transfers and callbacks to sites, including what to say when a site manager is unavailable.
- Brief them on every menu change, special event and seasonal menu before it goes live.
Rotate agents through the sites a few times a year. Venue teams also benefit from knowing the voices on the other end of the line.
Mistakes groups make when they centralise
Central reservations can go wrong in predictable ways. Most of them come from treating it as a cost-saving exercise rather than a guest-service one.
- Moving every call to the centre on day one, before the team knows the venues.
- Replacing each site's number with a single group number, so regulars cannot reach the venue they know.
- Giving the centre read-only access to booking systems, so every booking becomes a message to the site.
- No clear escalation, so complaints and allergen questions bounce between the centre and the site.
- Measuring only call volume, not whether bookings and enquiries actually turned into covers.
- Forgetting that sites still need to answer some calls, and letting their phone habits lapse.
A phased rollout over about three months avoids most of these: events first, then overflow from the busiest sites, then a decision on whether to go further.
Numbers, routing and measurement
Keep each site's own local number, and point overflow and events to the centre through your phone system's routing. If you want one number for the whole group's events and Christmas bookings, an 03 number is a good fit; our guide on local, 03 and 0800 numbers explains the differences.
Measure the centre weekly against a few clear numbers: answer rate by hour, average time to answer, booking requests taken, events enquiries returned within a working day, and complaints passed to sites. Christmas is the real test: NIQ describes Christmas and New Year as hospitality's crucial trading period[5], and that is when event enquiries, changes and deposits peak. Plan extra cover from early autumn, not December.
Frequently asked questions
How many sites do you need before central reservations make sense?
There is no fixed number. It depends on call volume, how similar the sites are and whether you have a large events trade. Some groups start with three or four sites by centralising only events and overflow calls, and expand once the team proves itself.
Should central reservations answer every call?
Usually not at first. A common model is that each site answers its own calls during service, overflow goes to the central team after a few rings, and all event and large-party enquiries go to the centre from the start.
Do central teams need to work from head office?
No. Many work remotely or from one of the sites. What matters is access to every site's booking system, a shared phone system with queues and logs, and a fast way to reach each site's manager.
How do we keep the local feel if calls go to a central team?
Answer in the name of the site the guest rang, give the central team a current fact sheet for each venue, and pass regulars and complaints to the site. Visit each venue regularly so the team knows what they are selling.
References
Office for National Statistics (2026). UK business: activity, size and location, 2026 (workbook) (opens in a new tab) ↑
NIQ (CGA by NIQ) with RSM (2026). Bright September gives hospitality groups their best growth of 2026 (NIQ RSM Hospitality Business Tracker) (opens in a new tab) ↑
Office for National Statistics (2026). ASHE 2026 provisional, Table 14.6a: hourly pay excluding overtime by occupation (SOC 2020), all employees (opens in a new tab) ↑
Low Pay Commission (2025). National Minimum Wage: Low Pay Commission Report 2025 (opens in a new tab) ↑
NIQ (CGA by NIQ) (2026). Hospitality loses 19 licensed premises a week ahead of crunch Christmas (Hospitality Market Monitor Q3 2026) (opens in a new tab) ↑