AI Phone Agent for Sushi Restaurants
Sushi phone traffic splits in two: omakase seats and pickup rolls. Here is what an agent has to get right about party size, rice, raw fish, and pickup timing.
On this page
A sushi shop's phone rings for two businesses at once. One caller wants four seats at the counter at 7:30, and wants to know whether omakase is chef's choice or a set. The other wants three rolls, a miso, and a pickup on the way home, and wants to know when.
An agent that treats both calls as orders fails the first one. An agent that treats both as reservations fails the second. That split, not the cuisine, is what a sushi phone line has to be built around.
TL;DR
- Sushi phone traffic is two products: seats (omakase, party size, a time) and pickup (rolls, nigiri, a time), and they need different answers.
- Rice, not fish, sets the late-night limit: batches are cooked, held, and gone, and a ticket has to reach the counter while there is rice under it.
- Raw fish is sliced to order, so the pickup time is a kitchen instruction rather than a customer preference, and an early ticket is a plate that sits.
- Kovo books its own tables but writes into no platform book, and it quotes only the wait the owner set, so party size and timing need a written policy plus a handset number.
- Orders above 10 items in total or more than 8 of one item are declined, and in sushi those caps arrive at the second seat and the family order.
Why the sushi phone is two businesses
Most verticals take a single kind of call with variations. Pizza is an order with a question about the oven attached. Sushi splits at the root: the shop rents a seat with a chef in front of it, and it sells a bag of food.
The seat conversation is about the room. Party size, counter or table, how long the omakase runs, whether a six-top can be split, whether the eight-o'clock setting is a single seating. None of that is an order, and a voice agent that starts collecting items when a caller says "omakase for four" has already lost the thread.
The pickup conversation is the opposite. It is items, quantities, a pickup time, and rice. A caller who has ordered the same two rolls every Thursday does not want to be asked about the room.
An operator should decide which of the two the agent owns before choosing a vendor. If the phone is mostly seats, the product you need is a reservation platform with a voice partner, and OpenTable keeps a list of voice AI partners for its reservation products. If it is mostly pickup, keep reading.
What the vocabulary actually asks for
Sushi callers use words that carry a whole transaction inside them, and an agent that misreads one loses the order.
- Omakase. Chef's choice, per person, priced by the seat. If it is on the menu, the agent can describe what it includes and quote the number. What it cannot do is hold the seat.
- Party size. "Four, but one is a child." That is a room constraint, not a quantity, and it belongs to the host.
- Nigiri, maki, sashimi. Three different plates. "Twelve pieces" is six of one and six of another on one order and a different kitchen ticket on the next.
- Counter or table. Changes how omakase is served, and changes whether a walk-in fits.
- What is in the case. The fish list is the menu's live edge, and it is the question most likely to get a confident wrong answer.
The failure mode is specific to the cuisine: a caller says "omakase for two at 7:30" and a generic agent confirms a two-person order for 7:30, which satisfies neither the room nor the kitchen. The caller believes they have a seat. They do not.
The pickup time is a kitchen instruction
At a pizzeria, a pickup time is about the oven queue. At a sushi counter it is about slicing.
Raw fish is portioned to order. A plate of nigiri is not held under a lamp, so the ticket's timing decides whether the counter starts slicing when the caller is five minutes out or twenty. A ticket that prints too early is fish sweating on rice. A ticket that prints too late is a caller standing at the front with a bag coming.
That makes two things matter more than the voice. First, the pickup time the agent quotes has to be the shop's own policy rather than an invention, because a confident "twenty minutes" is a promise the counter never agreed to. Kovo does not read a live wait from the kitchen, so the number has to come from the owner, written into the knowledge the agent answers from.
Second, the order has to be timestamped in a way the counter can act on. The implementation guide for menu sync covers the data side; the operational side is deciding whether the pass reads the ticket time as "start now" or "start in fifteen".
Rice is the batch that ends the night
Every vertical has a resource that runs out before the menu does. For a sushi counter it is usually rice.
Rice is cooked in batches, seasoned, and held at body temperature, and a batch has a working life measured in hours rather than a whole service. The number of batches a shop plans for the evening is a real ceiling on how many covers and how many pickups it can serve, and it is invisible in every menu the software reads.
Two consequences follow. A late call is not a menu question, it is a batch question, and the answer changes at 9:40 in a way no catalog can express. And the agent can only know a batch is gone if someone tells it: Kovo reads the menu again on the next refresh, so a fish that sold out at 7 p.m. keeps being offered until somebody marks it unavailable in the panel as well as at the pass.
That is a manual step, and it should be written on the closing checklist next to the rice count, not discovered on a call. The case works the same way: the freshest items disappear first, and a caller who hears an offer and then a refusal at the counter does not come back.
Where the caps hit sushi first
Every product has limits, and the honest test is where they fall in your format. Kovo will not send an order above 10 items in total or more than 8 of one item.
Run your own prices through that. At $55 a seat, omakase for two is $110, so the dollar cap arrives at the second person rather than the tenth. A family order of 12 rolls is 12 entrees. A table asking for ten pieces of one nigiri is past the per-item limit before it becomes a plate.
In a pizzeria those caps catch the party order. In a sushi shop they catch ordinary Friday business, which means the phone needs a path for the calls the agent refuses. Set the handset number so a caller who asks for a person transfers, and staff the line during the two hours when seats and pickup both peak.
The rest of the missed-call arithmetic is the same as any format. Industry estimates put a missed restaurant call at $35 to $85 and roughly 30% of calls unanswered during the 5 to 8 p.m. peak, which you can work through with your own ticket in what missed calls cost a restaurant.
What Kovo does on a sushi line
Kovo answers, builds the order as the caller speaks, reads it back, and posts the finished ticket to Toast, Square, Clover, Olo, or an Epson or Star printer. It keeps nested choice groups, so a combo, a set, and a roll with two changes stay structured instead of collapsing into a note. Menu questions, hours, and recommendations stay on the call, and the order is read back before it is placed.
It books its own tables but writes into no platform book, quotes only the wait the owner set, and carries no ingredient database. With cards on, it texts a Stripe Checkout link and releases the ticket only when payment clears, which means no card number is spoken into a line that is being recorded. A plan runs $99 for 750 connected minutes or $299 for 5,000, and one subscription covers one store.
The sushi-specific setting is the handset number: without it, a caller asking about a seat has nobody to ask for.
Who this is wrong for
If your revenue is the counter and your calls are seat requests, an order-taking agent is the wrong purchase. The room is the product, the book is the system of record, and a phone agent that cannot touch the book will frustrate a caller who wanted a chair.
It is also the wrong purchase if your omakase is one nightly seating that sells out on a fixed day, or if the only calls you miss are vendors. The pizzeria version of this guide is a better fit for a shop built on delivery and carryout, and the blog index has the rest of the verticals.
FAQ
Can an AI phone agent book an omakase seat?
Not Kovo. It answers the phone, handles menu and hours questions, and takes orders from $99 a month, and it books omakase seats in its own book (not OpenTable or Resy), so a seat taken on the phone lives in Kovo's desk. Set the handset number in the desk so a caller who asks for a person transfers, and keep the seat itself in whatever system already runs your book.
What happens to a sushi order past the 10-item total?
It is not sent to the kitchen. A family order of 12 rolls is past the 10-item total, and nine of one roll is past the 8-per-item limit. Plan a manual path for those calls, because Kovo will not send the order and does not route the caller to a manager.
Can the agent quote a pickup time?
Not from the kitchen's live board, and it should not invent one. Kovo answers from the shop's own site, menu, FAQs, and hours, so the pickup window a caller hears is the policy the owner wrote down. A shop that wants '20 to 25 minutes' on a Friday puts that sentence in the knowledge it gives the agent.
Does the agent know which fish has sold out?
It knows what the menu says after the last refresh. Kovo pulls once a day and reads a menu at most two days old, so a fish marked unavailable in the panel stops being offered on the next call, but an 86 at 7 p.m. does not write back into the POS. Mark it in both places at the pass.
How much does a sushi phone agent cost?
Kovo Starter is $99 a month for 750 connected minutes, roughly 300 calls at a two-and-a-half-minute average, and Unlimited is $299 for 5,000. There is no per-minute fee and no overage: at the cap, calls forward to your own line. One pickup order of 4 rolls and a miso covers a real share of Starter.
Final Thoughts
The sushi phone is two conversations wearing one area code. Decide which one the agent owns, write the pickup policy down, and give the seat calls a person to reach. Then the arithmetic is ordinary: a bag of rolls taken at 6:40 instead of an unanswered ring.
Kovo takes the pickup order, reads it back, and prints it to the POS you already run, from $99 a month with 14 days free and no card. Call in your own hardest ticket, two rolls with changes and a set, and look at what the counter receives. Take a test call.