Does the AI receptionist answer WhatsApp calls?

The NexBuilt receptionist sits on the shop phone, not inside a WhatsApp voice call. A WhatsApp call is a different channel, and the fallback is a chat reply or the number on the board.

I will not tell a salon in Greater Kailash or a restaurant in Khan Market that the green button is covered because the board number is covered. Those are two rings.

What the default voice job actually answers

An AI voice agent picks up the business line people already dial from the listing, the card, and the glass. It says it is an assistant. It answers the usual questions. It can take a slot. It leaves you a log.

A WhatsApp call is a tap inside the app. The person never left WhatsApp. The shop phone may not ring at all. Covering the SIM does not cover that tap.

Chat versus a phone call is which channel holds the customer. This page is only the WhatsApp voice tap.

A shop-phone agent starts at Rs 25,000 on pricing. Chat starts at Rs 15,000. The default pair is a phone agent and a chat list, not a WhatsApp voice agent.

What Meta published about WhatsApp calling on the API

Meta’s Cloud API Calling page describes voice and video calls over WhatsApp using their Calling API. That page says the business number must be in use with Cloud API, not the WhatsApp Business app. It also says the business must have a daily messaging limit of at least 2,000 unique recipients, and that calling features must be enabled on the number.

That is a real product. It is not the default receptionist NexBuilt ships to a single chair. I will not sell it by renaming the shop-phone agent.

Their calling price page says all user-initiated calls are free, and that business-initiated calls are billed by duration, country and volume. I will not invent an India rupee minute from that page.

How to set up WhatsApp Business walks through the free install. The free app is not Cloud API. A tap-to-call on the free app is still a person, or it is silence.

The honest fallback

If they wanted a WhatsApp voice and nobody answers, they can type. Chat on WhatsApp can answer the fee, the hour, and a slot from the list you wrote.

If they wanted a voice and will leave the app, they can dial the number on the board. The agent can speak Hindi on that line if the card is written that way.

Put both paths on the profile. Hours. The board number. A pinned note that says write here for a slot. Do not pin “call us on WhatsApp” if nobody will pick up that tap.

A Khan Market floor that already loses the 8:30 table to a ringing SIM will not fix it by enabling a second voice product they have not staffed. Pick the ring that is actually dying.

When a WhatsApp calling build would even be in scope

Only if you are already on Cloud API, already past the messaging limit their docs name, and already sure the tap is the leak. That is a later conversation. I will not bundle it into the first voice floor so the quote looks full.

I will not invent how many Delhi customers now call on WhatsApp instead of the board. Count your own taps for a week. If the tap pile is rare and the SIM pile is the week, start with the SIM.

Downsides of leaving the tap unanswered

People who only live in WhatsApp will think the shop is shut. A missed tap feels like a missed call.

A pinned “call us” that nobody answers is worse than no pin.

Turning on Cloud API calling without a person or an agent on that path creates a new dead ring. Do not add a channel you will not staff.

I will not tell you covering WhatsApp calls raises tables by a figure I cannot see. The gain, if there is one, is the tap that used to die. Count it.

Count the taps, then pick the ring

Open WhatsApp. See whether people are tapping call or typing. See whether the board number is still the listing number.

Then get in touch. Bring one week of taps and one week of missed SIM rings. I will say the shop phone is the job, chat is the job, or the tap is a later Cloud API conversation I will not pretend is already in the floor.