ApivomApivom
Get Demo

Three WhatsApp models. One clear decision.

Choose between the WhatsApp Business app, an official Coexistence connection, and Cloud API. Mars supports the connected models through Meta’s official integration path.

WhatsApp connection guide
// At a glance

Compare the three operating models.

The Business app is a phone-first experience. Coexistence connects that same number to the platform. Cloud API is built for programmatic, team-led messaging.

FeatureBusiness app onlyMobile-firstCoexistenceApp + platformCloud APIAutomation-first
Experience
Business app continues on the same phoneIncludedIncludedNot included
Shared team inbox in MarsNot includedIncludedIncluded
Automation
Templates and programmatic sendingNot includedIncludedIncluded
Webhooks and workflow integrationNot includedIncludedIncluded
Scale
Campaigns and scheduled messagingNot includedIncludedIncluded
Continuity
Up to 180 days of approved history syncNot includedIncludedNot included
Limits
Group chat synchronizationNot includedNot includedNot included
Disappearing messages in connected 1:1 chatsIncludedNot includedNot included
Choice
Designed for transition without changing the phone experienceNot includedIncludedNot included
Designed for a platform-first operationNot includedNot includedIncluded
// Use case

Choose for the work, not for the buzzword.

Each model is valid. The right one depends on who answers customers, which tools must stay in place and how much automation the operation needs.

Stay with Business app when
  • One person handles the conversations on the phone.
  • You want the standard consumer-style app experience.
  • There is no need for a shared inbox, API events or campaign automation.

This is WhatsApp as a standalone mobile tool, not an Apivom integration.

// What Coexistence changes

Keep the number on the phone without assuming every phone feature transfers.

Coexistence keeps the same number usable in the official WhatsApp Business app while Meta also makes it available to Cloud API. It is useful when a business wants to keep its familiar phone workflow while adding a shared inbox and automation.

Some Business app features are deliberately unavailable in the connected Cloud API model: group-chat synchronization, disappearing messages, view-once media, live location and broadcast lists. A cloud-integrated inbox mirrors supported one-to-one chats, not every experience available inside the phone app.

// Common questions

The details that usually decide the setup.

Is Coexistence a fourth WhatsApp product?

No. Coexistence is the operating model that connects an existing WhatsApp Business app number to Cloud API. Embedded Signup is the official onboarding flow used to establish that connection.

Will Coexistence mirror every chat and feature from the phone?

No. Supported one-to-one chats are mirrored. Group chats are not synchronized, and disappearing messages, view-once media, live location and broadcast lists are not supported by the Cloud API side of Coexistence.

What is the best model for high-volume automation?

A Cloud API-first setup is the clearest model when the operation is team-based, campaign-heavy or workflow-driven. Coexistence is often the better transition when the business must continue using the same number in the Business app.

Who owns the Meta business assets?

The customer owns and administers the relevant Meta business portfolio, WhatsApp account and billing relationship. Apivom connects those assets as an official Technology Provider and operates the integration with the granted permissions.

// Next step

Tell us how WhatsApp works today.

We will map the current phone workflow, the required team inbox and the right official Meta connection model.