WhatsApp Call Permission Request: The Approval Gate Before Your Business Can Call a Customer
WhatsApp does not let a business place a voice call to a customer just because a phone number exists. Every outbound call needs explicit permission first — and getting that permission flow wrong is one of the fastest ways to lose calling access entirely, sometimes for days at a stretch.
What a Call Permission Request Actually Does
The call_permission_request interactive message asks a WhatsApp user to grant your business phone number permission to call them — temporarily or permanently. Since November 2025, users can grant permanent permission, reviewable and revocable at any time from their own business profile settings. Until permission is granted, the WhatsApp Business Calling API will not let a call connect.
What It Requires
Calling enabled on the business phone number, active WhatsApp Business Messaging permission, and a business meeting the minimum daily messaging tier — before any permission request can even be sent.
What It Unlocks
A connected outbound call, capped at 100 connected calls per business phone number every 24 hours, once the customer has responded.
How It Expires
Temporary permission lasts 7 days from approval. Permanent permission does not expire but is still capped by the same connected-calls limit, and the customer can revoke it at any time.
Free-Form vs Template: Two Very Different Submission Paths
A permission request can go out two ways, and each has its own rules. A free-form interactive request only works inside an open customer service window, supports a body message only with no header or footer, and needs no template approval. A template message can be sent outside that window, but it must be created and approved first, with the call_permission_request component configured correctly and a required body — get the category wrong, marketing content dressed up as utility or the reverse, and the template stalls in review or gets rejected outright.
The Rate Limits That Catch Businesses Off Guard
Permission requests are not unlimited, and the caps only reset once a connected call actually happens between the business and that customer.
| Limit | Scope | Value |
|---|---|---|
| Requests per day | Per business + customer pair | Maximum 1 in 24 hours |
| Requests per week | Per business + customer pair | Maximum 2 in 7 days |
| Connected calls | Per business phone number | Maximum 100 every 24 hours |
| Temporary permission | Per business + customer pair | Expires after 7 days |
Why These Setups Get Stuck
- Sending a free-form request outside the customer service window, which fails to deliver instead of reaching the user
- Submitting a call permission template under the wrong category, so it stalls in review or gets rejected
- Burning both weekly permission-request attempts on a customer who never responds, then having no way to ask again for days
- Sending requests to WhatsApp users on an outdated app version, which returns error 131026 instead of delivering the request
- No webhook handling in place to read the call_permission_reply event, so the business has no record of whether permission was granted, declined, or is still pending
- Ignoring the consecutive-unanswered-call rule until permission is revoked automatically mid-campaign
What a Proper Calling Permission Setup Involves
Confirm calling eligibility
Verifying the business phone number has calling enabled, correct messaging permission, and the daily messaging tier the Calling API requires.
Choose the right request path
Deciding between a free-form request inside an open session or a properly categorized, pre-approved template for outreach outside that window.
Build the webhook handling
Capturing the call_permission_reply event so the current permission state — granted, temporary, permanent, declined, or revoked — is always known before a call is attempted.
Pace requests against the limits
Sequencing permission requests so the 24-hour and 7-day caps are not burned on unresponsive numbers, and so unanswered-call thresholds do not trigger an automatic revoke.
Two consecutive unanswered business-initiated calls trigger a system prompt asking the customer to reconsider their permission. Four consecutive unanswered calls revoke the permission automatically — and Meta does not expose a running counter for this in the dashboard, so it is easy to cross that line without noticing.
I set up WhatsApp Business Calling and permission-request flows as part of WhatsApp API approval and setup support — configuring the request path, the webhook handling, and the pacing needed to keep calling access active. If your account is also hitting messaging-limit errors, see the related breakdown of WhatsApp error 131064.