WhatsApp Coexistence: Use the Business App and API on One Number
WhatsApp coexistence can let an eligible business use its WhatsApp Business app and API-connected software on the same number. Imagine Kavya, a hypothetical Jaipur boutique owner. She answers customers in the app, but her assistant needs an inbox for showroom bookings. Before connecting it, Kavya wants to know whether both interfaces will work for her number, what her assistant will see, and who should send the next reply.
WhatsApp coexistence lets an eligible business keep using its WhatsApp Business app number while connecting that number to the WhatsApp Business Platform API through a supported onboarding flow. It can suit a business that wants app access alongside an API-connected team inbox, but eligibility and chat visibility need checking for the specific account and provider. Keeping the number does not mean every older conversation or attachment will appear in a new inbox. Before signup, record unfinished customer requests in your normal work tracker. Ask the provider to explain its onboarding steps and what each interface should display. After connection, test a new enquiry, replies from each interface, an older conversation and any attachments your staff rely on. Assign one person or team to own the next reply, even if several people can see the conversation. If the test leaves a gap in context or message visibility, keep the existing workflow monitored while you resolve it.
What is WhatsApp coexistence?
Meta describes an Embedded Signup option for onboarding WhatsApp Business app users and notes that the feature is sometimes called “Coexistence,” according to Meta for Developers: Onboard WhatsApp Business app users. In practical terms, an eligible business can keep its app workflow while connecting the number to software that uses the WhatsApp Business Platform API. The API is a software connection, not another mobile app for staff to install.
The useful question for Kavya is not just whether both interfaces open. It is whether each person can see the context needed to answer correctly—and who is responsible for doing so.
How can you use the WhatsApp Business app and API on the same number?
Start by asking a provider to check whether your existing Business app number qualifies for its supported coexistence onboarding. Describe the job the new software must do, such as assigning showroom-visit enquiries to a bookings desk. Then follow the instructions presented for your account rather than assuming that a general API migration guide applies.
- Define the workflow. Name the enquiries the new inbox should handle and who handles everything else.
- Identify account access. Confirm who controls the number and who can complete the signup steps.
- Ask about visibility. Have the provider explain what it expects the app and new inbox to show, including older chats and attachments.
- Record open requests. Put pending bookings and promised callbacks in your usual tracker without copying unnecessary customer details.
- Complete supported signup. Read the account-specific screens and stop if a requested change differs from what your provider explained.
- Run a small test. With a consenting contact, check an incoming message, replies from both interfaces and the customer’s view.
- Expand gradually. Resolve missing context or duplicate replies before adding more staff.
A connected account is only the start. Your team still needs a hand-off rule and someone responsible for checking messages during the change.
What are the WhatsApp coexistence requirements?
Your Business app number must be eligible for a supported onboarding flow, and the provider you choose must support that flow for your account. Meta’s onboarding documentation does not establish that every individual number qualifies. Check its current instructions and ask your provider to verify your setup before making changes; see Meta for Developers: Onboard WhatsApp Business app users.
For an Indian business, use this pre-signup checklist. These are planning questions, not a list of formal Meta requirements:
- Who controls the existing business number and can complete signup?
- Has the provider confirmed that its product supports coexistence for this account?
- Which staff will answer in the app, and which will use the new inbox?
- What should each interface display for older chats, new messages and attachments?
- What are the provider’s current fees and support steps if setup fails?
- Who will monitor customer enquiries throughout the test?
Get the answers in writing where possible. Distinguish a provider’s product requirements and fees from Meta’s onboarding rules.
What happens to chat history with WhatsApp coexistence?
Keeping the same number does not establish which previous chats an API-connected inbox will display. The app retaining a conversation and a new team inbox showing enough of it for a hand-off are different things. Ask your provider about both, including attachments and messages received after connection.
Run four checks before relying on the new inbox: open an older conversation tied to unfinished work; have a consenting contact send a fresh enquiry; reply once from each interface and confirm what the contact receives; and test an attachment your team normally uses. Note what each staff member can see. If the results differ from the provider’s explanation, investigate before making the new inbox the only place staff look.
Preserve the task, not an unnecessary copy of the whole chat. Kavya could record “shipping quote still needed” in an order tracker. A clinic administrator could note that an appointment change needs a callback without putting sensitive conversation details in a general task list.
Should an Indian business choose the app, coexistence or an API-only setup?
Choose the arrangement that gives staff a dependable place to work. A second inbox helps only if the people using it can identify their enquiries and the next reply owner.
| Approach | Possible fit | Question to resolve |
|---|---|---|
| Business app only | One owner handles most enquiries | How are open requests tracked when the owner is away? |
| Coexistence | Staff need API tools alongside app access | Is this number eligible, and what can each interface show? |
| API-only setup | Staff plan to work in provider software | How will onboarding and hand-offs work? |
| Separate numbers | Distinct contact channels suit the business | How will customers know which number to use? |
In Kavya’s hypothetical boutique, coexistence is worth testing if her assistant can identify and own showroom-visit requests without losing essential context. If the test fails, improving the current request tracker may be more useful than adding another inbox. This is a decision example, not a reported customer result.
How should you budget for app and API messages?
Separate messages sent through the mobile app from activity sent through the API. The WhatsApp Business mobile app is not billed per message under WhatsApp Business Platform pricing; the Platform pricing change applies to the API. Since 1 July 2025 Meta charges per delivered template message (marketing, utility, authentication) instead of per 24-hour conversation, according to Meta for Developers: Pricing on the WhatsApp Business Platform.
From 1 October 2026 Meta charges for service messages (free-form replies inside the 24-hour customer service window) per message, at the same rate as utility messages in that market, with no volume tiers. Each business phone number gets 1,000 free delivered service messages per calendar month; the allowance resets monthly, does not roll over and is per number, not shared across numbers. From 1 October 2026 utility templates sent inside an open 24-hour customer service window are charged; before that they were free inside the window. See Meta for Developers: Upcoming pricing updates for service and utility messages. Do not assume that every reply in a combined app-and-API workflow has the same billing treatment.
For a budget, list the API message types your proposed workflow would send, then check Meta’s current rate card and your provider’s current fees and invoice terms. Keep mobile-app activity in a separate row rather than assigning it an API message charge.
How do you prevent duplicate replies during rollout?
Give every conversation one reply owner, even when more than one person can see it. For Kavya’s example, the rule might be: “The counter team owns existing-order questions in the app. The bookings desk owns showroom visits assigned in the shared inbox. Check the open-request tracker before replying to anything visible in both places.” Adapt the rule to what your tests show.
Test a changed request, not only a first enquiry. If a customer moves a showroom visit after Kavya replies in the app, can the assistant see the latest relevant message and avoid sending a second confirmation? If not, decide who finishes the conversation and record the hand-off. Keep a short test log showing the scenario, what each interface displayed, what the customer received and who follows up.
What should your team check before using the new inbox?
- Visibility: Can each role find the new enquiries it must answer?
- Context: Can staff recognise unfinished work without assuming every old chat is present?
- Ownership: Is one person or team responsible for the next reply?
- Exceptions: Who checks the app and contacts the provider if an expected message is missing?
- Costs: Which proposed actions use API messaging, and where will staff verify current charges?
If booking enquiries are the reason for adding an inbox, explore Intellibook AI’s WhatsApp AI receptionist for booking enquiries after checking eligibility and the supported connection. Evaluate it against a specific hand-off: who receives an enquiry needing staff attention, and where will that person find its context?
Frequently asked questions about WhatsApp coexistence
Can I use the WhatsApp Business app and API on the same number?
Yes, if your existing Business app number is eligible for a supported coexistence setup. The arrangement can retain app access while connecting that number to API-based software. Ask your provider to verify your account, explain its onboarding flow and demonstrate the message behaviour your team needs before changing its routine.
What happens to WhatsApp coexistence chat history?
Do not assume every past chat or attachment will appear in a new API-connected inbox. Ask what each interface displays after connection. Record important unfinished work, then test an older conversation, a new enquiry, replies from both interfaces and an attachment your staff commonly use before relying on the inbox for hand-offs.
What are the WhatsApp coexistence requirements?
Your number and account need to qualify for a provider-supported onboarding flow. Confirm who can complete the account steps, which features the provider supports and what each interface should show. Also check the provider’s current fees and support arrangements. Plan a small message test and assign reply ownership before a wider rollout.
Will messages sent in the WhatsApp Business app incur API charges?
Messages sent solely through the Business mobile app should not be counted as API messages in a Platform cost estimate. Once you connect API-based tools, ask your provider which actions use the Platform and how its own fees work. Verify current Meta pricing and invoice terms before estimating the combined workflow’s cost.
Test the booking hand-off before adding another inbox
Confirm your number’s eligibility, check what staff can see in each interface and name the owner of the next reply. If booking enquiries still need a clearer hand-off, assess whether Intellibook AI fits the workflow you tested.
