Technology, data and AI

Building a business case for AI call handling

Work out what missed calls and phone time really cost your restaurant or pub, how to value AI call handling, the risks to weigh and a worked Example.

Ava research teamPublished 7 min read

On this page
  1. The three questions a business case must answer
  2. Step 1: measure what the phone is doing now
  3. Step 2: put a value on a missed booking call
  4. Step 3: cost the staff time properly
  5. Step 4: list the risks and running effort
  6. Example: a worked case for a 90-cover restaurant
  7. Numbers to leave out of the case
  8. Step 5: decide, then pilot
  9. Frequently asked questions
  10. References

Key takeaways

  • Start with your own call data: how many calls ring out, when, and what callers wanted.
  • Value a missed call through booking intent, conversion, party size, spend per head and gross profit, not turnover.
  • Cost staff time at the full employer cost, including National Insurance, pension and holiday, not just the hourly wage.
  • Run a time-limited pilot with agreed measures before committing; the biggest risks are wrong answers and poor handovers, not the technology.

The three questions a business case must answer

Most hospitality businesses have not adopted AI at all: 70.7% of UK accommodation and food businesses said they used no AI technology in late September 2026[1]. Among those that had not tried it, the barriers named most often were lack of expertise (8.4%) and cost (6%)[2]. A business case deals with both by replacing a vague sense of 'might help' with numbers from your own venue.

  1. How much revenue, and more importantly gross profit, is lost to calls nobody answers?
  2. How much paid staff time goes on calls that follow a script?
  3. What could go wrong, and what would it take to manage that risk?

If you cannot answer the first two with your own data, the case is not ready. Spend two weeks collecting it before talking to any supplier.

Step 1: measure what the phone is doing now

  1. Pull the call log

    Most VoIP and business phone providers show answered, missed and voicemail calls by hour. Download four weeks if you can, including a busy weekend.

  2. Mark service hours

    Highlight calls during lunch and dinner service. That is where missed calls cluster and where answering costs most in floor time.

  3. Sample the reasons

    For one week, ask whoever answers to tally the reason: booking, change or cancellation, hours and directions, menu or dietary, party or event, supplier, other.

  4. Check callbacks

    How many missed callers rang back, and how many booked online instead? Compare missed numbers with the next day's bookings where you can.

  5. Time the answered calls

    Average length for each reason. Booking calls are often longer than people think once alternatives and dietary notes are discussed.

No log? Ring your own venue at 12.45pm and 7.30pm on a Friday and Saturday from a mobile, three or four times each. It is crude, but it shows whether calls are being answered at peak.

Step 2: put a value on a missed booking call

Use a chain of numbers, each one from your own records or a cautious estimate you can defend. Write the chain down so others can challenge it.

  • Missed calls per week during opening hours.
  • Share of those calls that were booking intent (from your tally).
  • Share of booking callers who would have booked if answered, after allowing for those who called back or booked online.
  • Average party size for phone bookings.
  • Average spend per head for that day part.
  • Gross profit margin on that spend, because the case should be built on profit, not sales.

Multiply through for weekly lost gross profit. Then be honest about uncertainty: run it with a low and a high estimate for the conversion step, which is the weakest number in the chain.

Formula: missed calls × booking share × conversion × party size × spend per head × GP% = gross profit at risk per week.

Step 3: cost the staff time properly

Phone time is usually costed at the wage of whoever answers, which understates it. From April 2026 the National Living Wage for workers aged 21 and over is £12.71 an hour[3], and median pay for waiters and waitresses was £12.81 in April 2026, with restaurant managers at £15.75[4]. On top of pay, employers pay National Insurance at 15% on earnings above the secondary threshold[5], which is £5,000 a year in 2026 to 2027[6], plus at least 3% employer pension contributions on qualifying earnings for auto-enrolled staff[7] and paid holiday.

Median hourly pay for front-of-house and management roles, April 2026Excluding overtime; employer costs come on top.
Median hourly pay for front-of-house and management roles, April 2026Bar chart. Restaurant and catering managers and proprietors: £15.75; Kitchen and catering assistants: £13.02; Waiters and waitresses: £12.81; Bar staff: £12.81.Restaurant and catering managers and proprietorsRestaurant and catering managers and proprietors: £15.75£15.75Kitchen and catering assistantsKitchen and catering assistants: £13.02£13.02Waiters and waitressesWaiters and waitresses: £12.81£12.81Bar staffBar staff: £12.81£12.81Median hourly pay for front-of-house and management roles, April 2026Bar chart. Restaurant and catering managers and proprietors: £15.75; Kitchen and catering assistants: £13.02; Waiters and waitresses: £12.81; Bar staff: £12.81.Restaurant and catering managers andproprietorsRestaurant and catering managers and proprietors: £15.75£15.75Kitchen and catering assistantsKitchen and catering assistants: £13.02£13.02Waiters and waitressesWaiters and waitresses: £12.81£12.81Bar staffBar staff: £12.81£12.81

Source: Office for National Statistics, 2026[4]

Show the data
ItemValue
Restaurant and catering managers and proprietors£15.75
Kitchen and catering assistants£13.02
Waiters and waitresses£12.81
Bar staff£12.81

Example loaded cost. A server paid £12.81 an hour for 30 hours a week earns about £19,984 a year. Employer National Insurance at 15% above £5,000 adds about £2,248, and 3% pension on earnings above £6,240 adds about £412. Most workers on a five-day week are entitled to 5.6 weeks' paid leave[8], so the year has about 1,392 working hours. That puts the real cost at roughly £16.27 per hour worked, 27% above the hourly rate, before Employment Allowance, which can reduce the National Insurance bill for eligible employers[9].

The bigger cost is often not the minutes but when they happen. A manager on a five-minute booking call at 7.30pm is not on the floor, and that is when tables wait for bills, a complaint escalates or a new server needs help. Note those peak-time minutes separately; they are the strongest part of most cases.

Step 4: list the risks and running effort

A credible case shows the downside too. Leaving it out is how projects get approved and then quietly abandoned.

  • Wrong answers: the assistant can only be as accurate as the facts it is given. Someone must own hours, menus and policies and update them the day they change.
  • Bad handovers: if allergen questions or complaints do not reach a person quickly, the guest experience is worse than an unanswered phone.
  • Guest acceptance: some callers dislike automated answering. Tell them up front and give them a quick route to a person.
  • Data protection: call recordings and transcripts are personal data and may include health details. Plan a DPIA, retention period and privacy notice update.
  • Integration effort: ease of integration and use was the factor most often influencing AI use in accommodation and food, cited by 25.5% of businesses using or unsure about AI[10]. Ask what set-up involves for your phone line and booking system.
  • Supplier lock-in: check notice periods, how you get your data out and what happens to your number if you leave.

Example: a worked case for a 90-cover restaurant

Example. A fictional independent restaurant in Manchester logs four weeks of calls. All figures below are illustrative inputs for the method, not benchmarks.

Example inputs for a fictional restaurant; replace every figure with your own.
InputExample valueWhere it came from
Missed calls per week, opening hours38Phone provider log
Share that were booking intent45%One-week tally of answered calls
Would have booked if answered40%Cautious estimate after callbacks
Average party size3.2Booking system, phone bookings only
Average spend per head, dinner£38Till reports
Gross profit margin68%Management accounts
Staff minutes on calls per week420Tally of answered calls
Share of those minutes in peak service55%Tally

Example, continued. 38 missed calls × 45% × 40% gives about 6.8 lost bookings a week. At 3.2 guests, £38 a head and a 68% margin, that is roughly £566 of gross profit at risk each week, or about £29,400 a year. Halve the conversion estimate and it is still around £14,700. Add seven hours a week of staff phone time, about four of them at peak, and the case for handling routine calls automatically is clear enough to justify a pilot, but not so clear that it should skip one.

Numbers to leave out of the case

Some figures make a business case look stronger while making it less believable. Leave them out, or put them in a separate 'possible upside' line that nobody is asked to bank.

  • Lifetime value of a regular. It may be real, but it is unprovable for a single missed call and invites an argument you do not need.
  • Every missed call as a lost booking. Many are suppliers, sales calls and people who will ring back.
  • Headcount savings. Few venues remove a role because the phone is answered; the realistic gain is time and attention at peak.
  • Supplier case studies. Use them to choose questions to ask, not as inputs for your own numbers.

A smaller, defensible number that survives scrutiny from an accountant or a sceptical business partner is worth more than a large one that collapses at the first question.

Step 5: decide, then pilot

Use simple decision rules so the conversation stays on evidence.

  • Go to a pilot if the low estimate of gross profit at risk, plus costed staff time, comfortably exceeds the total cost of the service and the internal effort to run it.
  • Fix the basics first if missed calls are mostly caused by one gap, such as no one on the phone between 3pm and 5pm; a rota change may be enough.
  • Do not proceed if nobody can own the facts list and the handovers. The tool will fail without an owner.

Run the pilot for four weeks with targets agreed in advance: share of calls answered, booking requests captured with complete details, handovers reaching a person within your target time, guest complaints about the phone, and manager minutes on calls at peak. Compare with your baseline log, not with memory.

To shape the shortlist, use questions to ask an AI phone provider. To decide which jobs the assistant should take on, read what an AI employee can take off a manager's plate, and for the digital side of the same problem, website chat for restaurants.

Frequently asked questions

How do I find out how many calls my restaurant misses?

Download the call log from your phone provider, which usually shows missed and voicemail calls by hour. If there is no log, make test calls at peak times and tally reasons for a week.

Should the business case use revenue or profit?

Profit. Use gross profit on the lost spend, because food, drink and variable costs would have been incurred to serve those guests.

What is the weakest number in a missed-call calculation?

The share of missed callers who would have booked if answered. Use a cautious estimate, test a low and high version, and check it during a pilot.

How long should a pilot run?

Four weeks is usually enough to cover different trading days, as long as you have a baseline from before the pilot to compare against.

References

  1. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑

  2. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑

  3. GOV.UK (2026). National Minimum Wage and National Living Wage rates (opens in a new tab) ↑

  4. 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) ↑

  5. ICAEW Library & Information Service (2025). Hospitality: industry profile (opens in a new tab) ↑

  6. HM Revenue & Customs (2026). Rates and thresholds for employers 2026 to 2027 (opens in a new tab) ↑

  7. GOV.UK (2026). Workplace pensions: what you, your employer and the government pay (opens in a new tab) ↑

  8. GOV.UK (2026). Holiday entitlement (opens in a new tab) ↑

  9. HM Revenue & Customs (2026). Rates and thresholds for employers 2026 to 2027 (opens in a new tab) ↑

  10. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo