AI Phone Agent for Pizzerias
Pizza calls are the hardest orders a phone line takes: half-and-half pies, extra crispy, a side of ranch. Here is what a pizza phone agent has to get right.
On this page
A pizzeria phone call is not a normal order. It is a large half-mushroom half-pepperoni, extra crispy, cut in squares, a side of ranch, and a question about whether the gluten-free crust is made in the same oven. It arrives while the counter is four deep and the oven door is open.
That is the call a phone agent has to survive. Not a demo script with one item.
TL;DR
- Pizza is the highest-modifier order in a restaurant, and a phone agent that flattens "half mushroom, half pepperoni, extra crispy" into a note creates kitchen mistakes.
- Industry estimates put the average phone ticket between $32 and $48, different from an online ticket, and a phone order carries no marketplace commission.
- A missed call is estimated to cost $35 to $85, and roughly 85% of callers do not call back after one goes unanswered.
- Kovo handles nested modifier groups, half-and-half pies, and a read-back before the order is placed, from $99 a month.
- Orders above 10 items in total or more than 8 of one item are not sent to the kitchen. Party orders still need a person.
Why pizza is the hardest order to take by phone
Most restaurant orders are a list. A pizza order is a tree.
A large pie has a crust, a sauce, a cheese, a cut, a doneness, and then two independent sets of toppings, one per half. A calzone has a filling and a side of sauce. A wings order has a count, a sauce, and a dip. A salad has dressing on the side or not, which changes what the kitchen does.
On paper that is a menu. On a phone line it is a sequence of corrections: "no, the left half", "extra crispy means well done", "ranch, not blue cheese", "is the garlic knot order six or twelve".
The failure mode is not that the agent mishears. It is that the ticket loses the structure. A kitchen can execute "half mushroom, half pepperoni" if it arrives as two modifier paths. It cannot execute a paragraph in the special-instructions field at 8:15 on a Friday.
What the agent has to hear
Four things, in this order:
- The item and the size. Large, 16-inch, or the shop's own name for it. The menu model has to accept all three.
- The structure. Which half gets what, which items are separate, which are a combo.
- The kitchen instruction. Extra crispy, light sauce, no garlic, cut in squares. This is not a topping and should not be priced like one.
- The rest of the order. Drinks, sides, dips, and the second pie that someone shouts from the next room.
Then it reads the whole thing back. Not a summary. The actual ticket, in the order the kitchen will read it.
Kovo's menu model comes from the shop's own POS catalog or menu page and keeps nested choice groups, so a half-and-half pie opens its own groups on each half instead of collapsing into free text. The read-back is the second check: a caller who hears the wrong half can fix it before anything prints.
The pickup problem, and the quote you should not guess
Pizza callers ask two questions before they order: how long, and how much.
A phone agent should not invent a wait time. If the shop has not given it a rule, the honest answer is "the kitchen will text you when it's ready" or a range the owner set, not "twenty minutes" because twenty sounds good. Kovo quotes only the wait the owner set, and says nothing when none is set, so a shop that gets this question constantly should put a baseline in the desk.
Price is the easier half. The agent quotes from the live menu, including modifiers. If a marketplace menu is marked up, the Kovo menu markup percent keeps the phone from quoting the in-store price on a delivery order.
The Friday 6 p.m. wall
Pizza phone volume is not spread evenly. It spikes hard, and it spikes when the oven is full.
At 6:40 on a Friday, a shop with two phone lines and one cashier is not answering the third call. Industry estimates put roughly 30% of calls unanswered during the 5 to 8 p.m. peak, and a missed pizza call is not a lost lead. It is a family ordering from the place two blocks over, and they will like it there.
The arithmetic is worth doing with your own numbers. Take your average phone ticket, multiply by the calls you know you miss on a Friday, and multiply by four Fridays:
- 12 missed calls a night × $38 = $456 a week.
- $456 × 4 = $1,824 a month.
Kovo Starter is $99. Unlimited is $299. The missed-call math goes through the same calculation with the published ranges, and the phone vs online ticket comparison explains why a phone ticket is not automatically the bigger one.
What the ticket should look like
Here is the test to run on any vendor, including Kovo. Call in this order:
"Large, half mushroom, half pepperoni, extra crispy, cut in squares, and a dozen garlic knots with ranch."
Then ask for the kitchen ticket. It should show:
- one large pie,
- mushroom on one half,
- pepperoni on the other,
- a doneness modifier,
- a cut modifier,
- a separate line for the knots,
- a dip,
- and a total that matches the menu.
If the screen shows a paragraph instead, the agent is transcribing, not ordering. The Toast integration page shows how the ticket reaches the KDS on one of the four POS systems Kovo prints to.
Payment, honestly
Two paths, and pizza shops use both.
If cards are off, the order is confirmed on the call and the caller pays when they collect. That is the simplest setup and it is what most shops start with.
If cards are on, Kovo texts a Stripe Checkout link to the caller's number and holds the ticket until payment clears. The card is typed on Stripe's page, so no card number is spoken, recorded, or stored by Kovo. The tradeoff is real: the caller has to tap a link, and the ticket does not print until they do. It is not a card taken on the call, and a shop that needs the transaction finished before the caller hangs up should know that before signing.
Where a pizza phone agent is the wrong buy
If your calls are mostly "do you deliver to 112th" and "are you open on Thanksgiving", you do not need an agent. You need a better website and a recorded message.
If your average ticket is a single slice and a soda, the math does not work at any price above free. If your shop is a destination where the phone is a reservation line for a dining room, an order-taking agent solves a problem you do not have.
And if the calls you lose are party orders and catering, no current phone agent fixes that. Kovo will not send an order above 10 items in total or more than 8 of one item. It declines to ticket what the kitchen cannot build in one pass. That is a handoff problem, and it needs a human.
FAQ
Can an AI phone agent take a half-and-half pizza order?
It can, if the menu model supports it. Kovo handles nested choice groups, and a half-and-half pie opens a separate set of toppings on each half, so a caller saying 'half mushroom, half pepperoni, extra crispy' produces one ticket with two modifier paths rather than a note the kitchen has to interpret. Ask any vendor to take that exact order on a demo call, then look at the ticket.
How does the agent know a topping is sold out?
Kovo reads the shop's menu source once a day and the call path pulls when the menu is two days old, so an item marked unavailable stops being offered on the next answered call. An owner 86 in the menu board outranks the source, and a Square or Clover item marked sold out stays sold out after the pull. If the kitchen 86s the sausage at 7 p.m., mark it unavailable in the Kovo menu as well, the same way you would update a menu board.
What happens to a very large pizza order?
Kovo will not send it. The defaults are 10 items in total and 8 of one item, and above that the agent says the order is too large to send through and keeps taking what fits. The owner can raise either limit, or turn on large-party routing so a party call rings the handset instead. The phone never silently drops it.
Will it read back a pizza order correctly with a noisy kitchen behind the caller?
Speech recognition handles a busy room better than a headset-wearing cashier does, because it is not also running a register. The order is read back before it is placed, which is the actual safeguard: a caller who hears 'half mushroom, half pepperoni, extra crispy, large' can correct it before a ticket prints.
How much does a pizza phone agent cost?
Kovo Starter is $99 a month for 750 connected minutes, roughly 300 calls, and Unlimited is $299 for 5,000 minutes. There are no per-minute fees and no overage: at the cap, calls forward to the shop's own phone. One recovered $33 phone ticket a month covers a meaningful share of the Starter plan.
Final Thoughts
Pizza is not a generic restaurant vertical with a different word on the box. It is a modifier problem, a 6:40 p.m. problem, and a ticket-structure problem. A phone agent that gets those three right earns its $99. One that produces a paragraph in the notes field costs more than it saves.
Kovo takes the half-and-half, reads it back, and prints it to Toast, Square, Clover, Olo, or a printer. Try it with your own menu for 14 days, no card, and call in the order you know your kitchen gets wrong. Take a test call.