From October 1, 2026, service billing considers delivered messages, a monthly allowance per number, category and exceptions. This guide separates Meta's rate card from platform, AI, infrastructure and operations costs.
The 24-hour CSW, Free Entry Point window of up to 7 days and monthly service allowance have different origins and conditions. Check the rule for each delivery, the available allowance and delivery receipts.
Support · window open
online
Hi, I bought yesterday and still haven't gotten my code.
Hey! Let me check that for you 👀
Scenario-specific ruleFound it! Resending your access right now.
Scenario-specific rulePerfect, thanks so much!
Inbound is not a delivery charge; utility in the CSW and MBA follow their own rules.
Service, utility and authentication remain separate categories. Service has 1,000 free monthly deliveries per number; above that allowance, the Brazil BRL rate card is R$ 0.0350 per delivery. Utility in the CSW does not consume that allowance.
Support · allowance already used
online
Hi, I bought yesterday and still haven't gotten my code.
Hey! Let me check that for you 👀
R$ 0,0350Found it! Resending your access right now.
R$ 0,0350Perfect, thanks so much!
Base rate after the allowance, with no other applicable exemption. Count deliveries rather than attempts: failures and inbound do not enter a billable service-delivery count.
The schedule Meta published for 2026 and 2027. Each milestone changes, in practice, the cost of operating on WhatsApp.
The rule depends on Brazil Sold-To in Billing Hub. Treat it as rollout and eligibility, not as a completed migration for every Brazilian account.
The Meta Business Agent starts charging per token: US$ 2.00 per 1 million tokens, a single global rate — including inside the window and at the free entry point.
Service above its allowance is billed per delivery; utility and authentication have their own categories and tiers.
June 30, 2027 is the deadline for eligible Messaging accounts; on July 1 non-BRL accounts in that scope are interrupted.
Format does not replace category: measure only service deliveries belonging to the declared scenario. Inbound, failure, utility, marketing, authentication and MBA do not share that counter.
Text
R$ 0,0350
Image
R$ 0,0350
Audio
R$ 0,0350
Video
R$ 0,0350
Document
R$ 0,0350
Buttons
R$ 0,0350
Location
R$ 0,0350
Sticker
R$ 0,0350
Base rate after the allowance, with no other applicable exemption. In groups, the unit is every delivered recipient. The canonical source states market, currency, category and effective date.
An estimate for Brazil recipients. Provide service deliveries, numbers, remaining allowance, category and month; compare the result with your rate card and account invoice.
Real numbers in the scenario: 1 · Service deliveries per number: 24000 · Remaining allowance per number: 1000
From 0 to 1,000; it is neither shared nor carried over.
AI, BSP, platform, infrastructure and operations are separate from Meta's rate card.
Rate per message: R$ 0,0350
Estimate result
Per conversation
R$0.40
Meta total
R$805.00
Attributed service cost: R$805.00
12 months with these assumptions and rates
R$9,660.00
Observed exempt deliveries: 1,000
Billable deliveries: 23,000
Delivered, billable utility: Not informed
Delivered, billable authentication: Not informed
Delivered marketing (standard rate card): Not informed
Declared external costs: Not informed
Partial total: costs or data are missing: R$805.00
Estimated complete total:
Not informed
Hybrid comparison
Declare the mix before comparing. Provide numbers, categories, tracks, topology and external costs before comparing total cost.
Estimated Meta saving: No saving is calculated for these assumptions
Estimated total saving: No saving is calculated for these assumptions
Not informed
Fictional educational example. 7,200 of 24,000 deliveries on the official track is only an illustration; adjust the mix, external costs and rules for each channel to your operation.
Only delivered outbound service in this scenario; exclude inbound, failures and other categories.
Allowance is per number and an FEP-mixed case depends on the balance and conditions for each delivery.
Mixed FEP without observed balance is not calculated as an exact cost.
Average cost uses only service attributed to conversations; campaigns do not enter the denominator.
A static scenario, not a yearly rate promise; the allowance restarts each month.
BRL and USD rates are independent rate cards. Without dated FX, MBA in USD cannot be added to messaging cost in BRL.
On October 1, utility can be charged even inside the CSW. It does not use the service allowance and keeps its own categories, tiers and conditions.
Order #1042 confirmed · delivery today
Order #1043 confirmed · delivery tomorrow
The 24-hour window and utility pricing are independent rules starting October 1.
The 1,000-delivery monthly allowance is for service; it does not offset utility or authentication.
Utility and authentication get volume tiers; service pays the full rate, no discount.
Do not generalize free delivery: FEP, inbound, service, utility and MBA follow different rules.
Meta Business Agent has a base price of US$ 2.00 per 1 million input and output tokens. It is a single charge: processing and delivery are included; cache is excluded.
Do not add a service fee to the same MBA delivery; cache tokens are not charged.
Your own AI has a separate provider cost and the Cloud API delivery still has its applicable category.
A global USD base price does not permit direct addition to BRL; any FX needs an explicit rate, date and direction.
The cost and availability of your own AI depend on the provider, your account and the chosen configuration. Cloud API delivery still follows its applicable category.
Inbound, service allowance and FEP are not synonyms. Read the origin, window, balance and category before calling a delivery free.
R$ 0,00
Inbound is not a billable service delivery. It does not determine the cost of a reply.
It requires an eligible origin and initial reply within the 24-hour CSW. The window of up to 7 days is independent of the 24-hour CSW.
Allowance per number
Service has 1,000 monthly deliveries per number; it is not portfolio-wide, does not apply to utility and does not roll over.
US$ 2 / 1M tokensMBA still has its own token charge even where a delivery follows another rule.
BRL migration applies to eligible customers with Brazil Sold-To in Billing Hub. Confirm eligibility and Messaging account currency before planning the cutoff.
Billing rules and a rate card depend on account currency; BRL and USD are not an automatic conversion.
Sold-To, payment method and Messaging accounts are operational preconditions. Check them in Billing Hub before planning the migration.
Deadline for eligible Messaging accounts. After it, the documentation provides for interruption for accounts in that scope that remain outside BRL.
Plan the payment method before billable messages and follow the schedule that applies to your Messaging account.
Username is optional and rollout is gradual. BSUID identifies a user-portfolio relationship, while identity, permissions, window and OTP cases still require explicit rules.
Meta documents reservation for eligible businesses, with gradual rollout and its own requirements. Review your account requirements before adding usernames to the support flow.
An operation must associate BSUID, consent and contact continuity; username does not make phone numbers obsolete.
Documentation supports reservation from this date, subject to eligibility and rollout; it does not confirm a worldwide availability date.
Templates and BSUID messages remain subject to permissions, window and known identity. One-tap, zero-tap and copy-code OTP require phone.
Gradual rollout in 2026
BSUID does not prove send eligibility: permissions, templates, window and known identity still determine what can be sent.
For Brazil recipients on October 1, 2026, standard marketing is R$ 0.3217 and service, utility and authentication have a BRL base rate of R$ 0.0350. USD is an independent rate card, not informal FX.
The Brazil BRL table is canonical for this scenario; USD accounts use their own USD rate card, not a converted figure.
Utility and authentication use marginal tiers by portfolio, market and category; service has no progressive discount.
Use the rate card for your account's market, currency and effective date. Meta's table excludes BSP, taxes, your own AI and infrastructure.
BRL tiers cannot be used to pretend there is a complete USD utility or authentication total.
Cloud API, official coexistence and a multichannel operation are not equivalent. Compare only after declaring tracks, numbers, categories, costs and accepted risk.
Cloud API with its own rules and approval
estimated Meta cost / mo
R$805.00
An official profile to assess by eligibility, category, cost and operational needs.
Unofficial channel, outside Meta coexistence
estimated Meta cost / mo
no seal · risk
Risk, consent, topology and total cost need assessment before any use.
An explicit mix of distinct tracks
estimated Meta cost / mo
Not informed
Provide numbers, categories, tracks, topology and external costs before comparing total cost.
The comparison starts with no defined mix and may yield zero savings or higher cost under the stated assumptions.
There is no default percentage: compare topology, volumes per track, external costs and each channel's limits in your company scenario.
Compare official Cloud API, official coexistence and a multichannel operation with distinct connectors. Each path needs its own numbers, identities, consent, reconciliation and costs.
Notification · OTP · status
Official Cloud API
Templates, quality, consent and receipts remain required; an API does not grant OBA or assure a delivery outcome.
Campaign & marketing
Official Cloud API
Marketing depends on category, quality, opt-out and pricing rules. Plan volume and budget against the applicable rate card.
Official coexistence
Business app + Cloud API, if eligible
The app and API have different billing, synchronization and limits; coexistence is not free app automation.
Multichannel operation
Distinct connectors
Define architecture, reconciliation and responsibilities before distributing messages across channels.
Conversation Routing has owner, standby and handoff in eligible accounts. How support is organized depends on the integrations, permissions and channels configured by the company.
The deal, no fine print
Organize payment method, delivery data, categories, allowance, eligibility and monitoring. Actions depend on an account's real state, not a generic configuration.
Separate inbound, failure, service, utility, authentication and marketing. For groups, count delivered recipients.
Track the remaining allowance per number. FEP and other exemptions have their own conditions and do not replace the allowance.
Categories, reclassification, quality, opt-out and limits remain before any send.
Billable messages need a payment method. Use your account's schedule and eligibility to organize the transition.
Validate Sold-To, currency, Messaging account and Embedded Signup v4; v2/v3 have an announced October 15 deprecation.
Use statuses, pricing analytics and invoices: API acceptance does not prove delivery or zero cost.
Lean flow
5 back-and-forth messages 5×
1 menu solves it 1×
Rules, rates and conditions to plan the operation and discuss cost with clarity.
Oct 1, 2026
new rules and rate cards effective
1,000
service deliveries/month/number
R$ 0.0350
BRL service above the allowance
US$ 2 / 1M
MBA input + output tokens
empty mix
hybrid has no saving before assumptions
This educational material helps organize the scenario; the account rate card and invoice remain the final reference.
Single demo: local educational calculator
Take this deck on your phone
Point your camera to open this page on your phone.
Official sources (Meta for Developers)
WhatsApp and Meta are trademarks of Meta Platforms, Inc. Conversa Labs has no relationship, affiliation or endorsement from Meta. Dates and rates reflect Meta's announcements (2026) and may change — always check the official source.
Updated 28 September 2026 · See Meta’s official rules and rate cards. Meta · WhatsApp Business Platform
Conversa Labs 
