What you'll achieve
When a customer is dealing with a damaged order, a billing dispute, a failed transaction, or a sensitive health question — a slow text thread makes everything worse. Back-and-forth compounds frustration, resolution drags on for days, and CSAT drops with every message that goes unresolved.
This guide shows you how to use WhatsApp Business Calling inside Wati to escalate support conversations to voice in one click — inside the same WhatsApp thread, without asking the customer to switch channels, dial a separate number, or repeat their issue from scratch.
Support teams that add calling see dramatically faster resolution. Hakeem, for example, reduced support resolution times from days to minutes by enabling customers to call directly from the same WhatsApp conversation.
By the end of this guide, you'll have WhatsApp Calling configured for your support team — inbound calling enabled, contact-owner routing live, and recordings with AI summaries logging every call automatically — so your operators can resolve complex issues in a single conversation.
The short version
To set up WhatsApp Calling for your support team and start resolving issues over voice:
Enable calling in Settings → Team Inbox Settings → Call and toggle on "Enable WhatsApp Call" for your business number.
Turn on "Allow Customers to Call Your Business" so customers can reach your team directly — free, no permission needed.
Toggle on "Allow Auto Permission Requests" so the system handles permission re-acquisition after missed callbacks automatically.
Activate call notifications in Manage Notifications → Call so operators are alerted the moment a call comes in.
Test by having a team member call your business number, then confirm the record appears in Team Inbox → Call Logs.
Continue reading for detailed setup instructions and strategic best practices.
When to use this guide
Use this if:
You're on a Growth, Pro, or Business Wati plan and want support operators to handle complex issues over voice without leaving WhatsApp.
Your text threads are dragging — issues that take 10 messages to resolve could be closed in a 2-minute call.
Customers are frustrated or upset and need a human voice, not another chat reply.
You need real-time troubleshooting — a student mid-session, a traveler with a time-sensitive issue etc.
You want call recordings and AI summaries for QA, training, and dispute resolution.
Do NOT use this if:
Your Wati account was onboarded via Coexistence — calling is incompatible with this setup and requires migrating to standard Cloud API onboarding first.
You're looking for a sales or lead conversion calling workflow — see the sales-focused WhatsApp Calling guide instead.
Limitations
Before you invest setup time, confirm your account meets these requirements:
Plan required: Growth, Pro, or Business plans.
Coexistence incompatibility: Accounts onboarded via Coexistence cannot use calling at all.
Outbound country restrictions: Business-Initiated Calls (BIC) are unavailable if your business number is registered in the USA, Canada, Egypt, Vietnam, or Nigeria. Inbound calls from customers are available globally with no country restriction.
Meta messaging throughput gate: Minimum 2,000 business-initiated conversations in a rolling 24-hour window to qualify for Meta's Calling API.
Permission rate limits (outbound only): Max 1 permission request per contact per 24h; max 2 in any 7-day period. Inbound calls require no permission.
Daily outbound call cap: Max 5 connected outbound calls per contact per 24h once permission is granted.
Auto-revocation: After 4 consecutive unanswered outbound calls, permission is revoked automatically.
API access to call data: Wati provides dedicated API endpoints to retrieve call logs, recordings, transcripts, and summaries for calls handled within Wati's infrastructure — individually (
GET /api/ext/v3/calls/{call_id}/recording,/transcript,/summary) or in batch. Webhooks for call events (inbound, outbound, status, termination, permission) and call signaling APIs for CRM/portal integration are also available (Pro and Business plans only, enabled on request by contacting your CSM or Wati support).CRM call-logging limitation: HubSpot/Zoho call logging only captures calls made from the Wati web app, not mobile. Operators making calls they want CRM-logged should use the web platform.
Concurrent call limit: One operator handles one call at a time; max 1,000 inbound and 1,000 outbound concurrent calls per business number.
Before you begin
Wati plan: Growth, Pro, or Business (confirm in Settings → Account Details)
Wallet funded: Min ₹500 (INR accounts) / $10 (USD accounts) for outbound callbacks. Inbound calls are free.
Business phone number: Registered in a BIC-supported country for outbound callbacks (inbound works globally)
Meta messaging throughput: At least 2,000 BIC conversations per 24-hour rolling window
Onboarding type: Standard Cloud API (not Coexistence)
Permissions: Admin access to Wati Settings
Estimated setup time: 10–15 minutes
Key concepts
BIC (Business-Initiated Call)
An outbound call your business places to a customer. Requires prior consent, country-restricted, and billed per connected minute from your Wati wallet.
UIC (User-Initiated Call)
An inbound call the customer places to your business. Always free, globally available, no permission needed. This is the primary flow for support — customers reach out when they need help.
Call Permission Template
A Meta-billed utility message template requesting customer consent to receive outbound calls. Required for BIC only — inbound calls from customers never require a permission request.
How it works
Customer taps the WhatsApp call icon (or operator requests a callback)
↓
Operator receives a notification and answers directly from the Team Inbox
↓
Issue is resolved in real time with full conversation history and context
↓
Call ends and is automatically logged (with AI summaries synced to CRM)
↓
Wallet is billed per connected minute for outbound calls only
(inbound calls are free)
1. Customer calls in or operator requests a callback
Customers tap the call icon in WhatsApp to reach your support team directly (free, no permission needed). For operator-initiated callbacks, a permission request goes out first.
2. Operator receives the call
A browser or app notification alerts the operator, who answers from Team Inbox. Full conversation history — prior messages, shared files, order details — is visible alongside the call.
3. Issue is resolved in real time
The operator handles the issue live with full context, no channel switch, no re-explaining from the customer.
4. Call ends and is logged
Timestamp, duration, and operator name are saved to Call Logs. On Pro/Business with Auto Record enabled, the recording, transcription, and AI summary attach to the thread and sync to your CRM.
5. Wallet is billed (outbound only)
Inbound calls are always free. Outbound calls are billed per connected minute. Unanswered/busy calls are not charged.
Step-by-step setup
Step 1: Activate WhatsApp Calling
Goal: Enable the calling feature on your Wati account.
Steps:
Go to Settings → profile icon → Team Inbox Settings → Call → select your business phone number → toggle on "Enable WhatsApp Call."
Result: Calling is activated for your number and additional configuration toggles appear.
Step 2: Enable Inbound Calling for Customers
Goal: Let customers call your support team directly from WhatsApp.
Steps:
In the same Call settings panel, toggle on "Allow Customers to Call Your Business."
Result: The call icon becomes visible to customers in their WhatsApp conversation — they can call your support team whenever they're ready, with no permission step required.
Step 3: Configure Auto-Permission for Outbound Callbacks
Goal: Keep outbound calling access active without manual permission follow-up.
Steps:
Toggle on "Allow Auto Permission Requests" in the Call settings panel.
Result: If a customer misses an outbound callback attempt, the system automatically sends a new permission request — maintaining calling access without operators chasing consent manually.
Step 4: Enable Call Notifications
Goal: Ensure operators are alerted to incoming support calls in real time.
Steps:
Navigate to Manage Notifications → Call and activate both notification toggles.
Use the Available to take calls toggle to control your status:
Turning it off hides all call notifications and automatically silences the ringing sound.
If you want to remain available but mute the sound, clear the highlighted checkbox.
This lets you receive visual notifications without the audio alert.
Result: Operators receive browser notifications for inbound calls — no missed support calls due to the tab being in the background.
Step 5: Review Call Logs and Monitor Wallet Balance
Goal: Confirm call records are captured and wallet is funded for outbound callbacks.
Steps:
Click the Call icon in Team Inbox → view Missed Calls and All Call Logs.
Navigate to Wallet → Pricing Overview to review rates and current balance.
Result: Full call history visible with operator attribution. Wallet confirmed above minimum thresholds for outbound calling.
Using WhatsApp Calling on the mobile app
Once calling is enabled on your account (Steps 1–5 above), your operators can make and receive support calls directly from the Wati mobile app — no additional account-level setup needed.
Heads up: Calls made from mobile are not logged to HubSpot or Zoho CRM. If CRM logging matters for a call, use the web app instead.
Requirements
Wati mobile app version 3.43.1 or later (iOS or Android)
Device notification permissions enabled
Enable call notifications on your device
iOS: Open the Wati app → grant notification permissions when prompted → select Always Allow to receive calls in the background.
Android: Open Wati → go to the Calls section → tap Open Settings when prompted → enable full-screen notification permissions for incoming calls.
Receive an inbound support call
When a customer calls in, a notification appears on your device. Tap to answer — the call connects inside the Wati app with conversation history accessible alongside.
Make an outbound callback
From Call Logs: Tap Calls in the bottom navigation → find the contact → tap the Call icon. If permission is already granted, the call starts immediately. If not, tap Send Request to request it first.
From a chat: Open the contact's conversation in Team Inbox → tap the Call icon in the top-right corner.
Find contacts with permission ready
Tap the filter dropdown in the Calls section → select Request Accepted → tap Apply.
This shows only contacts who have granted permission, so operators can dial with confidence.
Manage call availability
To stop receiving incoming call notifications on mobile: Settings → Notifications → Calls → toggle off Availability to take calls.
Call activity syncs automatically between the mobile app and the web platform, so logs stay consistent regardless of where the call was made.
Here are some examples by industry
Healthcare: A patient asks about symptoms, a prescription refill, or lab results over chat — text feels too impersonal or slow for a sensitive health topic. The patient (or the clinic) requests a call, and the conversation happens by voice inside the same WhatsApp thread instead of switching to a phone line or patient portal. One conversation replaces a chain of messages that could drag on for hours.
E-commerce & Retail: A customer messages in about a delayed shipment or a damaged item — the kind of issue that triggers frustration fast. Instead of trading messages back and forth, the support operator escalates to a call in one click, handles the complaint live, and closes the ticket in a single conversation.
EdTech: A student hits a technical issue mid-session during a live online class. Rather than waiting on a ticket queue while the class continues, the student requests a callback from within the WhatsApp conversation. The support operator calls back in minutes, resolves the issue in real time, and the student gets back to their session.
Travel & Hospitality: After a booking is confirmed, a hotel or resort operator calls the guest to confirm special requirements — dietary needs, accessibility arrangements, late check-in timing. A two-minute call handles what would otherwise be a slow, multi-message thread, and the guest feels looked after before they've even arrived.
Confirm it's working
To confirm your setup is working, ask a team member to make a test inbound call to your WhatsApp business number.
You should see:
The call icon visible to customers in the WhatsApp conversation.
The incoming call notification appear on the operator's browser or mobile device.
The operator able to answer the call directly from Team Inbox without leaving the conversation.
The completed call appear in Team Inbox → Call icon → All Call Logs with the correct timestamp, operator name, and duration.
For outbound calls, place a test callback to a permissioned contact and check your Wallet balance to confirm that the per-minute charge is deducted correctly.
Success looks like: a customer's call comes in, an operator answers from Team Inbox, and the call record appears automatically in the call logs.
Pro tips for success
The Always-Open Door Play: Turn on "Allow Customers to Call Your Business" and keep it on. Inbound calls are free, require no permission, and put control in the customer's hands. The easier it is to reach a human, the less likely customers are to escalate complaints or churn.
The QA-Ready Recording Play: Turn on Auto Record + AI Summary (Pro/Business) so every support call is documented without anyone lifting a pen. Use transcripts for QA reviews, training new operators, resolving billing disputes, and building a searchable record of how your team handles complex scenarios.
The Owner-Answers Play: Enable contact-owner-based routing (Pro/Business) so the operator who handled the original chat is the one who picks up the phone. No re-explaining, no lost context — the customer feels heard from the first word, and resolution time drops significantly.
The Auto-Permission Callback Loop: Enable "Allow Auto Permission Requests" so the system handles permission re-acquisition after missed callbacks automatically. This keeps your outbound calling access alive without operators chasing consent manually — especially useful for high-volume support teams handling time-sensitive issues.
Troubleshooting
Why isn't the "Call customer" button showing up?
Possible causes
The contact has not granted outbound call permission yet.
Permission was revoked after 4 consecutive unanswered calls.
The operator is not assigned to the team that owns the contact.
Resolution
Check permission status in the Request Accepted view.
Send a new permission request if needed (subject to the 1-per-24-hour rate limit).
Verify the operator's team assignment matches the contact's owning team in Settings.
Why aren't operators receiving incoming call notifications?
Possible causes
Notification toggles in Manage Notifications → Call are not enabled.
Resolution
Go to Manage Notifications → Call and activate both notification toggles for the affected operator.
Why is outbound calling blocked even though the feature is enabled?
Possible causes
Business number is registered in a restricted country (USA, Canada, Egypt, Vietnam, or Nigeria).
Wallet balance is below the minimum threshold (₹500 / $10).
Account was onboarded via Coexistence.
Resolution
Confirm your business number's registered country is not in the restricted list — this is a Meta-level block and cannot be overridden in Wati.
Top up wallet above minimum in Settings → Wallet.
If your account uses Coexistence onboarding, contact Wati support to explore migrating to standard Cloud API onboarding.
Why did my permission request get blocked?
Possible causes
Already sent 1 permission request to this contact within the last 24 hours.
Sent 2+ permission requests in the last 7 days.
Resolution
Wait for the rate limit to reset.
If the customer calls in (UIC) in the meantime, answer and use that live window to resolve the issue — note that a UIC does not grant your business outbound (BIC) permission.
Why is my CRM not logging calls placed from the mobile app?
Possible causes
HubSpot and Zoho CRM call-logging is only triggered by calls made from the Wati web app, not mobile.
Resolution
Ensure operators making CRM-logged calls are using the Wati web platform.
For mobile-only operators, manually log call notes to the CRM until mobile CRM sync is supported.
🚀 What's next
Now that your calls are working in Team Inbox, your next step is to enable Auto Record, Transcription, and AI Summary to automatically capture and summarize support calls. This can help you review conversations, onboard operators, and keep track of what was discussed without relying on memory.