Skip to content
Exclusive resource · Conversa Labs

Shield Kit
WhatsApp API 2026

Everything that changes — and what to do before October 1 — on a single page.

This brief gathers the October 1 rules, Brazil rates and allowance conditions to plan the operation. Share it with the team and consult official sources when closing the scenario.

  1. 01 The four dates that matter
  2. 02 Your math in 30 seconds
  3. 03 Reference rates (Brazil)
  4. 04 Hybrid comparison with assumptions
  5. 05 Six moves before October

01The four dates that matter

01 Jul 1, 2026

BRL for eligible customers

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.

02 Aug 1, 2026

The AI starts the meter

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.

03 Oct 1, 2026

Service per delivery

Service above its allowance is billed per delivery; utility and authentication have their own categories and tiers.

04 Jun 30, 2027

Deadline for eligible accounts

June 30, 2027 is the deadline for eligible Messaging accounts; on July 1 non-BRL accounts in that scope are interrupted.

02Your math in 30 seconds

Eligible deliveries − remaining allowance × rate

service deliveries: 24000 − observed allowance: 1000 = billable deliveries: 23000 × R$0.0350 = R$805.00

Count only service deliveries on the stated number, apply the available allowance and keep utility, authentication, marketing, FEP and MBA separate. The result is an estimate to compare with the invoice.

03Reference rates (Brazil)

Message type Per message
  • Service R$0.0350
  • Utility R$0.0350
  • Authentication R$0.0350
  • Marketing R$0.3217
jan abr jul out

04Hybrid comparison with assumptions

Hybrid strategy

Compare numbers, categories, channel, consent, external costs and risk for every track. Your company's defined topology shows whether there is total saving in the scenario.

  • Identify number, category, channel and consent per delivery

  • Separate Meta saving from total cost, including operations and infrastructure

  • Map connectors and routing separately, with the costs, limits and responsibilities of each channel

no total until the scenario is declared

05Six moves before October

  1. 01

    Measure deliveries, not attempts

    Separate inbound, failure, service, utility, authentication and marketing. For groups, count delivered recipients.

  2. 02

    Observe allowance and FEP

    Track the remaining allowance per number. FEP and other exemptions have their own conditions and do not replace the allowance.

  3. 03

    Classify templates and consent

    Categories, reclassification, quality, opt-out and limits remain before any send.

  4. 04

    Plan payment

    Billable messages need a payment method. Use your account's schedule and eligibility to organize the transition.

  5. 05

    Confirm BRL and onboarding

    Validate Sold-To, currency, Messaging account and Embedded Signup v4; v2/v3 have an announced October 15 deprecation.

  6. 06

    Reconcile after sending

    Use statuses, pricing analytics and invoices: API acceptance does not prove delivery or zero cost.

Want to plan your operation?

Bring volumes, categories, numbers and external costs to discuss your scenario. Integrations and configurations follow the contracted scope and each provider's requirements.

Read the full page

Point your camera to open the interactive presentation with a calculator.

Conversa Labs Conversa Labs © Conversa Labs · en

WhatsApp and Meta are trademarks of Meta Platforms, Inc. Conversa Labs has no relationship with Meta. Dates and rates reflect 2026 announcements and may change — check the official source.

Meta · WhatsApp Business Platform