Move from a chatbot platform to your own AI on WhatsApp
Moving off a bot platform is four jobs: export what the platform holds (conversations, contacts with their opt-in, flows and the bot's knowledge), move the number, rebuild the flows as automations with your own AI model on your own API key, and recreate your approved templates. A number that lived only on the API can return to the WhatsApp Business app and keep its API access through Meta's Coexistence feature.
easyCoexistence connects the number you keep in the WhatsApp Business app to Meta's Cloud API through Coexistence in about two minutes, then runs automations and AI replies on your own Anthropic, OpenAI or OpenRouter key, with no AI markup and no run cap.
How long Meta says to wait after disconnecting a business platform in the WhatsApp Business app before a new signup.
A number cannot be deleted from a WhatsApp Business Account if it sent paid messages in the last 30 days.
Where a portfolio admin deletes a business phone number; Meta offers no API call for it.
Display name, quality rating and messaging limit in Meta's migration of an API-only number between providers.
Most steps per automation line, 60 in all, branches nested up to 4 deep; further logic moves to a Call my webhook step.
What should you export before leaving a bot platform?
Everything the platform stores that you cannot rebuild from memory, while the account is still open. Conversations held by an API-only setup never reached a phone, so the platform's copy may be the only one. Ask for exports before you give notice:
- Conversation history, as CSV or JSON if the platform offers it, for your records or your own agent's memory.
- Contacts, with how and when each one opted in. Template sends to people who never opted in draw blocks.
- Every flow: triggers, keywords, buttons and branches, as an export or screenshots.
- The bot's knowledge or FAQ text, which becomes your AI's instructions.
- Your templates: name, language, category, body text and example values for each variable.
- Webhook and integration URLs, and any saved quick replies your team relies on.
How does the number move to Coexistence?
It depends on whether someone still answers the number from the WhatsApp Business app today. Check that first, because the two routes do not mix. Meta's own phone number migration, which keeps an API-only number's display name, quality rating and messaging limit, moves it between providers' accounts but leaves it on the API without the app, so it is not the route to Coexistence:
| The app is still on the phone | The number lives only on the API | |
|---|---|---|
| Free the number | In the app: Settings > Account > Business Platform, select the platform, Disconnect | The platform's account has to release it: a portfolio admin deletes it in WhatsApp Manager |
| Timing | Wait 15 minutes, as Meta's signup errors ask | Not possible within 30 days of the last paid message, so plan the date |
| Then | Connect the existing app account through Coexistence | Register the number in the WhatsApp Business app on a phone, then connect it |
| Chats | Stay in the app throughout | Start fresh in the app; the platform's history is in your export |
How do bot flows map to automations?
Most flows have a direct counterpart, and the rest move into your AI's instructions or your own system. An automation is a trigger and a flow of up to 30 steps per line, 60 in all, with branches (Split into paths by rules, AI picks the path by meaning) nested up to 4 deep and questions that wait for the answer, and one automation answers a given message, keyword ones first, then first message, after hours and the catch-all. Map each flow before building, so two automations do not compete for the same words:
How does the bot's AI become your own AI?
By bringing your own key and model instead of renting the platform's. On the Automations page, press "AI keys", pick Anthropic, OpenAI or OpenRouter, paste the key and press "Test and save": it is checked without spending tokens, and the model list loads. In a "Reply with AI" step, choose the model and paste the bot's knowledge into "Instructions", tightened into facts and questions; for more than fits there, an Agent answers step takes the knowledge as uploaded files (PDF, Office, pictures), public links or pasted text, and can call your own APIs. Your provider bills the tokens to you directly, with nothing added in between. Set "Earlier messages it reads" and "AI replies per chat per hour, at most" under Advanced before turning it on.
What happens to your templates?
Templates belong to the WhatsApp Business Account they were created in, so they follow the number only when the account stays the same. If the number lands on a new account in your own Business Portfolio, recreate them from your export. ChatGPT or Claude can do it through the MCP connector: create_template submits each one to Meta's review with example values for {{1}} and {{2}}, and get_template_status shows APPROVED, PENDING or REJECTED; approval usually takes minutes, up to about 24 hours. On a Coexistence number, templates are sent through the API only, never from the app. For automations, put coupon codes and other variables in the body: templates with copy-code or Flow buttons, named variables or a header picture cannot be sent by an automation yet.
What changes for your team and your customers?
Customers notice nothing: same number, same name, nothing to install. Your team gets the WhatsApp Business app back as the place where people answer, on the phone and its linked devices, with the AI working on the same chats and stepping back when a person replies. There is a Conversations screen in the dashboard, with an answer box, tags and contact fields, but people keep answering from the app: a reply from either place pauses the bot on that chat. Four app features turn off on a Coexistence number: disappearing messages, view once, live location in one-to-one chats, and broadcast lists, which become read-only. Group chats stay in the app only and never reach the API.
In what order should you switch?
In an order that leaves no customer unanswered for long. Rebuild and test before the number moves where you can, using the exports, and keep the new automations switched Off until the number is connected. The connection itself takes about two minutes once Meta's wait is over. For a number already in the app, the phone keeps receiving messages during the switch, so someone can answer by hand while the automations are being turned on.
How to set it up
- Export from the platformDownload conversations, contacts with opt-in dates, flows, the bot's knowledge and your templates before cancelling.
- Free the numberDisconnect it in the app under Settings > Account > Business Platform, or have a portfolio admin delete it from the old account in WhatsApp Manager.
- Connect through CoexistenceWait 15 minutes after disconnecting, then connect the WhatsApp Business app account; the app stays on the phone.
- Rebuild the flowsCreate the automations yourself in the editor, or ask your AI to with create_automation, with the switch Off.
- Recreate templates and go liveResubmit templates with create_template, run tests, then switch the automations On and read the first runs.
Common mistakes
- Cancelling the platform before exporting. An API-only number's conversations never reached a phone, and opt-in records you cannot show make every later template send a risk.
- Starting the new signup while the platform still holds the number. Meta refuses it with errors such as 2655093 or 3441049; disconnect first and wait 15 minutes.
- Rebuilding a forty-branch button tree as forty automations. One automation answers a given message and holds its own branches, so use Ask a question with Split into paths and Go back to a step, an agent, or your own system behind Call my webhook.
- Leaving the WhatsApp Business app's own away message on beside a new After hours automation. Both answer, and the customer gets two messages.
Your AI can rebuild the flows and recreate the templates through the MCP connector. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Is there a gap with no automated replies during the move?
A short one. From the moment the platform lets go until the new automations are switched On, nothing answers automatically. For a number already in the app, the phone keeps receiving messages throughout, so a person can cover that hour.
Can I import the chat history I exported from the platform?
Keep the export in your own system, where your own agent can use it as memory, for example through a Call my webhook step. Automations read only the chats they saw themselves, kept for the days you choose (30, 90 or 365), and there is no import tool.
Do my contacts need to opt in again?
Meta's opt-in rules apply to your business, not to the software you send with. Keep the opt-in records you exported, and send templates only to people who agreed to hear from you.
Can my AI rebuild the flows for me?
Yes. Give ChatGPT or Claude the exported flow and ask it to recreate it: it calls create_automation with enabled set to false, then test_automation with sample messages, and you switch it On when the answers look right.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on