TLDR: Otto is used by pizza shops including Angry Napoli Pizza, Pizza Doh, Pizza by the Bay, The Pizza Lounge, and Alessio's Pizza. It handles the full complexity of pizza phone orders including half-and-half toppings, size combinations, meal deals, and modifier stacking, and sends every order directly to the kitchen without staff involvement. It answers within two rings, 24/7.
For a pizza shop, the phone is not a supplementary channel. It is the business. Most pizza revenue arrives through the phone, particularly on Friday and Saturday nights when every missed call is a direct hit to the night's takings. There is no padding elsewhere in the week to absorb those losses.
This is exactly the context Otto was built for. This article covers how it handles the specific complexity of pizza orders, which pizza shops are using it, and what the financial case looks like.
Pizza orders are modifier-heavy in a way that most other cuisine types are not. A customer ordering a burger makes a handful of choices. A customer ordering pizza for a group of four on a Friday night might be placing eight separate items, each with independent customisation requests, across two or three different sizes, with a meal deal applied to part of the order.
The complexity that matters most: half-and-half toppings where different sides of the pizza have different ingredients, extra or reduced quantities of specific toppings, special instructions about sauce amounts or cheese distribution, size combinations within the same order, and meal deal pricing that depends on which items are combined.
For a human phone operator mid-service, managing this complexity accurately across back-to-back calls is demanding. Errors happen. Remakes happen. During a Friday night peak when the phone is ringing constantly and the oven is full, accuracy drops.
Otto is configured around your specific menu during onboarding, including every topping combination, every size option, every meal deal structure, and every modifier rule your kitchen needs to produce the order correctly. It captures the full complexity in natural conversation and confirms it back to the caller before the order is sent to the kitchen.
Otto is currently used by several Australian pizza venues including Angry Napoli Pizza on Queensland's Sunshine Coast, Pizza Doh, Pizza by the Bay, The Pizza Lounge, and Alessio's Pizza.
Giuseppe at Angry Napoli Pizza handles his shop largely alone. Between December 2025 and March 2026, Otto managed 475 conversations for his venue including 119 calls in a single peak hour. The orders went directly to the kitchen without Giuseppe touching the phone during service.
"It's impressive the way it works -- different languages, all the requests, all the issues handled. Beautiful, amazing." - Giuseppe, Owner, Angry Napoli Pizza
Read the full case study at callotto.ai/case-study/angry-pizza.
The Otto Restaurant Phone Report 2026, which analysed 1,067 Australian restaurants and cafes, found that restaurants miss around 1 in 3 calls on average, with over 70% of those being revenue-related. For a pizza shop where the phone is the primary channel, missing 1 in 3 calls during Friday and Saturday service is a significant revenue event.
At the average high-volume phone order value of $61 AUD, a pizza shop missing 20 calls across a Friday and Saturday service is losing $1,220 per weekend. Over 50 weekends that is $61,000 annually.
Otto's Growth plan is $299 AUD per month with no lock-in. For any pizza shop missing more than five phone orders per month that Otto would have captured, the plan pays for itself. The missed calls calculator at callotto.ai lets you calculate your specific figure.
The modifier handling is configured during onboarding based on your specific menu. You explain how half-and-half works at your shop, what topping options exist, how meal deals are structured, and what the modifier rules are. The Otto team builds this into the agent.
During a call, Otto takes the order in natural conversation. A caller who says "I want a large half pepperoni half margherita with extra cheese on the whole thing" receives a response that confirms each element and asks any necessary follow-up questions before the order is finalised. The confirmed order goes to the kitchen exactly as specified.
For full detail on how phone ordering works see callotto.ai/solutions/restaurant-phone-orders.
Otto is used by multiple Australian pizza shops including Angry Napoli Pizza, Pizza Doh, Pizza by the Bay, The Pizza Lounge, and Alessio's Pizza. It is configured around each venue's specific menu including half-and-half toppings, size combinations, meal deals, and modifier rules. It handles the full complexity of pizza phone orders and sends them to the kitchen without staff involvement.
Yes, when configured correctly during onboarding. The Otto team builds your specific modifier rules into the agent including half-and-half combinations, topping variations, sauce quantities, and meal deal structures. Otto confirms the full order back to the caller before sending it to the kitchen.
Restaurants miss around 1 in 3 calls on average, with over 70% being revenue-related (Otto Restaurant Phone Report 2026). For a pizza shop missing 20 calls across Friday and Saturday at $61 average order value, that is $1,220 per weekend or roughly $61,000 annually. Otto's Growth plan at $299 AUD per month pays for itself if it captures more than five orders per month that would otherwise have been missed.
Yes. Once an order is confirmed with the caller, Otto sends it directly to the kitchen via KDS or printer without any staff member needing to re-enter it. The order appears in the kitchen exactly as if a staff member had taken it at the counter.
Most venues are live within one business day of completing onboarding. You provide your menu including toppings, sizes, meal deals, and modifier rules. The Otto team handles the configuration. You test the agent by calling it before it goes live on your real number.
For a pizza shop where the phone is the primary revenue channel, missing calls is not a minor operational issue. It is a direct revenue loss that compounds across every service.