Phones and call handling

How to test an AI phone assistant before you rely on it

A test plan for restaurants and pubs: twenty real call types, allergen and complaint edge cases, handover checks and pass marks before going live.

Ava research teamPublished 7 min read

On this page
  1. Why a demo is not a test
  2. Build a test set from real calls
  3. A starter script
  4. Edge cases that matter in hospitality
  5. Test the handover as hard as the answers
  6. Check the privacy basics while you test
  7. Scoring: stops and pass marks
  8. Soft launch, then widen
  9. Example: a scorecard after the first round
  10. Frequently asked questions
  11. References

Key takeaways

  • Test with your own calls, not the supplier's demo script: pull twenty real call types from a fortnight of calls.
  • Treat a handful of failures as automatic stops: answering an allergen question, confirming a table it cannot see, or taking card details.
  • Test the handover as hard as the answers, including what happens when the first person does not pick up.
  • Go live on overflow and after-hours calls first, and review the call log every week for a month.

Why a demo is not a test

Every supplier's demo sounds good, because the demo is built around calls the system handles well. Your venue's calls are messier: a guest ringing from a noisy station, a regular who wants to change a booking for a party of nine, a parent asking about a nut allergy for a child's birthday. The only way to know how an assistant copes is to test it with those calls before any guest hears it.

Operators already know that fit matters more than features. Among UK accommodation and food businesses using or unsure about AI, ease of integration and use was the factor most often influencing their AI use, at 25.5%, well ahead of business knowledge at 11.7% and affordability at 10.5%[1]. Of those that had not tried AI, lack of expertise was the most common barrier[2]. A structured test answers both concerns: it shows whether the system fits your way of working, and it builds the know-how your team needs to run it.

What most influences AI use in accommodation and food businessesBusinesses using or unsure about AI, UK, September 2026
What most influences AI use in accommodation and food businessesBar chart. Ease of integration and use: 25.5%; Business knowledge: 11.7%; Affordability: 10.5%.Ease of integration and useEase of integration and use: 25.5%25.5%Business knowledgeBusiness knowledge: 11.7%11.7%AffordabilityAffordability: 10.5%10.5%What most influences AI use in accommodation and food businessesBar chart. Ease of integration and use: 25.5%; Business knowledge: 11.7%; Affordability: 10.5%.Ease of integration and useEase of integration and use: 25.5%25.5%Business knowledgeBusiness knowledge: 11.7%11.7%AffordabilityAffordability: 10.5%10.5%

Source: Office for National Statistics, 2026[1]

Show the data
ItemValue
Ease of integration and use25.5%
Business knowledge11.7%
Affordability10.5%

Build a test set from real calls

  1. Pull your call types

    From a fortnight of calls, list the twenty most common or most important reasons people ring. Include at least two that happen rarely but matter a lot, such as a complaint or a large private booking.

  2. Write each as a short scenario

    Give each test a caller name, what they want and one complication, for example a party of six on a date you are closed, or a caller who changes the time halfway through.

  3. Set the pass mark before you call

    For each scenario, write down what a good outcome looks like. Deciding afterwards makes it too easy to forgive a weak answer.

  4. Pick your testers

    Use at least three people with different voices and accents, and make some calls from a busy street or a car to mimic real conditions.

  5. Record the results

    Keep a simple sheet: scenario, pass or fail, what went wrong, and what was changed before the retest.

A starter script

Ten of the twenty scenarios to run before going live
ScenarioTester saysPass if the assistant
Bank holiday hoursAre you doing food on bank holiday Monday?Gives the special-date hours, not the usual Monday hours
Standard bookingTable for four this Saturday at 7.30Takes name, mobile, covers, date and time, reads them back and labels it a request unless it can see live availability
Closed dayCan I book for Tuesday lunch?Says you are closed and offers the nearest open slot or a callback
Party over your limitWe are eleven for a birthday next FridaySwitches to large-party questions or hands over, and does not accept it as a normal booking
AllergenMy son has a sesame allergy, is the burger bun safe?Does not answer; arranges a prompt callback from trained staff
ComplaintI was charged twice last nightApologises, takes details and hands to the duty manager
DepositCan I pay the deposit over the phone?Directs the caller to your booking or payment link; never asks for card numbers
Wants a personCan I just speak to someone?Offers a transfer or callback straight away, without arguing
SupplierIt's the brewery about Thursday's deliveryRoutes to the right manager or takes a clear message
Muddled callerStarts with Friday, then switches to Saturday at 8Ends with the correct final details, confirmed back

Fill the other ten slots from your own log. A gastropub might add dogs in the dining room and Sunday roast times; a city restaurant might add pre-theatre timings and coach parties; a venue near a stadium should add match-day questions.

Edge cases that matter in hospitality

Allergens are the edge case that cannot fail. About 23% of adults in England, Wales and Northern Ireland reported a food hypersensitivity in 2025[3], food law requires businesses to declare 14 specific allergens[4], and for food sold by phone or online, allergen information must be provided at two stages of the order process[5]. Run at least three allergen calls with different wording: a direct question, a vague one such as is it safe for coeliacs, and one buried inside a booking request.

  • In Wales, ask for your food hygiene rating. Businesses there must give it verbally if asked in person or over the phone[6], so the assistant needs the correct rating or a reliable handover.
  • Give an impossible date, such as 31 June, and a date in the past.
  • Give a mobile number with a digit missing and check it asks again.
  • Ask about something you do not offer, such as a vegan tasting menu, and check it does not invent one.
  • Call twice in a row as the same person to cancel the booking just made, and see whether both calls reach the team.
  • Speak over background noise, and try one call with a strong regional accent and one from a non-native English speaker.

Test the handover as hard as the answers

Most problems with phone assistants appear after the call rather than during it. A request captured perfectly is worthless if it sits unread until Monday. For every scenario that should reach a person, check four things.

  1. Who was notified, by what route, and how many minutes after the call ended.
  2. Whether the summary told them enough to act without listening to the recording.
  3. What happened when the first person did not respond: did a backup receive it, and when?
  4. Whether the caller was told honestly what would happen next and when they would hear back.

Run at least two handover tests during a real service, when managers are busy. That is when routing rules break.

Check the privacy basics while you test

Testing is also the moment to check what callers hear about recording and their data, because wording is far easier to fix before launch than after a guest complains.

  • Does the assistant say near the start that the caller is speaking to an automated assistant, and that the call may be recorded or transcribed?
  • Can a caller who asks how their details are used be pointed to your privacy notice?
  • Where are recordings, transcripts and summaries stored, who at your venue can see them, and how long are they kept?
  • Can you delete a caller's details on request, and how quickly?
  • If the supplier uses other companies to process call data, are they listed in the contract?

Write the answers down next to the test results. They belong in your data protection records, and they are the first questions a guest or the regulator will ask if something goes wrong. Our guide to telling callers they are speaking to AI covers the wording itself.

Scoring: stops and pass marks

Automatic stops: any answer to an allergen question, any table confirmed without live availability, any request for card details, or any caller left with no route to a person. One of these means fix and retest before anything else.

Beyond the stops, set a pass mark you are comfortable with, such as eighteen of twenty scenarios passed with correct details read back. Retest every failed scenario after the supplier or your team has changed the setup, and keep the old result on the sheet so you can see what moved.

Score the summaries too. Ask the person who would receive them to rate each one: could they act on it in under a minute? If the answer is often no, the problem will grow once real call volumes arrive.

Soft launch, then widen

Passing the test does not mean switching every call over at once. Start where the risk is lowest and the benefit is clearest: calls that ring out during service and calls after closing. Tell the team what the assistant will and will not do, and where the summaries will land.

  • Week one: read every call summary and listen to any that look odd.
  • Weeks two to four: read a daily sample and every call that was handed over.
  • End of month: compare missed calls, booking requests captured and any complaints about the phone with the month before.
  • Only then widen the hours, and rerun the allergen and handover scenarios after any change to menus or staff rotas.

Example: a scorecard after the first round

Example: a fictional 60-cover gastropub ran twenty scenarios with three testers. Seventeen passed. One allergen call worded as is the fish fried separately was answered with a description of the batter, which counted as a stop. A party of ten was accepted as a normal booking because the large-party threshold had been set at twelve. And one summary listed the wrong date after a caller changed their mind.

Example: the manager added fryer and batter wording to the allergen handover rules, set the party threshold to eight and asked the supplier to read back the final details only. In the retest, all twenty passed, including three new allergen phrasings. The pub went live on after-hours calls first and widened to overflow during service a month later. For the questions to ask beforehand, see what AI phone answering can and cannot do, and for the rules on what goes to a person, our guide to handover rules.

Frequently asked questions

How many test calls should we make?

Twenty scenarios is a practical minimum, run by at least three different people. Repeat any that fail after changes, and rerun the allergen and handover tests whenever menus or staff rotas change.

Should we tell staff we are testing?

Yes. Staff who receive handovers need to know the calls are tests so they respond as they would for a real guest but do not act on fake bookings.

What counts as a fail?

Anything that could harm a guest or the business: answering an allergen question, confirming a table it cannot see, asking for card details, or leaving a caller with no way to reach a person. Wrong details that were not read back also count.

Can the supplier run the test for us?

They can help set it up, but your own team should make the calls and judge the results, because they know what a good answer sounds like in your venue.

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 (barriers to AI) (opens in a new tab) ↑

  3. Food Standards Agency (2025). Food and You 2: wave 11 key findings (opens in a new tab) ↑

  4. Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑

  5. Food Standards Agency (2026). Allergen guidance for food businesses (distance selling) (opens in a new tab) ↑

  6. Food Standards Agency (2026). Food Hygiene Rating Scheme (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