The quick answer
Business calling can bring a customer conversation from chat to voice, subject to Meta eligibility, configuration and customer call permission. Reliable operation also needs available agents, working microphones, missed-call handling and a deliberate policy for recordings and summaries.
Some questions are easier to resolve in a short call. A customer may need help choosing a service, explaining an installation issue or understanding a quotation. Keeping that call linked to the conversation can make the next handover much clearer.
The call button is only the visible part. Before a team relies on WhatsApp calling, it needs to understand who can be called, which agent is available, what happens when another call arrives and whether a recording may be made and retained.
Confirm calling readiness for the actual number
If you retain the Business App through coexistence, verify calling support separately. Keeping app access does not establish Calling API eligibility for the same number.
WhatsApp business calling is a configured capability, not something every connected number should be assumed to have. Check current Meta eligibility and country availability, the business account’s calling settings and the provider connection used by your workspace.
Separate three checks: the account is eligible, the application is configured and the agent’s browser can carry audio. An account-ready label cannot prove that a laptop microphone is permitted or that a company network allows the required real-time connection.
For Wamigos setup, ask for a complete test with the actual business number, an authorised test customer and the agent device. A successful signal that starts ringing is useful, but the acceptance test should also confirm two-way audio, a clean end state and the resulting conversation record.
Check customer call permission before dialling
Meta requires user permission before a business-initiated WhatsApp call. The connected calling service should check the current permission state and guide the agent through the supported request process when needed. An open messaging window is not the same as call permission.
Explain why the call would help and let the customer choose. “Would you like a short call to review the installation options?” is more respectful than repeatedly asking for permission without context. Do not treat a recorded consent decision as permanently valid without checking its current status.
If permission is unavailable or the person prefers text, continue through an appropriate messaging route. The aim is to solve the customer’s problem, not to make every conversation become a call.
Prepare the agent’s device and queue
Let agents choose the correct microphone and test it before calling. Headsets, browser permissions, Bluetooth devices and a laptop’s built-in microphone can produce very different results. Include a visible ringing state and an audible incoming-call alert, while accounting for browsers that require a user interaction before playing sound.
Agree what happens when every agent is busy. The next caller needs a clear missed-call or callback journey rather than disappearing behind the active call. A notification should lead to the right contact, and taking the follow-up should have a visible owner.
| Situation | Operational response |
|---|---|
| Microphone denied | Explain how to enable it and retest before dialling |
| Agent already on a call | Preserve the current call and route or record the next attempt |
| Customer does not answer | Record the outcome and follow an appropriate callback policy |
| Connection interrupted | Show the uncertain state and reconcile before repeated retries |
| Call completed | Save the outcome and the next action against the contact |
Make recording a deliberate business policy
Decide why the business records calls, what notice and consent are required, who may access a recording and how long it is retained. Requirements vary by jurisdiction and situation; a platform setting does not replace the business’s legal assessment.
If administrators require recording, make the rule clear to agents and customers and test what happens when recording cannot start. Do not imply that a call was recorded merely because a recording option was enabled. The stored artifact needs its own successful outcome.
Recordings should be private, linked to the correct customer and available only to authorised users. A copied playback link should not become a permanent public URL. Consider how exports, deletion requests and any retention exceptions are handled.
Use AI summaries as reviewed working notes
An AI summary needs usable audio or transcript evidence and a working model connection. If no recording exists, the product should say so rather than inventing a conversation. If transcription is still processing, show that state separately from a failed summary.
A useful summary captures the reason for the call, agreed decisions, unresolved questions and the next action. Avoid turning tentative customer comments into confirmed orders or payment commitments. Agents should be able to review important details against the recording where authorised.
Keep summary access aligned with the underlying conversation. A short summary can still contain personal information. Include recordings, transcripts and derived notes in the business’s access, retention and deletion processes.
Prove capacity and understand the complete cost
Call capacity depends on Meta limits, the calling architecture, agent sessions, network conditions and the supporting services. A synthetic concurrency test can check software coordination, but it cannot prove the audio quality of many simultaneously answered calls on real customer devices.
Test progressively with separate consenting phones and agent sessions, then review connection time, failed attempts, audio quality, missed-call handling and saved outcomes. Publish an operational capacity only when that level has evidence and a monitoring plan.
Separate current Meta call charges from software usage, real-time media transport, recording storage and optional transcription or summarisation. Ask for the rate and charging unit for each part. Do not assume a messaging subscription includes unlimited voice minutes or permanent recording storage.
Common questions
Can we call any customer with an open WhatsApp chat?
No. Check current calling eligibility and user call permission. A messaging conversation and permission for a business-initiated call are different.
Must an agent request permission again before every call?
Check the permission state returned by the calling service and Meta’s current rules. Do not assume permission is either always permanent or always required afresh.
Are recordings automatically available for every call?
Only if recording is configured, permitted for that situation and successfully captured and stored. A completed call alone is not proof of a recording.
Can an AI summary replace listening to the call?
Use it as a working aid. Verify important commitments and uncertain details against the authorised recording or transcript, particularly before changing an order or payment.
How many simultaneous calls can our business handle?
Use a tested operating limit for your actual setup. Include Meta constraints, available agents and real audio tests; a theoretical service quota is not a complete answer.
Sources & further reading
Primary documentation reviewed 16 November 2026. Provider rules, pricing and eligibility can change. Check the linked source before making account or billing changes.






