Restaurant AI Receptionist Cost India: ₹2/min

Dvaarik is self-serve SaaS today: there is no setup fee and no minimum commitment. You log in, add your services, staff, hours and knowledge, connect channels, and pay only for what your agents actually do.

Credits are prepaid and never expire; at zero balance agents pause gracefully, so there are no surprise bills. Agencies and developers can sell the same platform under their own brand through the white-label partner programme, and set their own client pricing.

Headline per-minute rates in this market are mostly entry tickets to a sales conversation. The number below that matters is not the rate — it is the second column. Every figure was read on the vendor's own page on 21 Jul 2026 and is stored with the sentence it came from in our India AI voice agent pricing index.

We are not claiming to be the cheapest, and you should distrust anyone in this market who does. The claim we will defend is about terms, not the digit: ₹2/min applies to your first minute, at any volume, with nothing to sign.

One methodology note, because it changes how you should read every other comparison page you find. Several Indian vendors publish tables of *rivals'* rates. Trikon's page, for example, lists Bolna at ₹8–11/min — Bolna's own pricing page says 6.00¢, which Bolna itself renders as ₹5.52. We do not source a single number in the table above from a competitor's comparison page, only from each vendor's own site, and we date-stamp it because several of these rates moved within weeks.

Not all of them, and pretending otherwise is how these projects get abandoned in month two.

A two-minute call bills ₹4. Sort your inbound by what a missed one costs you:

• Party, banquet and bulk enquiries. One captured enquiry is worth your per-head price times the guest count — for a 40-guest function that is tens of thousands, and you know that number better than we do. Today Dvaarik is self-serve with no setup fee and no required plan — usage is prepaid credits, voice from ₹2/min with whole-minute billing. This is the calculation that matters most for a restaurant with a function hall.
• Table reservations, especially weekend evenings. A missed booking call at 8pm is a table that goes to whoever picked up.
• Direct delivery and takeaway orders. Every direct order is an order that does not carry your aggregator's commission — whatever that percentage is for you, it is not zero.
• Delivery-zone and "do you deliver to my pincode" questions. Under a minute each, so one billed minute and ₹2 — and the wrong answer costs you the order.
• Menu, price, timing, address, parking. Genuinely low value per call, and genuinely high volume. This is what stops staff from answering the calls above.

The agent's job is to clear the last category instantly and route the first two to a human or into a structured capture. If your phone only ever rings for the last category, be honest with yourself and read the last section of this page.

A cloud kitchen's phone is a different instrument. There is no host stand, no reservation book, and the calls that come in are order status, delivery-zone serviceability, item availability, a repeat customer trying to order directly, and complaints.

The economics also differ. Cloud-kitchen calls are short — "is my order out" and "do you deliver to Kondapur" are one- and two-minute conversations. Billing is whole minutes, so a 70-second call bills two minutes: short calls do not buy you a fraction of a rupee, and you should plan for the rounding rather than against it. Forty calls a day, each billing two minutes, is 2,400 minutes and ₹4,800 a month. Volume can be high without the bill running away, but it is the call count, not the seconds, that drives it.

What we build first for a cloud kitchen, in order:

1. A direct-order line that actually gets answered. The number on your packaging, your Instagram bio and your WhatsApp catalogue. The agent answers 24/7, takes the customer's details and pushes the conversation to WhatsApp where the items are confirmed in writing.
2. Pincode and zone serviceability. A rule set, not a guess. The agent tells the caller yes or no, and the minimum order value for that zone if you have one.
3. Item availability with an owner-controlled pause. When a dish is 86'd or the kitchen is drowning, you flip the agent into enquiry-only mode from your phone. It stops taking orders and starts taking callbacks.
4. Order-status calls off your staff's plate. These are pure interruption cost. Handing them to the agent is usually where a kitchen manager first believes in the thing.

What we deliberately do not build on day one is full spoken ordering with customisations. See the FAQ below for why.

If your restaurant does functions, this is the workflow to build first, and it is where the ₹2/min bill becomes rounding error.

A party enquiry is a long call — three to five minutes — and it is negotiated in the caller's comfort language. The agent's job is not to close it. It is to capture it completely so a human can close it: date, time, guest count, veg and non-veg split, hall or section preferred, budget per head or total, whether they need decor and DJ, and a callback window.

That capture lands as a filled lead row and a WhatsApp summary to the manager. If nobody calls back within your stated window, the Leads agent can call the enquirer back — and to be exact about what that means, outbound calling is only ever to people who contacted you or gave you their number for this purpose. Never a bought list. Never outside permitted calling hours. The agent identifies your restaurant at the start of the call.

For deposits, the Payments agent can send a UPI payment link inside the same conversation, and Dvaarik takes no commission on what you collect. The link opens the caller's UPI app with your payee name and the amount already filled in, so they approve with their PIN and the money reaches your bank account in seconds. You set the deposit amount and the rule for non-payment — hold the slot two hours then release, or escalate to the manager. See how the link flow works on the payments page, and how slot-locking works on the booking page.

Restaurants run on WhatsApp memory. The call ends, and the useful part is what arrives afterwards: the menu PDF, the location pin, the booking time in writing, the advance link, the party package.

The pattern that works is simple and cheap. The voice call takes the booking. A WhatsApp message confirms it in writing — that is ₹2 on our side plus Meta's own conversation charge billed to your account. A reminder goes out a few hours before the slot with a one-tap confirm or release. A released table goes back into the book instead of standing empty at 8:30pm on a Saturday.

In our builds the reminder is the cheapest step and the one owners are most likely to leave out — and it is the one that puts covers back on the book. It costs ₹2 a conversation. A released and refilled two-top on a weekend evening is worth many multiples of that.

For demand that starts on Instagram — a reel, a story, a comment saying MENU — the Instagram agent replies in DM and moves the thread to WhatsApp. Today Dvaarik is self-serve with no setup fee and no required plan — usage is prepaid credits, voice from ₹2/min with whole-minute billing.

Most restaurant AI failures are not accuracy failures. They are permission failures — the agent was allowed to promise something the kitchen could not deliver.

The rules we hard-code on every restaurant build:

• Never assert table availability unless it is connected to a real book or a real rule set. "Let me take your details and the manager will confirm within ten minutes" is a better answer than a confident wrong one.
• Never invent stock. If it is not on the availability list, the agent offers alternatives instead of guessing.
• One-tap pause, owner-controlled. Kitchen overloaded, chef down, power cut — you switch the agent to enquiry-only from your phone and it stops committing to anything.
• Escalation rules the owner wrote. Complaints, allergy questions and anything involving a refund go to a human, immediately, with the transcript.
• No promises about delivery time beyond the window you told us to quote.

The subject described in this section: These are boring and they are the reason the agent survives past its first Saturday night.

Mixed-language calls are the normal case in an Indian restaurant, not the edge case. A caller opens in Telugu, gives the guest count in English, negotiates the per-head budget back in Telugu, and confirms the date in English.

The agent handles 22 scheduled Indian languages plus code-mixed speech — Hinglish, Tenglish, Tanglish — and follows the caller when they switch mid-sentence instead of dragging them back into one language. That matters most on party enquiries, where the person calling for a 40-guest function will not negotiate in their second language.

You can fix the greeting language per outlet — a Hyderabad branch opens in Telugu, a Pune branch in Marathi, both fall back to English on request. All of it sits at the ₹2/min Bharat Standard rate; there is no regional-language surcharge on our side, which is worth checking against whichever vendor you compare us with, because language gating by tier is common in this market. More on the multilingual page.

Today Dvaarik is self-serve with no setup fee and no required plan — usage is prepaid credits, voice from ₹2/min with whole-minute billing. That has to be earned back in calls that carry revenue.

The subject described in this section: It does not pay for itself if:

• Nearly all your volume arrives on aggregator tablets and walk-ins, and the phone rings four or five times a day.
• You are a counter-service outlet with no reservations, no functions and no direct delivery. A WhatsApp catalogue will serve you better and cost you almost nothing.
• Nobody at the restaurant can sit with us for an hour to approve the menu answers, the delivery zones and the escalation wording. An unapproved script should not take real customer calls.

The subject described in this section: It pays back quickly if you have party or bulk enquiries worth thousands each, direct delivery you would rather not hand to an aggregator, weekend reservation pressure, or more than one outlet sharing a number.

If you are unsure, tell us roughly how many calls you miss between 12–3pm and 7–11pm and we will say plainly whether it is worth it — including when it is not. Full offer on the pricing page, and how restaurants use it on the restaurants page.