An AI Phone Agent for Your Restaurant: What It Can and Cannot Do

AI Phone Calls in the Muncho dashboard lets you build agents, answer inbound calls, review call and chat history, and manage numbers and credits. It is available on Pro, which also includes reservations. The annual plan fee covers the software; call usage is paid from your wallet.

This post is the honest scope. It is more useful than a feature list.

What is in the section?

Open AI Phone Calls in the sidebar and you get a grouped set of pages:

• Agent: Agents, New Agent
• Campaigns: Campaigns
• History: Call History, Chat History, Scheduled Calls
• Numbers: My Numbers, Buy Numbers
• Developers: API Keys, API Docs
• Account: Billing

Check your agent instructions and test the guest questions you expect before directing your restaurant calls to it.

Under the covers this is a white-label embed of a full voice platform inside the Muncho dashboard, which is why the page layout feels different from the rest of the sidebar and why the feature set is deeper than a restaurant add-on usually is.

What can it genuinely do today?

• Build an agent. A voice agent with your instructions, your greeting and your tone.
• Answer inbound calls on a number you own or buy.
• Handle inbound questions about your menu, hours and location.
• Keep history. Call History, Chat History and Scheduled Calls, all reviewable.
• Manage numbers and credits.

The honest use case for most restaurants is the call you are currently missing. A phone ringing at 7.30 on a Saturday while every member of staff is carrying something is a lost order or a lost table, every time. An agent that answers, knows your hours, knows whether you are open, and can take a message is worth more than a clever one that does nothing reliably.

What can it not do?

It cannot place an order into your ordering system. Agent-placed ordering is not exposed.

It cannot top itself up. You add money to your restaurant wallet through Add money in the dashboard. Usage is charged to that balance.

Test these limits before you decide how much of the front desk to put on the phone agent.

Who should have access?

Two staff permissions, and getting them right matters because this section can spend money.

• phone_calls controls access to the section at all.
• phone_calls_admin separately controls Buy Numbers, API Keys and Billing.

So a front-desk login can review call history and still be unable to buy a number or see the billing page. Set it that way. The default is not the safe one for a venue with ten staff logins.

Note also that the section is visible for every restaurant by default. A venue that has not been enabled commercially still sees it and gets an upsell rather than an empty menu, which occasionally confuses owners who think they have bought something they have not.

What does it cost?

The India pricing card is annual per outlet, plus GST: Plus Rs 11,999 and Pro Rs 23,999. AI calls are on Pro, with no limit on how many run at the same time. Plus has no AI calls.

AI calls cost Rs 4 a minute from your wallet, charged in 30 second steps. A Muncho phone number costs Rs 500 a month, and calls on it add Rs 0.50 a minute. Use Add money in the dashboard to top up the restaurant wallet; top-ups are valid for 365 days.

The thing to model is minutes, not calls. A well-scoped agent that answers hours and location questions runs short calls. An agent asked to handle a long, meandering conversation runs long ones, and the bill follows the minutes.

How should you scope the agent?

Narrow, and then widen it.

Start with the three questions your phone actually gets: are you open, where are you, and do you have a table. The first two the agent can answer perfectly. The third it can take a message about and hand to a person.

Write the instructions the way you would brief a new host, in plain sentences, with the specifics that are genuinely yours: the entrance that is hard to find, the parking, the fact that the kitchen closes before the bar does.

Then listen to the Call History for a week. The gap between what you told the agent and what people actually ask is where the second version comes from.

Where does it fit against everything else?

The phone is the channel Muncho covers least well elsewhere, which is exactly why this section exists.

A guest at a table has the QR menu. A guest at home has your delivery or pickup link. A guest who paid gets a review prompt and a receipt on WhatsApp. The person on the phone got nothing, until now.

Treat it as coverage for that gap rather than as a replacement for a host. The agent is good at never being busy. Keep staff involved for requests that need human judgement.

What to do first

1. Check your permissions before anyone else logs in. Turn phone_calls_admin off for everyone who does not need to spend money.
2. Buy or connect one number and point it somewhere that is not your main line.
3. Write a short agent covering hours, location and menu basics.
4. Call it yourself, twice, once asking something easy and once asking something you know it cannot do.
5. Read the transcript. That one reading tells you more than any amount of configuration.
6. Decide honestly whether the calls you are missing are worth the minutes.

If the answer is yes, widen the scope slowly. Check Pro for the restaurant tools and usage prices before choosing your plan.