Nothing to pay to be called
When the customer dials, your business is charged nothing. Money only ever changes hands on calls your team places.
A customer taps call inside the thread. It rings in the inbox, an agent answers with the whole exchange already on screen, and the call files itself against that contact.
Start free trial7 days free · No credit card · Cancel anytime
Incoming callFree to take
A busy line is never handed a second caller, and a call belongs to whoever picks it up first. Any agent reaching for it afterwards is told it has already been answered.
The thread is already open on the customer's phone. Letting them press call inside it adds no bill for you to watch and no equipment for your team to look after.
When the customer dials, your business is charged nothing. Money only ever changes hands on calls your team places.
Voice rides the same WhatsApp Business number your team already replies from. There is no second line to buy, no switchboard to wire up, nothing for agents to install.
The agent picking up is looking at the messages, the contact fields and the team's private notes while the phone is still ringing. Nobody is asked to explain themselves twice.
A call opens or renews the 24-hour customer service window, so the message you send afterwards carries no extra fee.
A call writes itself into the conversation under the same contact, and every step it goes through gets its own line: that it rang, whether anyone picked up, whether it went unanswered, and how long the two sides were connected. Each of them waits there for whoever opens the thread next.
Voice call in progress04:12
Hi there, could someone talk me through the delivery options?
Voice call · taken by ALSending over the two options we just went through.
Each number carries its own answer rule, and you set it per number rather than once for the account. One of them suits a line a single person owns; the other suits a line the room shares.
The out-of-the-box rule. A call goes to whoever owns the number. If that person is already talking to someone else and a teammate assigned to the number is free, the free teammate gets it instead. Nobody who is mid-call is ever handed a second caller.
Flip the number to ring all agents and the call reaches every signed-in teammate who has access to it. Nobody is nominated in advance, which is what you want on a support line where the fastest free pair of hands should win.
Accepting a call claims it outright. A second agent reaching for the same one is turned away with a plain "already answered" rather than being dropped onto a customer who is mid-sentence with a colleague.
Roles decide each one on its own, and each can be narrowed: every contact, only contacts already saved, or only the chats assigned to that agent. Seeing the call history is a third right again.
Every step a call goes through raises its own event, from placed and connected to ended, failed and missed. Point your automation at the missed one and the reply is already moving while the caller is still putting the phone down.
Nobody was free · the customer still heard back · the callback is waiting for the morning shift
The controls sit beside everything else that number does. Run voice on the sales line and leave the billing line silent, or change your mind on a Tuesday afternoon.
Weekly opening hours with a timezone of their own, plus a holiday schedule for the days you are shut. The button stops offering a call nobody is there to answer.
Hide it and the number goes back to being a messaging number, with no visible way in for voice.
Stop incoming calls on a number without touching the messaging that runs on it, which is what you want for the week your team is short-handed.
Decide whether agents may return a call from inside the chat, or keep the number strictly one-way and inbound.
Each row carries the direction, the outcome, the name against it and the connected time. The clock starts when the two sides join, not when the phone starts ringing, so a long wait never pads out a short conversation.
| Contact | Direction | Agent | Status | Duration |
|---|---|---|---|---|
| +1 415 ··· ···· | Inbound | AL | Answered | 4:12 |
| +44 7·· ··· ··· | Outbound | DM | Answered | 2:41 |
| +49 1·· ··· ··· | Inbound | None | Missed | None |
| +1 415 ··· ···· | Inbound | KT | Answered | 6:03 |
Illustrative log. Numbers are masked and agents are initials.
WhatsApp will not let a business ring whoever it likes, which is precisely why people pick up when you do call. They say yes once, and the line stays open for a week.
A call permission request goes out without leaving the conversation. The same contact can be asked once in any 24-hour period, twice at most across a week.
Their answer makes that contact callable on the spot, with nothing to install on their side and nothing to configure on yours.
The permission holds for a week. If they are away from the phone, try again inside that week instead of asking a second time.
What an outgoing minute costs depends on where it lands. Every destination carries its own rate, that rate steps down as your monthly volume to the destination grows, and the counter returns to zero when a new month starts.
The meter only starts once somebody picks up. Placing the call, sitting through the ring tone and hanging up unanswered all cost nothing. Voice is metered separately and leaves your messaging bill alone.
Voice is part of the official WhatsApp Business API, so qualifying is really a question about the number rather than about WaliChat. A number already on the API usually clears all five and only wants the last one flipped.
Migrating it to the WhatsApp Business API costs nothing, and neither the number nor the conversations already in it change hands. Your customers see no difference.
How connecting worksReceiving follows the WhatsApp Business API's own map, minus a handful of embargoed territories:
Dialling out is narrower. A business number registered in any of these cannot place calls yet:
Both lists belong to Meta and are theirs to change.
Voice is not a closed feature with a screen you can only look at. Every state a call passes through is delivered to your endpoint, so a call can update a CRM, open a ticket or start a follow-up without anyone retyping it.
Webhook events a call raises
Each one carries the call, the contact and the agent it was routed to.
No. Whenever the customer is the one dialling, your business pays nothing at all. Charges only ever attach to calls your own team places.
One thing does. The customer has to grant permission before you can dial, and once they have you can ring straight away or at any point over the following week. The asking itself is rate-limited, so the same contact can receive one request in any 24-hour period and two across a week.
At the moment of pickup. Everything before it is free: placing the call, the ring tone, a call nobody takes. From pickup the clock runs in six-second blocks, and a part-used block counts as a whole one.
No. Voice is billed on its own. A call also opens or refreshes the 24-hour customer service window, which is the period where free-form replies carry no extra fee.
That follows the answer rule set on the number. Left alone, one agent rings: the person who owns the number, or a free teammate assigned to it when the owner is mid-call. Switch the number to ring everyone and every signed-in agent with access to it rings, and whoever accepts first keeps the call.
A browser, a working connection, and some way to speak and listen, whether that is a headset or the machine's own mic and speakers. Calls run inside the WaliChat inbox, so there is no client to install and no extension number to remember.
Not while it stays paired that way. Voice is an API-only capability. Migrating the number onto the WhatsApp Business API costs nothing and leaves both the number and its archive of conversations intact.
Join 5,000+ teams already using WaliChat to grow faster.