Skip to main content
    New on the WhatsApp Business API

    WhatsApp voice calling for your whole team — finally available on the Business API.

    Voice calling has finally arrived on the WhatsApp Business Cloud API. ChatterSwift makes it work the way support actually runs: any agent on your team picks up, from anywhere they're signed in.

    See how it works

    What used to take a full day of chat now wraps up in a few minutes on a call. That's the difference customers report after moving their support queries to WhatsApp voice calls.

    Why WhatsApp Business calling has been broken until now

    Four reasons businesses on the WhatsApp Business API have been losing customer conversations to slow chat threads and missed calls.

    API users had no calling at all.
    Move to the WhatsApp Business API (or the newer Cloud API) and you unlock templates, automation, and multi-agent chat. You also quietly lose voice. The same number that powered your business calls can't be used in the WhatsApp Business app anymore. Calls just stopped being possible. Until now.
    Calls only ring on one phone.
    On the regular WhatsApp Business app, calls land on whichever phone the number lives on. One device, one person, one chance. Miss it and the customer moves on.
    Resolution times balloon.
    A question that takes two minutes on a call drags out across a full day of chat. Typing. Waiting. Re-explaining. Screenshots. Voice closes the loop in minutes.
    WhatsApp calls don't get marked as spam.
    Cold phone calls get auto-flagged by carriers and Truecaller before the phone even rings. WhatsApp calls work differently. The customer has to approve a Call Permission Request first, so there's no spam filter sitting between you and the conversation.

    How ChatterSwift voice calling works

    Three steps from a WhatsApp conversation to a live call answered by your team.

    1

    Get permission to call.

    Send a Call Permission Request template, or wait for the customer to ping you first. Once permission lands, you can call them back for at least 7 days. Customers can stretch that window all the way to permanent if they want.

    2

    Calls route to your team.

    When a customer calls, every available agent on your team rings at once. Whoever answers first takes it. No more "the person who owns this phone is in a meeting." If anyone's free, the call gets picked up.

    3

    Answer from anywhere.

    Wherever an agent is signed into ChatterSwift, calls reach them. By the time they pick up, the customer's chat history, contact details, and past calls are already on screen. No fumbling through tabs to figure out who's calling.

    A WhatsApp call from a customer routing to multiple available agents on the team

    Built for the way support teams actually work

    Routing, availability, history, and context — designed for shared inboxes on the WhatsApp Business API, not single-owner phones.

    First to answer wins.
    Incoming calls ring every available agent at once. Whoever picks up first takes it. Nothing to configure, no waiting on a single owner.
    Agents decide when they're on duty.
    A simple availability toggle. Agents flip themselves on at the start of a shift and off when they're done, and only the people who are actually around get rung. Breaks and end-of-day stop costing you missed calls from the wrong person.
    Every call lives next to the conversation.
    Every call attaches to the customer's contact, right next to their chat history. So the next agent to talk to them sees the full thread, chats and calls together, without asking them to repeat the whole story.
    A searchable log of every call.
    The team-wide call history shows every call across every agent. Who picked up. Who called. How long it lasted. Handy for performance reviews, and even handier for catching conversations that quietly need a follow-up.

    Inside the call

    When a call connects, the agent already has the customer on screen. Name, contact details, recent chat history, every previous call. No frantic looking up of records mid-conversation. No awkward “could you give me your order number again?”

    While the call is happening, agents can jot notes in a side panel. The moment the call ends, those notes save against the contact. So whoever talks to that customer next, whether by chat or by call, sees exactly what was said.

    It's a small thing that adds up fast. Most customer queries don't get resolved on the first call by the first agent. They bounce around people and days. Notes mean whoever picks up next continues the conversation instead of restarting it.

    ChatterSwift in-call view showing the customer's contact details, chat history, and live WhatsApp call panel with in-call notes

    WhatsApp Call Permission Requests, explained

    A short, plain-English guide to how consent works for WhatsApp Business calling.

    Calling on the WhatsApp Business API doesn't work like a regular phone line. You can't just dial a customer who's never heard of you. Meta requires explicit consent first, through something called a Call Permission Request (CPR). Here's how it actually plays out, on both the WhatsApp Cloud API and the older on-premise Business API.

    What is a Call Permission Request?

    A Call Permission Request is a message template you send to a customer asking if it's okay to call them on WhatsApp. They see a card in their chat with your business name and an “Allow calls” button. Tap Allow, and you can call. Ignore it, and you can't.

    Think of it as the WhatsApp Business API version of “is now a good time to talk?” But this time, the platform enforces the answer. Not just polite convention.

    Two ways permission gets granted

    There are two paths to a callable customer:

    1. You ask first. Send a Call Permission Request template. If the customer approves, you can call.
    2. They call you first. If the customer initiates a call to your business, permission is granted automatically. You can answer, and you can call them back later within the permission window.

    Either way, the customer is in control. They've taken an explicit action that says “yes, I'm okay with voice from this business.”

    How long the permission window lasts

    Once a customer grants permission, you have a window of at least 7 days to call them. They can stretch that window in their WhatsApp settings, all the way to “always”, by choosing to allow calls from your business permanently.

    If the window runs out, you haven't lost the customer. Send another Call Permission Request and the door's open again.

    Why CPR is the reason WhatsApp calls don't get marked as spam

    Cold calls from unknown numbers get auto-flagged by carriers, Truecaller, and built-in spam filters before the phone even rings. WhatsApp calls slip past all of that. Not because they're whitelisted, but because they literally can't happen without consent.

    A customer who just tapped “Allow calls” isn't going to mark the same call as spam thirty seconds later. The consent step replaces the spam filter. That's the whole design.

    Frequently asked questions

    Do I need the WhatsApp Business API to use ChatterSwift voice calling?

    Yes. ChatterSwift runs on the WhatsApp Business API — that's what makes team-wide calling possible in the first place. If you're using the regular WhatsApp Business app today, we'll help you migrate your number to the API when you onboard.

    Does this work with the WhatsApp Cloud API?

    Yes. ChatterSwift runs on the WhatsApp Cloud API — the modern, Meta-hosted version of the Business API. If your number is on the older on-premise API or the WhatsApp Business app, we'll help you migrate to the Cloud API during onboarding so calling works seamlessly.

    How much does WhatsApp Business API calling cost?

    WhatsApp Business API calls are priced per-minute by Meta on top of your standard messaging conversation costs. Rates vary by country — Indian businesses pay India-specific calling rates set by Meta. Use our WhatsApp Business API cost calculator for a live estimate based on your call and message volume.

    How is this different from WhatsApp Web calling?

    WhatsApp Web mirrors a single phone — it's tied to one personal or Business app account, on one device. ChatterSwift gives you proper multi-agent voice on a WhatsApp Business API number: any agent on your team can answer, calls log against the customer record, and you get a team-wide call history. WhatsApp Web has none of that.

    Can mobile agents take calls too?

    Yes — anywhere an agent is signed into ChatterSwift, calls reach them.

    Why don't WhatsApp calls get marked as spam?

    Because they require consent before they can happen. Customers grant permission either by approving a Call Permission Request or by calling you first. Calls without that consent simply don't connect — there's no spam filter needed because there are no unwanted calls to filter.

    Does it work with my existing WhatsApp Business number?

    Yes, if your number is on the WhatsApp Business API (Cloud or on-premise) or eligible to migrate to it. Numbers currently in use on the WhatsApp Business app can be migrated; we walk you through it during onboarding.

    Bring voice into your WhatsApp Business API workflow.

    Voice closes loops that chat just can't. A two-minute call wraps up what would otherwise be a day of back-and-forth. And on the WhatsApp Business API, ChatterSwift is what makes those calls happen across your whole team. Not just one phone. Wondering about cost? Estimate your WhatsApp Business API pricing.

    Talk to sales

    Already on ChatterSwift? Voice calling is included on your plan.