Restaurant Technology and AI

DIY AI Phone Agent vs a Managed Service

What building your own restaurant voice agent really takes (phone setup, menu data, testing, monitoring, consent rules) set against a managed service.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. Hello is the easy part
  2. The parts list, and who owns each
  3. Where homemade agents break on restaurant calls
  4. Consent, recording and disclosure are yours too
  5. The monthly cost of running it yourself
  6. Side by side
  7. When building it yourself makes sense
  8. Five questions before you start building
  9. Frequently asked questions
  10. References
Restaurant Technology and AI: DIY AI Phone Agent vs a Managed Service46.1%: of restaurant operators name complexity as a top concern about AI, ahead of costRESTAURANT TECHNOLOGY AND AIDIY AI Phone Agent vs aManaged Service46.1%of restaurant operators name complexity as a topconcern about AI, ahead of costAva for RestaurantsInsightsRestaurant Technology and AI: DIY AI Phone Agent vs a Managed Service46.1%: of restaurant operators name complexity as a top concern about AI, ahead of costRESTAURANT TECHNOLOGY AND AIDIY AI Phone Agent vsa Managed Service46.1%of restaurant operators namecomplexity as a top concern about AI,ahead of costAva for Restaurants
Figure source: National Restaurant Association, 2026[1]

Key takeaways

  • Getting a voice agent to say hello takes an afternoon. Getting it through a noisy Saturday call with a party of nine and a nut allergy is the real build.
  • A homemade agent makes you the owner of every part: phone line, speech, voice, instructions, handoffs, records, recording notices and fixes.
  • Speech recognition is not equally accurate for every caller[2], so test with the voices and phone lines you actually get.
  • The running cost is your manager's review time and on-call duty. Build only if someone can own both.

Hello is the easy part

The builder demos make it look like an afternoon's work: paste in the menu, pick a voice, connect a number, call it. That part really is quick. The work starts when a guest rings at 7:40 on a Saturday from a car with a weak signal, asks for a table for nine, mentions a nut allergy halfway through and talks over the agent twice. A restaurant phone agent earns its keep on that call, and it has to leave your host something usable when it hangs up.

A working agent is a chain of parts: a phone number or forwarding rule, speech recognition, a language model that decides what to say, a synthetic voice, your house information, rules for handing calls to staff, somewhere to keep recordings and transcripts, alerts for the team, and the greeting that tells callers they are speaking to an automated system and that the call is recorded. Build it yourself and you choose, pay for and keep every link in that chain working.

Example: a do-it-yourself build, start to go-live
  • Your team
  • System
  1. 01Your team

    Choose the parts

    Number, speech, voice and model, each from a provider you pick and pay.

  2. 02Your team

    Write the instructions

    Hours, policies, menu facts, and the answers it must never guess.

  3. 03System

    Wire the handoffs

    Transfers, a backup when nobody picks up, and where records go.

  4. 04Your team

    Test real calls

    Kitchen noise, accents, interruptions, odd requests, bad signal.

  5. 05Your team

    Go live and keep watch

    Read transcripts, fix answers, track every provider's changes.

Example sequence. The last step never ends, which is the part most build estimates leave out.

The parts list, and who owns each

Who carries each part of a restaurant voice agent under each approach.
PartBuild it yourselfManaged service
Phone line and forwardingBuy a number or set up forwarding; handle outagesForwarding rules agreed and tested with you
Speech and voicePick providers, tune for noise and accentsChosen and maintained by the service
InstructionsWrite prompts and keep them currentYou approve the facts and boundaries; the service builds the script
Handoffs to staffBuild transfers, backups and a no-answer stepSet from the manager path you choose
Records and alertsStore recordings and transcripts, write summaries, send alertsSummary by email; recording and transcript in the account
Recording notice and disclosureWrite it and check it against each state's rulesA greeting with the notice, approved by you
Monitoring and fixesYour evenings and weekendsThe service's support, plus your weekly review

Operators already know where this pinches. In the National Restaurant Association's November 2026 research, complexity was the most cited concern about AI at 46.1%, ahead of cost at 43.5% and customer acceptance at 41.9%[1]. Only 3.2% of operators were implementing AI projects companywide, while 20% were running small pilots, and training and education topped the list of support operators wanted, at 56.5%[1]. A build adds to every one of those pressures.

Restaurant operators' top concerns about AIShare of US restaurant operators naming each concern, National Restaurant Association, November 2026.
Restaurant operators' top concerns about AIBar chart. Complexity: 46.1%; Cost: 43.5%; Customer acceptance: 41.9%.ComplexityComplexity: 46.1%46.1%CostCost: 43.5%43.5%Customer acceptanceCustomer acceptance: 41.9%41.9%Restaurant operators' top concerns about AIBar chart. Complexity: 46.1%; Cost: 43.5%; Customer acceptance: 41.9%.ComplexityComplexity: 46.1%46.1%CostCost: 43.5%43.5%Customer acceptanceCustomer acceptance: 41.9%41.9%

Source: National Restaurant Association, 2026[1]

Show the data
ConcernOperators naming it
Complexity46.1%
Cost43.5%
Customer acceptance41.9%

Where homemade agents break on restaurant calls

Most failures happen in the ear, not the brain. Speech recognition is not equally accurate for everyone: a 2020 study in PNAS tested five commercial speech recognition systems and found an average word error rate of 0.35 for Black speakers against 0.19 for white speakers[2]. Phone audio, kitchen clatter and cars make every system worse. A build that sounds perfect in a quiet office has to be tested against the guests who actually call you.

  • Callback numbers. One misheard digit makes the whole request useless. Read every number back, and test it with callers who speak quickly.
  • Dates. “Next Friday” said on a Thursday, “the 14th” without a month, “tomorrow” after midnight. Make the agent repeat the full date.
  • Interruptions. Guests talk over greetings and change their minds mid-sentence. The agent has to stop talking and listen.
  • Allergies. US law names nine major food allergens[3], and a guess about any of them is a liability. The rule is a handoff to a person, every time.
  • Gaps in the instructions. Asked something you never covered, a model will produce a plausible answer unless it is told to say it doesn't know and take a message.
  • Silence. When one provider in the chain slows down, the caller hears dead air and hangs up. Somebody has to notice.

Example test call for a homemade agent: from a mobile in a noisy room, say “Hi, yeah, can I get a table Friday, um, actually Saturday, for nine, maybe ten, around seven-thirty? One of us has a tree nut allergy.” A pass is a read-back of Saturday, the full date, nine or ten guests, 7:30, a name and a number, plus a handoff for the allergy. Anything less is a request your host can't act on.

Two existing guides do most of the groundwork for either path: preparing restaurant information for AI tools for the source material, and how to test an AI phone agent before going live for the test matrix. The handoff rules in when an AI phone agent should hand off to staff apply whoever builds it.

Building your own means writing your own greeting and owning the law behind it. Recording first: federal wiretap law lets a party to a call record it, or someone with one party's prior consent[4], but a number of states require every party's consent, including California, Florida, Illinois and Pennsylvania[5]. A recording notice at the start of the greeting is the simple way to cover callers wherever they are.

Outbound calls are stricter. On February 8, 2024 the FCC ruled that calls made with AI-generated voices are “artificial” under the Telephone Consumer Protection Act, so they face the same consent rules as other artificial or prerecorded voice calls[6]. FCC rules also require an artificial or prerecorded voice message to state clearly at the beginning who is responsible for the call, and to give a phone number for that business[7]. A homemade agent that rings guests back to confirm bookings needs all of that designed in; the FCC ruling on AI voices covers what it means for restaurants, and state AI disclosure laws covers the inbound side.

Card numbers are the third trap. PCI guidance says card security codes may not be stored after authorization, even encrypted, and a call recording that captures one must be securely deleted or made unrecoverable[8]. The cleanest design is not to take card numbers by voice at all: text the guest your ordering link and let your payment page do its job.

The monthly cost of running it yourself

Build estimates usually stop at launch. The recurring cost is the hours after it: reading transcripts, correcting answers, updating hours, retesting after a provider changes something, and being the person who gets the message when it breaks. Value that time at what the person doing it earns. The national median wage for food service managers was $33.36 an hour in May 2025[9].

ExampleManager time spent reviewing a homemade agent
Example: worked figures
InputExample
Calls the agent answers per day50
Minutes to review each checked call2
Share of calls you review (%)30%
Reviewer's hourly pay$33.36
Calls a month1,085
Staff hours on these calls36
Hours handed off11
Monthly value of that staff time$362

How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.

Assumptions

  • Hourly pay is the May 2025 national median wage for food service managers, before benefits.[9]
  • Example: 50 calls a day, with 30% of transcripts read in the first months and two minutes to read each one and note a fix.
  • Fixing prompts, retesting and handling outages come on top and are not counted here.

Example inputs. Use your own call volume and the pay of whoever will own the agent.

Example: on these inputs, review alone takes about 11 manager hours a month, roughly $360 at the median wage, before a single prompt is rewritten. A managed service does not make review go away; you should still read summaries every week. What it removes is the maintenance underneath: provider changes, outages, transfer logic and recording storage.

Then there is the on-call duty. Each provider in a homemade chain updates its service on its own schedule, and a change to the speech or voice layer can alter how the agent behaves on a Saturday you didn't plan to spend at a laptop. Somebody has to get the alert, know which part failed and switch the line back to the host stand while it is fixed. With a managed service, that person still exists on your side, but their job is to send a message, not to debug the stack.

Side by side

Building your own agent or using a managed service
Build it yourselfManaged service
Time to the first real callBuilding, then weeks of testingApprove the answers, test calls, then forward
Who fixes it on a Friday nightYouThe service's support
Control over wordingEvery word, and every mistakeYou approve the greeting and the answers
Handoffs and backupsBuilt and tested by youSet from the manager path you choose
Recording notice and disclosureYour legal homeworkBuilt into a greeting you sign off
Call recordsWherever you store themSummary by email, recording and transcript kept
Your own systemsAnything you can codeSigned webhooks to the systems you run

For most single restaurants the right-hand column is the better fit. A group with developers on staff may weigh it differently.

ExampleFriday dinner service with Ava (Example)
  1. Answered2 events
  2. Request captured3 events
  3. Passed to staff2 events
  4. Confirmed by staff2 events

Activity

  1. Call

    Kitchen hours

    Caller asked when the kitchen closes tonight. Ava gave the approved time: 10 pm.

  2. Call

    Table request · party of 8

    Saturday, 7:30 pm, birthday. Saved as a request for the host to confirm; no table promised.

  3. Text

    Ordering link sent

    Caller wanted pickup and agreed to a text. Ava sent the restaurant’s official ordering link.

  4. Call

    Allergy question → manager

    Guest asked about a tree-nut allergy. Ava did not answer it and took a callback for the manager on duty.

  5. Web form

    Catering inquiry · 40 guests

    Office lunch next Thursday, drop-off, vegetarian options wanted. Sent to the catering manager.

  6. Call

    Missing item on a delivery

    Guest said a side was missing. Ava logged the order name and passed it to the manager with a summary.

  7. Call

    Host confirmed party of 8

    Host called the guest back and confirmed Saturday at 7:30 pm. Status updated in the inbox.

  8. Chat

    Private room question

    Website chat: rehearsal dinner for 22 in March. Event request created for the events lead.

  9. Call

    Catering manager followed up

    Catering manager called back, confirmed the date and sent menu options. Marked as quoted.

  • 46Calls answeredExample
  • 12Requests sent to staffExample
  • 3Catering and event leadsExample
  • 5Handed to a managerExample

Example only. Fictional business, people and numbers; not a recording or a live account.

ExampleExample dashboard: a call arrives, a summary is written and the request is logged for staff. A homemade agent has to recreate this view from scratch.

When building it yourself makes sense

Some operators should build. A group with a developer on staff, its own ordering or booking system with an API, and an unusual workflow no service supports may get exactly what it wants from a build, provided someone owns it on call. That describes few restaurants. AI use rises with company size: 30% of US firms with at least 250 employees used AI in April 2026, against 17% of firms with fewer than 20[10], and 9 in 10 restaurants have fewer than 50 employees[11]. Most kitchens do not have a spare engineer.

A managed SI Employee covers the same ground without the build. You approve the house information and the manager path; it answers forwarded calls, takes reservation requests for your host to confirm, sends catering details to your catering manager, texts the ordering link when the caller agrees and hands complaints and allergy questions to a person. Groups that want call data in their own systems can receive each call by signed webhook (integrations). The three-restaurant group example shows how one manager path can serve three numbers.

If the attraction of building is mostly the price, read the limits of free AI receptionist tools first. Free credits and a weekend of building can look like the same thing as a working phone line until the first busy Friday.

Five questions before you start building

  1. Who answers for it at 9 pm on a Saturday?

    Name the person, and their backup. If the answer is “whoever notices”, nobody does.

  2. Who reads the transcripts every week?

    Someone who knows the menu and the policies, with time blocked in the schedule, not squeezed in after close.

  3. Can you keep the greeting compliant?

    Recording notice, automated-assistant disclosure and any outbound-call consent, for every state your guests call from.

  4. Is there anything to connect to?

    If your reservation or ordering system has no API, the agent can only take requests, which is what a managed service already does.

  5. What does a bad week cost?

    Price a weekend of missed bookings and wrong answers. If that number is larger than a year of a service, the build is not saving money.

Frequently asked questions

How long does it take to build an AI receptionist for a restaurant?

A first version that answers calls can take an afternoon. Testing it against real restaurant calls (noise, accents, interruptions, allergy questions, party bookings) and fixing what fails is what takes weeks, and monitoring never stops.

Can a no-code voice agent take restaurant reservations?

It can collect party size, date, time, name and number. Confirming a table needs a working connection to your reservation system and someone who owns it when it fails; without one, it is taking requests for your host to confirm.

Is it legal to put a homemade AI agent on our phone line?

Answering inbound calls is generally fine with a clear greeting and a recording notice where state law requires consent[5]. Calling guests back with an AI voice is treated as an artificial-voice call under the TCPA and needs consent[6].

What does a managed service still need from us?

Approved house information, the questions to ask for reservations and catering, a manager path with a backup, a round of test calls before forwarding, and someone who reads the call summaries each week.

Can we start with a managed service and build later?

Yes. Forwarding is a setting you can change, and the house information document you write is yours either way. Running a service first also shows you which calls a build would really need to handle.

References

  1. National Restaurant Association (2026). Research Insight: The Future of Restaurant Technology (press release, November 5, 2026) (opens in a new tab) ↑

  2. Proceedings of the National Academy of Sciences (via PubMed Central) (2020). Racial disparities in automated speech recognition (Koenecke et al.) (opens in a new tab) ↑

  3. US Food and Drug Administration (2026). Food Allergies (opens in a new tab) ↑

  4. Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code § 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑

  5. Digital Media Law Project, Berkman Klein Center (2026). Recording Phone Calls and Conversations (legal guide, no longer updated) (opens in a new tab) ↑

  6. Federal Communications Commission (2024). FCC Makes AI-Generated Voices in Robocalls Illegal (news release) (opens in a new tab) ↑

  7. Legal Information Institute (Cornell Law School), eCFR text of FCC rule (2026). 47 CFR 64.1200 - Delivery restrictions (opens in a new tab) ↑

  8. PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑

  9. US Bureau of Labor Statistics (2025). Table 1. National employment and wage data from the Occupational Employment and Wage Statistics survey by occupation, May 2025 (opens in a new tab) ↑

  10. Federal Reserve Bank of Minneapolis (analysis of Census Bureau BTOS) (2026). AI adoption in business grows steadily but unevenly (opens in a new tab) ↑

  11. National Restaurant Association (2025). National Statistics: Restaurant Industry Facts at a Glance (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