A complete WhatsApp Business Calling budget separates free user initiated calls from chargeable business initiated usage. It groups connected duration by destination and monthly tier, then adds permission messages, provider fees, implementation, staffing and quality control.
Start with call direction
Meta's current Calling API pricing says all user initiated calls are free. Businesses are charged for calls using duration, the country code of the number being called and the monthly volume tier. Do not blend those directions into one average price.
Begin with two counts. First, how many customers are expected to call the business? Second, how many outbound attempts will the business place after receiving call permission? Then estimate how many outbound attempts will be answered. Meta's call webhooks can mark an unanswered call completed without a start time, end time or duration. Keep those attempts in the operating forecast even though they do not contribute connected duration.
The setup guide explains eligibility, permissions, media and testing. The call versus chat guide helps decide which customer moments justify a live call. Both decisions shape volume before any rate is applied.
Convert duration into billable units
Meta calculates duration in six second pulses and counts a fractional pulse as a full pulse. A 56 second call is therefore ten pulses, not 9.33. Forecasting only whole minutes will be wrong when a service makes many short calls.
Use call level data where possible. For each connected business initiated call, round duration up to the next six second pulse, assign the recipient country and apply the rate for the applicable monthly tier. Meta says that when one call crosses a tier boundary, the entire call receives the lower rate associated with the higher volume tier.
| Budget line | Input to measure | Keep separate from |
|---|---|---|
| User initiated calls | Offered, answered and handling time | Meta outbound usage charge |
| Business initiated calls | Connected pulses by recipient country | Unanswered attempts and permission work |
| Permission requests | Free form or template message volume | Calling duration |
| Provider layer | Subscription, seats and usage fees | Meta rate card |
| Operations | Integration, staffing, training and QA | Provider invoice |
Use the current currency card. Meta records an October market-row update without a rate or tier-threshold change.
Build a range instead of one total
A forecast should have a base case and a stress case. Vary the answer rate, average connected duration, destination mix and total monthly minutes. A small change in any one assumption can move the result, especially when calls are short or the recipient markets differ.
Permission requests are another line. Meta states that their messages are subject to messaging pricing. Use the WhatsApp API cost model to keep message charges distinct from calling charges. Also model the staff time spent requesting permission, handling declines and deciding what happens after an unanswered attempt.
The full Calling API overview lists technical prerequisites and current availability restrictions. Treat eligibility as a gate, not a discount. A low forecast is irrelevant if the business number, market, app or media path cannot support the intended flow.
Add the costs outside Meta's rate card
Ask the provider to itemise subscription, seat, recording, storage, transcription, support and usage charges. Meta currently says its Calling API recording and transcription features have no extra charge, while also saying separate pricing is planned with no launch date. That statement does not prove a provider offers them free.
Add implementation and operating work. The budget may need WebRTC or SIP engineering, webhook monitoring, consent-state storage, routing, opening hours, missed-call handling, agent training, quality review and incident support. Include paid time for user initiated calls as well: free platform usage does not mean free service delivery.
The WhatsApp Business API guide explains access. DripTell's WhatsApp channel page and shared inbox page document messaging and ownership, not Calling API enablement. Confirm calling support separately.
Reconcile forecast with actual analytics
After launch, compare the forecast with official call analytics, which can expose cost, completed-call counts and average duration. Reconcile by direction, recipient country and month. Investigate changes in answer rate and short-call mix before assuming the rate card changed.
Keep outcomes beside cost. Check that the customer reached the right team and the written conversation records the promised next step.
Frequently asked questions
Are incoming WhatsApp Business calls free
Meta's current Calling API pricing page says all user initiated calls are free. Staffing, provider and integration costs still apply.
How is outbound call duration rounded
Duration is calculated in six second pulses and any fractional pulse is rounded up to a full pulse. Model at call level when short calls are common.
Which country determines the calling rate
Meta says the country code of the number being called determines the country input. Use the current official rate card for the account currency and date.
Should one budget include messaging and calling
They can share a total, but keep their calculations separate. Permission requests can create messaging charges, while connected business initiated duration follows the calling rate card.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
