WhatsApp Business API Migration Guide 2026

Something is breaking across thousands of Latin American businesses right now. Sales teams wake up to find their WhatsApp number blocked. Customer service inboxes go silent overnight. Marketing campaigns die mid-flight. The reason is always the same: the number was running on an unofficial WhatsApp integration — a QR-code bot, a grey-market API, a third-party tool that scraped the WhatsApp Web session — and Meta finally caught up with it.

This is not a one-off crackdown. Meta has been systematically tightening enforcement of its Terms of Service since 2024, and the pace accelerated dramatically in 2025–2026. Businesses that connected their CRM, chatbot, or sales automation through unofficial means are losing their numbers at scale, with no appeal process and no recovery path.

The solution exists and it is well-documented: the WhatsApp Business API (WABA) — Meta's official, fully supported channel for business messaging. This guide walks you through everything you need to know to migrate safely: what the API actually is, how it works, what it costs, and the exact steps to switch — whether you use Kommo CRM or a standalone setup.

By the end, you will have a concrete migration plan and a direct way to get expert help if you need it. Let's get into it.

Share: LinkedIn X WhatsApp

What Is Happening to Unofficial WhatsApp?

Meta has drawn a clear line: any WhatsApp integration that does not go through the official Business API is in violation of its Terms of Service. This includes:

• QR-code session hijackers — tools that scan the WhatsApp Web QR code and act as a bot on top of your personal session
• Reverse-engineered clients — software that mimics the WhatsApp mobile app's protocol without authorization
• Unauthorized SDKs — third-party libraries that wrap the WhatsApp protocol without a proper BSP agreement with Meta
• Grey-market API resellers — services that claim to offer "WhatsApp API" but route through unofficial channels

For years, many businesses operated in a grey zone. Enforcement was inconsistent, and thousands of companies built their entire communication stack on unofficial tools. That era is definitively over.

⚠️

If your number is banned, there is no reversal. Meta does not offer appeal processes for Terms of Service violations on WhatsApp numbers. The number cannot be used on any WhatsApp product — not the app, not the Business App, not the API. Migration protects you before the ban happens.

The enforcement mechanism has become increasingly automated. Meta's systems detect behavioral patterns associated with unofficial bots — message velocity, session anomalies, unusual API call signatures — and ban numbers without human review. A number that worked fine for two years can be gone in minutes.

What Is the WhatsApp Business API (WABA)?

Definition — Featured Snippet

The WhatsApp Business API (WABA) is the official, Meta-approved programmatic interface that allows businesses to send and receive WhatsApp messages at scale. It supports multiple human agents, CRM integrations, automated chatbots, message templates, rich media, and interactive elements — all within Meta's Terms of Service. Unlike the free WhatsApp Business app (limited to 5 devices), the WABA has no device cap and is designed for enterprise-grade volumes.

The WABA is accessed either directly through Meta's Cloud API (Meta-hosted infrastructure) or through a Business Solution Provider (BSP) — a Meta-certified partner that handles the infrastructure, compliance, and billing on your behalf.

Key capabilities you get with the official API that unofficial tools can never safely offer:

• Unlimited concurrent agent seats (your whole team, on one number)
• Pre-approved message templates for outbound campaigns
• Interactive messages with buttons and list menus
• Rich media: images, PDFs, videos, location, contacts
• Chatbot flows with handoff to human agents
• Native CRM integration (Kommo, HubSpot, Salesforce, etc.)
• Delivery and read receipts at scale
• Verified business display name and green checkmark (eligible accounts)
• Full LGPD/GDPR compliance path with opt-in management

Why Migrate Now?

Every week you wait is a week you run with an existential risk to your business communication. Here are the concrete data points:

• 2+ billion active WhatsApp users globally — the channel is irreplaceable for Latin American markets
• 98% open rate on WhatsApp messages, vs. 20–25% for email — there is no comparable alternative
• Enforcement is accelerating — Meta processed significantly more bans in 2025 than in all prior years combined, driven by AI-assisted detection
• No grandfather clause — there is no grace period for existing unofficial users. Violations are actioned on discovery, not on a schedule
• Number loss compounds — when a banned number was your primary customer contact point, rebuilding that database takes months
• Competitors are already on WABA — any competitor already on the official API operates with zero ban risk while you operate with existential risk

✅

The earlier you migrate, the more history you preserve. Conversation history, contact lists, and CRM data from unofficial tools can be exported and migrated before a ban forces the issue — but not after.

How WhatsApp Business API Works: Essential Rules

Understanding the WABA's operating model prevents surprises post-migration. These are the rules your entire communication strategy must be built around.

The 24-Hour Conversation Window

The WABA operates on a conversation-based billing model, not a message-based one. When a user sends any message to your business — whether it is "hi", a button tap, or a full inquiry — a 24-hour service window opens.

Within this window, you can exchange an unlimited number of free-form messages (text, media, documents) in either direction. The cost is charged per conversation (one opening event), not per message.

Outside the 24-hour window, you cannot send free-form messages. You can only initiate contact using a pre-approved message template. Sending a template opens a new conversation window and incurs the relevant per-conversation charge.

ℹ️

Free service conversations: Meta offers a certain number of free service conversations per month (conversations where the customer messages first). Check the current allocation at business.facebook.com, as this quota changes.

Message Types and Templates

All outbound messages outside the 24-hour window must use Message Templates — pre-approved text + variable placeholders submitted to Meta for review. Templates are categorized into four types:

• Marketing — promotional campaigns, product announcements, event invitations
• Utility — transactional messages, order updates, appointment reminders
• Authentication — OTPs and verification codes (special pricing)
• Service — reactive messages within the 24-hour window (free-form allowed)

Template approval typically takes a few minutes to 24 hours. Well-structured templates with clear value propositions are approved faster. Templates with excessive promotional language, unclear variables, or policy violations are rejected.

Sending Tiers and Limits

New WABA numbers start at Tier 1 and move up as they build a clean sending record:

Tier	Unique conversations / 24h	How to reach it
Tier 1	1,000	Default for new numbers
Tier 2	10,000	Send to 1,000 unique contacts in 7 days
Tier 3	100,000	Send to 10,000 unique contacts in 7 days
Tier 4	Unlimited	Send to 100,000 unique contacts in 7 days

Tier upgrades happen automatically when your volume qualifies — there is no manual application. However, account quality directly affects tier maintenance. If your block/report rate climbs above Meta's thresholds, your tier can be downgraded.

WhatsApp Business API Pricing: What You'll Pay

⚠️

Important disclaimer: The prices below are averages based on publicly available Meta data as of May 2026. Meta can change conversation pricing at any time, without prior notice, for any country and any category. Always verify current rates at business.facebook.com before building financial projections. These figures are provided for orientation only and must not be used as the basis for cost commitments to third parties.

WABA pricing depends on three variables: conversation category, destination country, and whether the conversation was initiated by the business or the customer. Here are approximate reference rates for Brazil:

Conversation Category	Initiated by	Approx. price (Brazil)
Marketing	Business	~USD 0.0625
Utility	Business	~USD 0.0080
Authentication	Business	~USD 0.0315
Service (reactive)	Customer	Free (within free tier)

⚠️ These are reference averages only. Meta updates per-conversation rates periodically and rates vary by destination country. The only authoritative source for current pricing is your BSP dashboard or Meta's official WhatsApp pricing page. Do not use these figures for budgeting without verification.

In addition to Meta's per-conversation fees, your BSP charges a platform fee — typically a monthly subscription (ranging from USD 50 to USD 500+/month depending on volume and features) plus sometimes a markup per conversation. Factor both cost layers into your business case.

For most Latin American SMBs doing customer service on WhatsApp, the monthly Meta cost is manageable — often USD 50–300/month for typical volumes. The ROI calculation becomes straightforward when you account for the alternative: losing the number entirely.

How to Migrate to the Official API: Step by Step

Migration is a single path regardless of your starting point. The main fork is whether you use Kommo CRM (which has a native integration) or a standalone setup.

If You Use Kommo CRM

Kommo has a certified WhatsApp Business API integration that connects your WABA directly to the pipeline. Here is the full flow:

1. Verify your Facebook Business Account

   Go to business.facebook.com → Settings → Business Verification. Submit company registration documents (CNPJ card, articles of incorporation, or utility bill). Meta approves most legitimate accounts within 1–3 business days.

2. Create a Meta Business App

   In Meta Developers (developers.facebook.com), create a new app and select "Business" as the app type. This is required to access the WhatsApp product panel.

3. Add the WhatsApp product and register your number

   Inside your Meta Business App, add the WhatsApp product. Then add a phone number — this is the number your customers will message. You'll receive a 6-digit code by call or SMS to verify it. Note: the moment you verify the number here, it disconnects from any existing WhatsApp app.

4. Connect Kommo to your WABA

   In Kommo, go to Settings → Integrations → WhatsApp. Click "Connect" and follow the embedded Meta flow (a Facebook Login popup). Select your WhatsApp Business Account and the phone number. Kommo will confirm the webhook endpoint automatically.

5. Create your first message templates

   In Kommo's WhatsApp settings (or directly in Meta's Business Manager), create your outbound templates. Submit for approval. While you wait (usually under an hour), configure your chatbot flows and agent routing rules.

6. Test and go live

   Send a test message from a personal number to your new WABA number. Confirm it appears in Kommo as a new lead/conversation. Assign it to an agent. Reply. Confirm delivery. Then brief your team and redirect all customer communications to the official number.

💡

Kommo Pro tip: Use Kommo's "Salesbot" to build a welcome flow for new conversations — capture the customer's name, purpose, and route to the right pipeline automatically. This replaces the manual triage your team was likely doing with the unofficial tool.

Without Kommo (Direct Meta Setup)

If you are not using Kommo, you have two options: use a BSP or connect directly to the Meta Cloud API.

Via a BSP (recommended for most businesses):

1. Choose a BSP

   Meta-certified BSPs for Latin America include 360dialog, Twilio, MessageBird, Gupshup, and locally-focused providers. Compare on pricing model, support quality, and features (inbox, chatbot builder, analytics).

2. Create your account and complete Facebook Business verification

   Most BSPs walk you through this with guided flows. Have your business registration documents ready.

3. Register your phone number through the BSP

   The BSP's onboarding wizard handles the Meta connection. You authorize them to manage your WABA on your behalf via a permission flow.

4. Set up your inbox and integrate your existing tools

   Most BSPs offer a built-in shared inbox, webhook-based integrations, or native connectors to popular helpdesks (Zendesk, Freshdesk, etc.).

5. Create templates, test, and go live

   Follow the same template creation and testing process described above. Monitor your quality score in the first 30 days.

Via Meta Cloud API directly (for technical teams):

If your team has engineering resources, you can bypass BSPs entirely by accessing the Meta Cloud API directly. You manage your own webhook server, handle retry logic, and build or integrate your own inbox. This is the lowest-cost path per conversation (no BSP markup) but requires meaningful DevOps investment.

⚡

Don't go dark: Plan your migration window to minimize downtime. The ideal sequence is: set up the new WABA completely → test it → redirect your published number only after full testing. If you must use the same number (e.g., it's already known by customers), schedule the cutover for a low-traffic window such as Friday evening.

---