AI Phone Agent for Indian Restaurants
Indian phone orders carry a heat level per dish, a thali that is six decisions, and a vegetarian split. Here is what a phone agent has to get right.
On this page
A Thursday dinner order at an Indian restaurant can reach the kitchen at four different heats. Chicken tikka for the table, dal mild for the eight-year-old, lamb rogan josh hot, and one paneer dish ordered "medium, but not too medium" by a caller who then adds garlic naan and a mango lassi.
Nothing in that order is difficult. All of it is relational, and an agent that hears "medium" once and applies it to the whole ticket has just sent a child a vindaloo.
That is the first thing to test on any phone agent, ours included, because the ticket is where the mistake becomes visible. At a $62 family order and four missed calls on a Friday, the arithmetic is $248 a week that walked to the place two doors down, and it walked because the phone was a person with one hand on the till.
TL;DR
- An Indian dinner order can carry 4 different heat levels, and an agent that stores one "medium" for the ticket sends the wrong dish to the wrong person.
- A thali is 6 to 8 compartments inside one menu item, so the ticket has to keep the structure instead of flattening it into a note.
- Vegetarian and vegan orders come off the same menu, and a family order of twelve dishes passes the 10-item cap, so the phone needs a path for the calls it will not send.
- 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.
- Kovo reads the order back, keeps nested choice groups, and prints to Toast, Square, Clover, Olo, or a printer from $99 a month, and it will not send an order above 10 items in total or more than 8 of one item.
Why one order arrives at four heat levels
Most cuisines put the kitchen instruction on the order. Indian cooking puts it on the dish.
"Medium" is not a preference the way "no onion" is. It changes what the cook does to that pan: how much chili goes in at the tadka, and whether the heat is built from powder or from fresh green chili. Four dishes at four heats is four pans with four different spice calls, and the ticket has to say so dish by dish.
The failure mode is not mishearing. It is compression. A generic order-taking agent hears "medium" once in a sentence, writes it to the order, and every dish on that ticket inherits it. The kitchen either follows the ticket and gets it wrong, or ignores the ticket and calls the counter. Both are slower than answering the phone.
Callers also say "mild" when they mean "no chili at all", and "Indian hot" when they mean the heat they had in Hyderabad. Neither is a number. The agent can only repeat what it recorded, so the shop has to decide what its three or four levels mean and write it down.
What a thali asks the agent to carry
A thali is not a dish. It is a tray with a fixed set of compartments, and the phone version of it is a single menu item that hides six to eight decisions.
Dal, sabzi, rice, bread, salad, pickle, a sweet, sometimes a papad. Some shops let the caller pick the sabzi and the sweet, some fix the whole tray and vary it by day, and some let them pick two sabzis. On a menu screen that is a nested choice group. On a phone line it is a caller saying "the thali, but not the sweet, and extra roti" while a child shouts in the background.
An agent that flattens this into free text has produced a note, not an order, and the kitchen will assemble a tray and guess. The menu sync guide covers how a menu survives the trip from the POS into the phone; the part that matters here is the shape of the item, because a thali that was modelled as a paragraph can only ever come out as a paragraph.
The practical test: order two thalis with different sabzis and one bread substitution, then check whether the ticket has two trays or one line item with a paragraph under it.
The vegetarian and vegan split, priced per dish
An Indian menu usually carries a vegetarian version of nearly every dish, which makes this vertical unusual: the vegetarian caller is ordering the house's own food, not asking for a substitution.
What breaks on the phone is protein. Paneer, chicken, lamb, and prawn versions of the same curry sit next to each other with different prices, and a caller who says "the korma" without naming the protein has said nothing the kitchen can cook. The agent has to ask, once, and it has to ask the right way.
Vegan is the harder half. Ghee, cream, yogurt, and paneer are in dishes that do not mention dairy on the menu, and no phone system can reason about that. Kovo holds no allergen or ingredient database, so a vegan caller with a strict diet is a person call. Say so on the line and set the handset number; an agent that guesses here is worse than a busy signal.
The Friday arithmetic, with your own ticket
Do this with your numbers, not a national average.
Take your average phone ticket, count the calls you know you missed on Friday and Saturday, and multiply by four weekends. At a $62 family ticket and 8 missed calls a week, that is $496 a week, or $1,984 a month. At 12 missed calls and a $48 lunch-and-dinner mix, it is $576 a week.
The published ranges are the sanity check, not the answer. Industry estimates put a missed restaurant call at $35 to $85, and the same QSR Magazine analysis estimates the average restaurant misses around 150 calls a month. For an Indian restaurant with a Friday thali rush, the missed calls are not spread evenly: they land between 6 and 8, when the counter is taking walk-ins and the kitchen is printing. The missed-call math walks the same multiplication with the ranges spelled out.
Where the caps and the gaps land
Two limits decide whether a phone agent fits an Indian restaurant, and both arrive earlier here than in most verticals.
The first is the order cap. Kovo will not send an order above 10 items in total or more than 8 of one item. An Indian family order of six curries, two rice, four breads, and two sweets passes 10 items without trying. Those calls are usually a party or a catering inquiry where someone needs to talk about timing and trays, so the phone still needs a written path for them and a person at the other end.
The second is what the agent genuinely cannot do. It books tables in its own book, but not into OpenTable or Resy, so a caller asking for six at 7:30 gets a seat in Kovo's book or a handset. It carries no ingredient database, and it quotes only the wait the owner set, so the "twenty minutes" a caller hears is a policy the owner wrote.
What Kovo does on an Indian line
Kovo answers, builds the order as the caller speaks it, reads the whole ticket back, and sends it to Toast, Square, Clover, Olo, or an Epson or Star printer. Menu questions, hours, recommendations, and complaints 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.
The parts that matter for this cuisine are structural. Nested choice groups keep a thali a tray and a heat level attached to one dish. A menu built from the POS catalog or the shop's menu page refreshes once a day, and the call path pulls again when the menu is two days old, so a sold-out dish stops being offered after the next refresh rather than at the moment the kitchen 86s it.
Payment is the part to get right before you sign. No card number is typed into the call. A card the shop already holds is charged while the caller is on the line; a first-time caller gets a link. If cards are on, the ticket is held and a Stripe Checkout link goes to the caller's number; the caller types the card on Stripe's page, and the ticket releases when payment clears. If cards are off, the order confirms on the call and the caller pays when they collect. The Toast routing page shows what the printed ticket looks like on one of the four systems.
Who this is wrong for
If your phone is mostly reservations for a dining room with a tandoor at the front and a tasting menu, buy a reservation platform, not an order-taking agent. Kovo books its own tables but writes into no platform book, and a guest who wanted that chair in OpenTable will not be helped by a product that takes a takeaway order well.
If your menu changes daily and the kitchen writes it on a board at 4 p.m., the menu sync will lag by a day, and a caller will hear about a dish you do not have. Fix the menu pipeline before you buy the phone.
And if most of your calls are catering for 60 people, the order caps will refuse the exact business you want. That is a person-and-a-quote problem.
FAQ
Can an AI phone agent take a spice level for each dish on the order?
It can if the menu model carries heat as a choice group attached to the item, which is how Kovo handles modifiers. The agent then records mild for the dal and hot for the vindaloo as two separate selections rather than one instruction for the ticket. Test it on a demo call: order 4 dishes at 4 heats and read the printed ticket yourself.
How does the agent handle a thali or a combo platter?
A thali is one item with 6 to 8 compartments, and each compartment can have its own choices, which is what nested choice groups exist for. Kovo keeps that structure, so the ticket shows the dal, the sabzi, the rice, the bread, and the sweet separately instead of a paragraph in the notes field. If the kitchen assembles thalis from a fixed set, model each version as its own item instead.
What happens to a large catering or party order?
Orders above 10 items in total or more than 8 of one item are not sent to the kitchen. An Indian restaurant hits the 10-item cap fast, because a family order of eight dishes plus rice and breads is ordinary Friday business. Kovo tells the caller no and does not route the call to a manager, so party and catering calls need a handset number and a person.
Does the agent know which dishes contain nuts or dairy?
No. Kovo holds no allergen database, and Indian menus use ghee, cream, cashew paste, and yogurt in ways a caller cannot see. A caller with an allergy has to reach a person: Kovo answers from 4 first-party sources, your site, menu, FAQs, and hours, and none of them is an ingredient list. Set the handset number and put allergy questions on it.
How much does an Indian restaurant 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 is no per-minute fee and no overage: when the month runs out, calls forward to your own line. At a $62 family ticket, two recovered calls a month covers a real share of Starter.
Final Thoughts
The decision for an Indian restaurant is not whether the agent can hear "thali". It is whether the product keeps heat attached to the dish, keeps a tray a tray, and gets out of the way when a caller has an allergy or a party. Those three tests separate an order-taking agent from an answering machine, and the heat test is the one your kitchen notices first.
Kovo records the heat per dish, reads the whole ticket back, and prints it to the POS you already run, from $99 a month with 14 days free and no card. The sushi counter guide is the same test applied to a split menu, and the blog index has the rest of the verticals. Call in your own hardest ticket, four dishes at four heats, and read what the kitchen receives. Take a test call.