The price depends on two things only — the message category, and the country code of the number you message. Where your company is registered doesn't matter.
Meta’s list rates per delivered template message, in the currency Meta bills each market. These are the markets for which we can point at a published figure — for anything else, use your own rate card in the calculator.
Rates are quoted from Meta’s published rate cards effective 1 July 2026, and from provider documentation where Meta publishes per-currency CSVs rather than inline figures. Meta updates rates only on 1 January, 1 April, 1 July and 1 October, with at least one month’s notice, and bills several markets in local currency — India in INR since January 2026, Brazil in BRL since July 2026. Utility and authentication rates fall with monthly volume; marketing rates never do. Pull the live card for your recipient countries before committing a budget: we do this with you during onboarding.
Any business or solution provider without a payment method registered with Meta by 30 September has service message delivery halted the moment charging begins on 1 October. This catches accounts that have only ever sent free in-window replies and so never needed to pay Meta anything.
Beyond the per-message rate, these are the rules that move the number most — and the ones most budgets miss.
Messaging and voice, on Meta's own billing mechanics: per delivered template, and per six-second pulse for outbound calls. Every rate is editable — load a market preset or type in your own card.
USD per delivered message, and USD per minute for outbound voice. Meta does not publish voice rates in its documentation pages, so the voice rate is always yours to enter from your rate card.
An estimate for planning, not a quote. It excludes volume-tier discounts on utility and authentication, local-currency billing, authentication-international rates, failed deliveries you are not charged for, and the whtapis platform fee. Meta charges only for delivered template messages and answered outbound calls.
Every call a customer places to you costs nothing on Meta's side, which is what makes a WhatsApp-first support line viable. You pay only for calls your business initiates, and only when the customer answers — ringing and unanswered attempts are not charged.
Outbound calls also need permission first: a call permission request template, billed at per-message rates. The calculator counts one permission template per outbound attempt, which is the conservative assumption — an approval lasts seven days, so repeat calls inside that window need no new template.
Nine steps from nothing to a live number. We run steps one to eight with you during onboarding — most of the elapsed time is Meta's review queues, not work on your side.
A new number starts with a cap on how many customers you can message in a rolling 24 hours. Send well — low block rates, good quality rating — and Meta raises the tier. Send badly and it drops, which is why campaign throttling and opt-out hygiene are platform features here rather than nice-to-haves.
How we handle campaign throttlingLimits apply to business-initiated conversations in a rolling 24-hour period and are per business phone number. Meta's current thresholds and review criteria are confirmed during onboarding.
Delivery, opt-outs and segment performance against the rates you model above.
Outbound campaigns that end in a conversation, not a delivery report. Replies and call-backs land in a real queue, and opt-outs propagate across every channel.
Every deployment is led by named people on our side and yours — not a ticket queue.
Every connection can come from you or from us — and you can mix per country. Switch later without changing platforms.
Most customers mix: their own trunk in one country, our numbers in another.
Send your markets and volumes and we will pull Meta's live rate card for each one, model the October rule change, and start the account activation in parallel.