WhatsApp Coexistence vs Cloud API: Which Connection to Choose

WhatsApp coexistence vs Cloud API is the first decision for any business moving its WhatsApp to the WhatsApp Business API. Coexistence keeps the number in the app and on the API at the same time; the Cloud API with a dedicated number takes the number out of the app in exchange for scale.

Both run on the same Meta technology, but they change the role of the phone, the sending speed, and the history. This guide compares the three connections and covers decision scenarios, the migration path, and the questions to ask a partner.

Key Takeaways

• Coexistence is the same number in the WhatsApp Business app and on the Cloud API; the Cloud API with a dedicated number uses a number that lives only on the API.
• The phone, sending speed (a fixed 20 mps versus 80 to 1,000 mps), app features, and history are the differences that decide the choice.
• The decision starts with the operation: who replies, how much the business sends, and how much the number customers already know is worth.

WhatsApp Coexistence vs Cloud API: The Difference in Brief

The difference between coexistence and the Cloud API is where the number lives. With coexistence, it stays in the WhatsApp Business app and also starts answering through the API; with a dedicated Cloud API number, it works only through the API, inside a platform.

What Coexistence Is

Meta calls the feature onboarding WhatsApp Business app users, also known as coexistence. The business connects the number it already uses in the app to the Cloud API and starts sending high-volume messages through a partner’s platform.

The app keeps working for one-to-one conversations, and WhatsApp keeps the history in sync on both sides. The complete guide to WhatsApp coexistence covers the requirements, activation, and what changes on the phone.

What the Cloud API With a Dedicated Number Is

The WhatsApp Cloud API is the version of the official API hosted by Meta. In the “pure” model, the number is registered only on the API: it no longer opens in the WhatsApp Business app, and all customer service happens in a platform with an inbox.

This model is the default for businesses that serve customers with a team, integrate a CRM, or send high volumes. In exchange for leaving the phone behind, the business gets the full speed limits and every API feature.

Where the WhatsApp Business App Alone Fits

The WhatsApp Business app without an API connection stays free and simple. It works well for businesses that reply from their own phone, with greeting messages, away messages, quick replies, and labels, without integrations or automation beyond the built-in tools.

The limit shows up when volume grows. The app does not send templates, does not talk to external systems, and cannot host an AI agent that takes actions, all features that depend on the API.

Comparison Table: App, Coexistence, and Cloud API

The table below summarizes the comparison based on the Meta documentation reviewed in October 2026. Each row is a criterion that often decides the choice between the app, coexistence, and the Cloud API with a dedicated number.

Phone, Agents, and Automation

The first block of the table answers the most practical question: who will reply, and from where. With coexistence, the owner stays on the phone while the team and the automation work in the platform; with a dedicated API number, everyone works in the platform.

For an operation with several salespeople, both API paths solve the problem of a shared phone. The guide to WhatsApp with multiple agents shows how to route conversations, hand off to humans, and measure each agent.

Throughput, App Features, and History

Throughput is the maximum speed in messages per second (mps), counting sent and received messages. According to Meta’s throughput documentation, reviewed in October 2026, a coexistence number has a fixed 20 mps, versus 80 mps by default on a dedicated API number.

On a dedicated number, an eligible number scales automatically to 1,000 mps, and there are the Groups API and the Calling API, which require the number to be out of the app. With coexistence, groups and calls stay on the device only, without API support, as the guide to WhatsApp coexistence and groups explains.

Costs for Each Connection: App, Coexistence, and API

The cost of a connection has two parts: what Meta charges for messages and what the partner’s platform charges for its service. The first part follows Meta’s public rules; the second varies by vendor and should be put in writing.

Free App Messages and Per-Message API Pricing

With coexistence, messages sent from the WhatsApp Business app remain free, and messages sent through the API follow Cloud API pricing. Meta’s official guide to API solutions for app users adds that groups, calls, and Status in the app also remain free.

Since July 1, 2025, Cloud API pricing is per delivered template message, with a rate that depends on the category (marketing, utility, or authentication) and the recipient’s country. The article on WhatsApp API pricing brings together the rates and simulations.

What Changed in October 2026

From October 1, 2026, Meta charges service messages and utility messages sent inside the 24-hour window, with 1,000 free service messages delivered per phone number per month. This applies to what goes out through the API. In Brazil, for example, Meta’s rate card lists R$ 0.035 per service, utility, or authentication message and R$ 0.3217 per marketing message.

That is why coexistence can lower the bill when a large share of human replies goes out from the app. The 24-hour window and free entry points of up to 7 days, such as Click-to-WhatsApp ads, still apply to the API side. The guide to WhatsApp coexistence pricing walks through the math.

How to Estimate the Bill Before Choosing

Before deciding, project a typical month of messages. The bill changes a lot depending on how much goes out through the API and how much stays in the app, and that split only exists with coexistence.

1. Count the marketing, utility, and authentication messages that will be sent as templates.
2. Estimate the service replies that will go out through the API, written by humans or by AI.
3. Set aside what the owner will keep answering from the app, with no Meta charge.
4. Add the platform’s monthly fee and compare the total between the two models.

Risk, Quality, and Messaging Limits

Both connections are official and follow the same Meta policies, which keeps the risk of a banned WhatsApp number lower than with unofficial tools. The difference lies in which messages fall under API enforcement and in what can turn the connection off.

Limits and Quality Apply to What Goes Out Through the API

According to Meta’s official PDF guide, one-to-one messages sent from the app do not count toward messaging limits or Cloud API integrity. Only what goes out through the API is subject to API enforcement, as on any dedicated number.

Messaging limits start at 250 unique users in 24 hours and rise to 2,000, 10,000, 100,000, and unlimited. Poorly targeted campaigns can lower the WhatsApp quality rating on both API connections.

14-Day Inactivity and Reconnection

Coexistence carries a risk that a dedicated API number does not: dependence on the phone. The account update webhook records the partner disconnection when the primary device stays inactive for about 14 days, and the API stops working.

When the business changes phones or reinstalls the app, the connection drops and can come back on its own within a few minutes. During reconnection, API messages are suspended and history from that gap is not synced, which customer service needs to plan for.

Coexistence vs Cloud API: New Number or Existing Number

When it comes to the number, the rule is simple: coexistence exists for businesses that cannot give up their current number or the phone, while a dedicated Cloud API number fits a new number or a number that can leave the app.

When the Current Number Matters Most

An established number is very valuable when it is on business cards, storefronts, Google, old ads, and in customers’ contacts. Changing it means telling everyone and losing conversations that would arrive through the saved contact, a cost that coexistence avoids.

History matters too. If the business allows it, up to 6 months of one-to-one conversations are synced to the platform, and the team sees each customer’s context from the first day on the API.

When a Dedicated Number Is Better

A number that lives only on the API makes sense for WhatsApp bulk messaging with templates, for large service teams, or for separate channels, such as one number for billing and another for sales. It is also the path for businesses that need the Calling API or the Groups API.

Businesses that use an unofficial WhatsApp API today often gain by starting over with a clean number on the official API. In that case, losing the app history matters less than the safety of a Meta-approved connection. The guide on moving from an unofficial API to coexistence covers the option of keeping the number.

WhatsApp Business App or API: Scenarios to Decide

Choosing between the WhatsApp Business app and the API gets easier when the business fits one of the three scenarios below. They are not Meta rules but a practical reading of each connection’s official limits.

Choose Coexistence When…

• The owner or lead salesperson replies from the phone and does not want to leave the app.
• The number has been known for years, and changing it would cost customers.
• The business wants to add automation, templates, and AI without stopping human service.
• Sending volume fits within 20 mps, and the operation uses groups or calls in the app.

Choose the Cloud API With a Dedicated Number When…

• The whole team works in the platform, and nobody depends on the phone.
• There are frequent template campaigns or sends that need more than 20 mps.
• The business needs groups or calls through the API, with its own integrations.
• There is no acceptable risk of the connection dropping because a device went inactive.

Stay on the App Only When…

For businesses that receive few messages a day and answer everything in person, the free app still does the job. Its built-in greeting and away messages cover the basics with no API cost.

The signal to change is clear: customers waiting for answers, a phone the team fights over, or the wish to use AI. At that point, coexistence is the smoothest step beyond the app without changing numbers.

How to Migrate From One Connection to Another

Migration between connections is not symmetrical. Going from the app to coexistence keeps almost everything; leaving coexistence or switching partners requires disconnecting in the app itself and redoing the flow, with attention to deadlines.

From the App to Coexistence

The business needs the WhatsApp Business app on version 2.24.17 or later and a partner that offers the flow. It enters the number, confirms the connection in the app (with a code or a QR code, depending on the flow version), and decides whether to share its history.

After the connection, the partner has 24 hours to sync contacts and conversations. If Meta rejects the number for lack of use, the official errors list says to use the app more before trying again, with no published minimum period.

Switching Partners or Moving to a Dedicated API Number

There is no direct migration from one coexistence partner to another. The business disconnects in Settings > Account > Business Platform, waits 15 minutes, and redoes the flow with the new partner; the Deregister API does not work for these numbers.

To move to a dedicated API number, the simplest path is a new number, because the app history does not migrate. The article on WhatsApp coexistence errors explains the messages that appear when the number is already on another platform.

From a Dedicated API Number to Coexistence

The reverse path also exists, but it is not immediate. A number registered on the Cloud API has to be deregistered first, and coexistence requires it to be registered in the WhatsApp Business app, with enough activity to be eligible.

In practice, the business gives up 80 mps or more and moves to a fixed 20 mps. This move back only pays off when the phone has become central to the routine again, as in businesses where the owner takes over customer service.

Questions to Ask a Partner Before Signing Up

Coexistence and the Cloud API only reach a business through a Meta partner, a Solution Partner or Tech Provider, via Embedded Signup. That is why connection quality depends on Meta and on whoever implements it. ConverZAP is a Meta-verified Tech Provider and offers both connections inside its app: a new number, or the number already used in the WhatsApp Business app, through coexistence.

Technical Questions

• Is the coexistence flow active in Embedded Signup, and does it already use version 4, given that Meta discontinues version 2 on October 15, 2026?
• Does the platform receive the messages sent from the app, so the team and the AI can see what the owner replied?
• How is the business alerted if the connection drops because of inactivity or a device change?
• Is history synced within the 24-hour deadline, and how many months does it cover?

Vague answers about events, alerts, and sync deserve caution. A connection without monitoring can drop because of inactivity and go unnoticed for days, with customers writing to a number the platform no longer receives.

Questions About Costs, Support, and Exit

• What is Meta’s charge and what is the platform’s fee, and who pays Meta?
• Does the account use an old partner’s credit line? Meta warns this can cause an error during a switch.
• What support is available when the connection drops, and how fast does it respond?
• How does exit work: can the business disconnect on its own and take its data?

Ask for these answers in writing, together with the proposal. The contract should state clearly who owns the Meta account and the number, so that switching vendors does not turn into a commercial lock-in.

Coexistence and the Official API: Where AI Agents Fit

With coexistence on the official API, the AI agent works on the Cloud API side: it reads the message, checks the knowledge base, and replies. On a dedicated API number, the role is the same, but without a phone replying in parallel. The guide on AI agents explains how they work.

AI Agent, Inbox, and a Human on the Same Number

With coexistence, every message the business sends from the app generates an echo event for the platform. That lets the agent notice that a human has taken over the conversation and stop replying, which avoids two answers to the same customer. At ConverZAP, messages you send from the phone show up in the inbox as “Sent from phone”, and the AI agent pauses so it doesn’t reply over you.

An AI agent integrated with a CRM checks calendars, orders, and records before replying. AI replies sent through the API without a template count as service messages, and the guide to human and AI customer service shows how to split the work.

How to Start on the Official API With ConverZAP

ConverZAP works with the official WhatsApp API: AI agents that take actions, a team inbox for multiple agents, and campaigns with approved message templates, opt-in, and unsubscribe. In the ConverZAP app, the business chooses between connecting a new number or the number it already uses in the WhatsApp Business app, through coexistence; the right choice depends on each operation.

The right connection is the one that fits the routine of the people who reply, not the one that looks most complete on paper. The coexistence setup guide shows the steps, and you can try it free with your own number: the 7-day trial already includes the connection.

WhatsApp Coexistence vs Cloud API: Frequently Asked Questions