AI Phone Agent for Chinese Restaurants
Chinese takeout phone orders arrive as combo numbers, half at lunch prices, and a delivery question the phone answers straight. What it has to get right.
On this page
The caller does not name a dish. They say "number forty-two" and expect the whole ticket to follow: chicken with broccoli, pork fried rice instead of white, hot and sour soup instead of the egg roll, and the whole thing to arrive in thirty minutes.
That single word carries three choices, and the person at the counter has taken it a thousand times. A phone agent has to expand it the same way, then read it back in a form the kitchen can cook from.
The reason it matters is volume. A Chinese takeout line at 6:30 on a Friday is not a reservation desk; it is a queue. Industry estimates put roughly 30% of restaurant calls unanswered during the 5 to 8 p.m. peak, and each of those is a ticket in the estimated $32 to $48 range, not a message.
TL;DR
- A combo number hides 3 decisions (the entree, the rice, and the soup or roll), and the ticket has to expand them or the kitchen guesses.
- Callers order lunch specials from 11 until the board comes down, and a price that ends at 3 p.m. is a menu item, not a phone setting.
- Delivery runs on the shop's own drivers, so the radius question gets one written answer — a street edge or a list of zip codes — instead of a guess.
- Industry estimates put a missed restaurant call at $35 to $85, and around 85% of callers do not call back after one goes unanswered.
- Kovo reads the combo and its parts back, prints to Toast, Square, Clover, Olo, or a printer, and starts at $99 a month; orders past the shop's own limit are declined.
The combo number is the primary key
Most verticals take an order as a list of items. A Chinese takeout menu is a lookup table, and the caller has the key.
A number can be a lunch special, a combination built around one entree, or a family dinner that feeds three. Regulars know those numbers better than the staff do, and they use them because saying a number is faster than saying five things while a television plays in the background.
Two things break when a phone agent does not treat the number as a key.
The first is speed. A caller who says "forty-two, pork fried rice, hot and sour" and gets asked "and what comes with that?" has been made to feel like the agent does not know the menu. They will either repeat themselves in a flat voice or hang up and order online.
The second is structure. The number hides three decisions, and each one has its own price and its own kitchen consequence. Pork fried rice is a different station than white rice. Soup is a different container than an egg roll. If the ticket comes back as a line item called "42" with no parts, the expeditor has to open the menu to pack the bag.
Kovo keeps the combo as one item with nested choice groups, so the number and its three answers arrive on the ticket together, and the menu sync guide explains how a menu with that depth gets from the POS into the phone without being flattened.
The lunch special has an edge at 3 p.m.
Lunch is where Chinese takeout makes its margin, and it is also where phone orders go wrong most often, because the menu changes at a clock time rather than at an event.
At 2:55, a caller can order the lunch special: smaller portion, soup, rice, one price. At 3:05, the same words get a dinner price and a larger portion, and the counter says so out loud, every day, to someone who did not read the fine print.
A phone agent quotes the menu it was given. That means the shop has to decide which of two designs it wants:
- Lunch as its own item. Two items on the menu, lunch sesame chicken and dinner sesame chicken, each with a price and a portion. The agent quotes correctly all day, and the only cost is a longer menu.
- One item, one price. Simpler to maintain, and wrong for three hours a day, or three hours a night depending on which price you pick.
Neither is a product feature to shop for. It is a menu design decision, and the operator who makes it deliberately gets a phone line that quotes the right number at 2:55 and at 3:05.
The delivery question has one answer
Every Chinese takeout call includes a geography test. "Do you deliver to Elm and 9th?" arrives before the order does, and the answer decides whether the rest of the conversation happens at all.
Kovo's answer is the boundary the owner wrote down. Delivery runs on the shop's own drivers, the agent takes the address, and the radius is quoted only as far as the written policy goes. It does not dispatch to a marketplace, so an order that needs a DoorDash courier is not one the phone can fulfil.
That is not a limitation to paper over. A shop that runs its own drivers still takes delivery orders by phone — with a person, who knows the boundary, the minimum, and the driver on shift. A shop that sells through DoorDash, Uber Eats, or Grubhub keeps that channel in the app, where the address is checked against a real map.
What Kovo can do is answer the rest of the geography: where the shop is, when it is open, and whether the caller's order is ready for pickup. Write the parking and pickup instructions where the agent reads them, because that is the question a pick-up caller actually asks.
The arithmetic on a Tuesday
Take your own ticket and your own missed calls, because the published ranges are a check, not a forecast.
Say your average phone order is $38 and you miss 10 calls a week between lunch and close. That is $380 a week, or $1,520 a month, and roughly 85% of those callers do not call back. The QSR Magazine analysis puts the average restaurant at around 150 missed calls a month, which is the number to compare yours against, and the loss concentrates in two windows: 11:30 to 1, and 5:30 to 7:30.
Run it with your numbers in the missed-call math, then compare it to a plan. Starter is $99 a month for 750 connected minutes, which is about 300 calls at two and a half minutes each.
Where the caps land on a Chinese menu
Kovo's caps are the shop's, with a default of 10 items in total and 8 of one item, an optional order-value limit, and a zero that removes any of them. The point is not to ticket something the kitchen cannot build in one pass.
For Chinese takeout those caps arrive in a specific shape. A family dinner for six, two extra entrees, a quart of wonton soup, and two sides crosses 10 items before the table has finished ordering. A party order of 12 combination platters trips the 10-item total. A single-item order of 10 egg rolls trips the per-item limit, which surprises shops that sell egg rolls by the dozen.
That is the phone's job to say no to, and then the shop's job to catch. Above a limit the call rings the shop only if the owner turned on large-party routing and set a handset number; otherwise the agent says the order is too large to send through and keeps taking what fits. Put the party-order policy on the counter card next to the register.
What Kovo does on a Chinese line
Kovo answers, takes the order the way the caller says it, keeps the combo structure, and reads the whole ticket back before it is placed. Menu questions, hours, recommendations, and order-status questions stay on the call. Handoff happens when the caller presses 0 or asks for a person, and only if the shop set a handset number. A website chat runs on the same engine, so the customer who types at 6:30 gets the same combo expansion.
The ticket goes to Toast, Square, Clover, Olo, or an Epson or Star printer. Payment has 3 paths. With cards off, the order confirms on the call and the caller pays when they collect. With cards on and a card the shop already holds for that number, it is charged off-session while the caller is still on the line, so the kitchen ticket reaches the wok during the call.
A first-time caller gets a Stripe Checkout link by text with the line held open, and paying it vaults the card for the next order. No card number is spoken, recorded, transcribed, or sent to a model. The Toast routing page shows the printed result on one of the four systems.
Who this is wrong for
If your calls are mostly "are you open" and "do you have a table for six", you are running a dining room, and an order-taking agent is aimed at the wrong half of your business. Kovo books its own tables but writes into no platform book.
If your menu is a hundred and forty items and changes weekly, the one-day refresh will lag, and callers will hear about dishes you dropped. Fix the catalog before the phone.
And if your delivery is a marketplace's problem, with a courier network setting the radius, the phone can repeat the policy but not the dispatch. Kovo does not send orders to DoorDash, Uber Eats, or Grubhub, and the Indian restaurant guide covers the same limits in a menu built on per-dish heat.
FAQ
Can an AI phone agent take an order by combo number?
It can when each combo is a real menu item with its own choice groups, which is how Kovo models a combination platter: the entree, the rice, and the soup or egg roll are separate choices inside one number. The read-back then says the number and its parts, so the caller hears 'number 42 with pork fried rice and hot and sour soup' before the ticket prints.
What about the lunch special price after 3 p.m.?
The agent quotes the price on the menu it was given, and the menu refreshes once a day, so a lunch price that quietly ends at 3 is a setting no phone system can enforce. Model lunch as its own item with its own name and price, or accept that a 3:10 caller hears the lunch number and the counter corrects it.
Can the agent tell a caller whether they are inside the delivery radius?
Yes, if the shop runs its own cars. The agent takes the delivery order and the address, and the radius is whatever boundary the owner wrote into the knowledge it answers from: a street edge or a list of zip codes. It does not dispatch to DoorDash, Uber Eats, or Grubhub, so an order for a marketplace courier belongs in that app.
What happens to a big family dinner order?
The defaults are 10 items in total and 8 of one item, both editable, and an owner can add an order-value limit or set either to zero. A family dinner for four with two extra entrees and a quart of soup crosses 10 items more easily than the entree count suggests, so count your own top sellers against the cap before you sign, and turn on large-party routing with a handset number if you would rather those calls rang the shop.
How much does a Chinese restaurant phone agent cost?
Kovo Starter is $99 a month for 750 connected minutes, about 300 calls, and Unlimited is $299 for 5,000 minutes, with no per-minute charges and no overage. At an estimated $38 phone ticket, three recovered dinner orders a month cover Starter, and the rest of the month is margin.
Final Thoughts
The decision is not whether a phone agent can hear "forty-two". It is whether the product expands the number into three decisions, quotes the right price at 3:05, and states the shop's own delivery boundary instead of guessing at a radius. Get those three right and the phone becomes the fastest order channel you own; miss the combo structure and it becomes a slow transcription service with a phone bill.
Kovo takes the number and its parts, reads them back, and prints to the POS you already run, from $99 a month, and the plan carries 750 connected minutes. The restaurant phone AI guides cover the other formats. Call in number 42 with two substitutions and look at the ticket the kitchen receives. Take a test call with your own menu.