文件

甚麼是 EasyCoexistence？

EasyCoexistence 透過 Meta 的官方 Coexistence 功能，將您一直使用的商業號碼連接至 WhatsApp Business Platform（Cloud API），然後全天候監察連接，避免連接在沒有提示的情況下中斷。

• 您手機上的應用程式會完全如常運作。Coexistence 會在旁加入 API，不會取代任何功能。
• 無需遷移，也不會遺失聊天記錄：您的歷史記錄會保留在手機上。
• 您可以在同一個帳戶連接任意數量的號碼。
• 您的對話不會經過我們的伺服器。Meta 可以將收到的訊息直接路由至您自己的系統。

連接號碼

1. 建立您的帳戶，然後開啟控制台。
2. 按一下「連接號碼」。Meta 的視窗會開啟；使用管理您業務的 Facebook 帳戶登入。
3. 輸入您的商業號碼，然後使用手機上的 WhatsApp Business 應用程式掃描 QR code。
4. 完成，通常少於 2 分鐘。號碼會在您的控制台顯示，並附有即時健康狀況。

您的號碼符合資格嗎？請先閱讀

Meta 會在允許使用 Coexistence 前執行幾項規則。大部分連接失敗都由以下其中一項引起：

• 號碼必須使用 WhatsApp Business 應用程式 2.24.17 或更新版本。個人 WhatsApp 帳戶無法連接。
• 號碼需要有真實且近期的雙向對話活動。全新或長期沒有使用的號碼會被拒絕。
• 號碼不能連接至其他 API 平台或供應商（群發工具、CRM、automation 工具）。請先在該處中斷連接，然後再試。
• 應用程式中的兩步驟驗證或待處理的裝置配對，也可能阻止啟用。

如果 Meta 顯示號碼「已註冊至現有 WhatsApp 帳戶」，請不要刪除手機上的 WhatsApp 帳戶；號碼必須繼續在應用程式中保持啟用。請改為在其他平台解除號碼連接。

應用程式會有甚麼變化（取捨）

啟用 Coexistence 會停用應用程式的幾項功能，全部只涉及個人聊天（1:1）。連接前請先了解：

• 1:1 聊天中的消失訊息會被關閉。
• 1:1 聊天中的檢視一次訊息會被停用。
• 1:1 聊天中的即時位置分享會被停用。
• 廣播清單：您無法建立新的清單，現有清單會變成唯讀。
• 啟用時，所有已連接的裝置都會中斷連接，需要重新連接。Windows 版 WhatsApp 和 WearOS 將不再獲支援。
• 群組、通話、目錄和動態消息會繼續在應用程式中運作，但不會在 API 端顯示。
• 號碼會受到每秒 20 則訊息的合併 API 吞吐量上限限制。日常聊天不受影響。

透過您的 AI 使用（每個帳戶一個連接器）

您的整個帳戶會獲得一個連接器 URL。它適用於您現在及將來連接的每個號碼：您的 AI 會看見所有號碼，並為每項工作選擇合適的號碼。

• Claude（網頁版或桌面版）：設定 → 連接器 → 新增自訂連接器，然後貼上 URL。
• ChatGPT：設定 → 連接器 → 進階，啟用開發人員模式，然後新增 URL。
• Claude Code（終端機）：claude mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp
• 系統提示時，使用您的 EasyCoexistence 電郵地址和密碼登入，並授權存取權限。

之後只需提出要求：「從我的號碼發送訊息」、「建立推廣訊息範本」、「我的號碼健康嗎？」、「將收到的訊息路由至我的系統」。

您的 AI 可以做甚麼（工具）

• list_numbers：列出您的所有號碼、狀態、質素和級別。
• get_number_health：顯示 Meta 的即時快照及近期事件時間軸。
• send_message：在 24 小時服務時段內發送自由格式回覆。
• create_template、get_template_status、list_templates：建立及追蹤訊息範本。
• send_template：使用已獲批的範本開始對話。
• get_api_credentials：取得連接您自己系統所需的 ID、端點和存取權杖。
• set_webhook_destination：將收到的訊息直接由 Meta 路由至您的 Webhook。
• get_connect_link：了解如何啟用另一個號碼。
• get_docs：本文件，讓您的 AI 可以回答有關產品的問題。

發送規則（由 Meta 設定，並非由我們設定）

• 回覆可以使用自由格式：任何在過去 24 小時內向您發送訊息的人，都可以直接獲得回覆。
• 開始對話需要使用預先獲批的範本。
• 在 Coexistence 中，範本只能透過 API 發送；手機應用程式無法發送範本。
• 推廣訊息由 Meta 向您自己的 WhatsApp Business 帳戶付款方式收費。我們絕不在訊息費用上加價。
• Meta 會限制 Coexistence 號碼的 API 吞吐量；手機上的日常訊息不受影響。

連接您自己的系統

控制台中每個號碼的頁面都會顯示其 API 基本 URL、帳戶 ID、電話號碼 ID 和存取權杖：n8n、CRM 或自訂程式碼透過官方 Cloud API 發送訊息所需的一切資料。如要接收訊息，請要求您的 AI 將收到的訊息路由至您的 Webhook（set_webhook_destination）：Meta 會將訊息直接傳送至您的端點，絕不會經過我們的伺服器。

監察及 14 天規則

我們透過 Meta Webhook 和定期檢查，全天候監察每個已連接的號碼（連接狀態、質素評級和訊息級別）。如果手機上的商業應用程式大約 14 天沒有開啟，Meta 可能會在沒有提示的情況下移除 Coexistence 連接。一旦出現任何問題，您的控制台會顯示問題及原因。簡單來說：繼續如常使用應用程式。

EasyCoexistence 並不是甚麼

• 不是收件匣或聊天機械人。對話會繼續在您的應用程式、AI 或您自己的系統中進行；我們不會增加另一個需要日常使用的控制面板。
• 不是群發訊息工具。Meta 的規則仍然適用：在 24 小時時段內回覆，使用範本開始對話。
• 不是 Meta 的產品。我們是獨立的 Tech Provider，使用平台的官方 Coexistence 功能。
• 不是您訊息的中間人。我們絕不會讀取或儲存您對話的內容。

即使 EasyCoexistence 明天消失，您的號碼也不會受到影響：應用程式會繼續運作，歷史記錄會保留在手機上，而 API 連接可以隨時解除。一座橋樑，而不是牢籠。

常見問題

指南

其他內容都會引用的詳細說明。

• WhatsApp MCP server for Claude, ChatGPT and CursorConnect Claude, ChatGPT or Cursor to a real WhatsApp number over MCP. Official Cloud API, eleven tools, no linked-device workaround and no ban risk.
• WhatsApp Coexistence: the app and the API on one numberCoexistence runs the WhatsApp Business app and the Cloud API on the same number at once. What it changes, what it does not, and how a number gets connected.
• Unofficial WhatsApp APIs: what actually gets numbers bannedUnofficial WhatsApp gateways sign in as a linked device, which breaks Meta's terms. What that costs, and what the official route looks like instead.
• WhatsApp Cloud API or Coexistence: which one a number needsBoth are Meta's. One takes the number onto the API alone, the other runs the API beside the WhatsApp Business app. Which to pick, and what each costs you.
• WhatsApp webhooks: routing messages straight to your serverHow WhatsApp webhooks work, what Meta sends, and how to route incoming messages directly to your own endpoint instead of through a provider's platform.
• WhatsApp Coexistence for agencies and consultanciesConnect client WhatsApp numbers without migrating them or retraining their staff. One account, many numbers, each in the client's own Business Portfolio.
• What being a Meta Tech Provider means, and why it mattersA Tech Provider connects other businesses' WhatsApp numbers through its own Meta app. What the status requires, and what it changes for the client.
• What WhatsApp Coexistence costs, provider by providerWhat each provider charges to hold WhatsApp numbers, at one, ten and fifty numbers. Figures from their own pricing pages, September 2026.
• WhatsApp Coexistence glossaryPlain definitions for the vocabulary around WhatsApp Coexistence: WABA, Business Portfolio, phone number id, templates, quality rating, Tech Provider and MCP.
• Can you use the WhatsApp Business app and the API on the same number?Yes. Coexistence is Meta's official feature for running the WhatsApp Business app and the Cloud API on one number at once. How it works and what changes.
• How to connect WhatsApp to an API without losing your chatsConnecting a WhatsApp Business number to the Cloud API without losing conversations. Why chats stay on the phone and what actually syncs.
• The cheapest way to get the WhatsApp Business APIWhat the WhatsApp Business API actually costs: Meta's conversation fees versus provider fees, and how to pay the least.

整合

從您已經使用的工具連接至已連接的號碼。

• Connect WhatsApp to n8n on the official Cloud APIRoute WhatsApp messages into an n8n workflow over Meta's official Cloud API, on a number the business still answers from the phone. No linked device.
• Connect WhatsApp to Claude with a custom connectorAdd EasyCoexistence as a custom connector and Claude can read, send and wire a real WhatsApp number over Meta's official Cloud API. One OAuth sign in.
• Connect WhatsApp to Make on the official Cloud APIRoute WhatsApp messages into a Make scenario over Meta's official Cloud API. Why Make uses the webhook path rather than our MCP server.
• Connect WhatsApp to Zapier on the official Cloud APITrigger a Zap from an incoming WhatsApp message over Meta's official Cloud API, and send replies back with a webhook action.
• Connect WhatsApp to ChatGPT with a custom connectorAdd EasyCoexistence as a connector in ChatGPT and it can read, send and wire a real WhatsApp number over Meta's official Cloud API.
• Connect WhatsApp to Cursor over MCPAdd EasyCoexistence to Cursor's MCP settings and send WhatsApp messages, manage templates and wire webhooks without leaving the editor.
• Connect WhatsApp to Claude Code over MCPOne command adds EasyCoexistence to Claude Code, so an agent can send WhatsApp messages, manage templates and wire webhooks from the terminal.
• Send and receive WhatsApp from PythonReceive WhatsApp messages in a Python web handler and send replies through Meta's official Cloud API, on a number a team still answers from the phone.
• Send and receive WhatsApp from Node.jsReceive WhatsApp messages in a Node handler and send replies through Meta's official Cloud API, on a number a team still answers from the phone.

比較

人們在選擇前會考慮的決定因素。

• EasyCoexistence vs a BSP inboxA BSP gives you a shared inbox and sits in the message path. Coexistence keeps the phone and routes messages to your own systems. When each one is right.
• EasyCoexistence vs building it yourselfEverything here is Meta's documented API, so you can build it. What that actually takes, and the part that is not the building.
• EasyCoexistence vs 360dialogBoth charge per number and neither marks up Meta's fees. The difference is the price and what the fee is for. Prices as published in September 2026.
• EasyCoexistence vs WATIWati is a WhatsApp inbox priced per seat with contact limits. EasyCoexistence charges per connected number and routes messages to your own system.
• EasyCoexistence vs respond.ioRespond.io is a multichannel inbox priced per seat and contact. EasyCoexistence charges per connected number, with no seats and nothing per message.
• EasyCoexistence vs DualhookBoth route WhatsApp webhooks directly from Meta and neither stores messages. Where they differ on price, tooling and what survives a reconnection.
• EasyCoexistence vs AiSensyAiSensy is a WhatsApp campaign platform sold on monthly plans. EasyCoexistence charges per connected number and delivers messages to your own system.
• EasyCoexistence vs InteraktInterakt is a WhatsApp commerce platform with per-agent plans. EasyCoexistence charges per connected number, with no seats and nothing per message.
• EasyCoexistence vs DoubleTickDoubleTick is a WhatsApp sales inbox priced per user. EasyCoexistence charges per connected number and routes messages into the CRM you already use.
• EasyCoexistence vs ZokoZoko is a WhatsApp commerce platform built for Shopify. EasyCoexistence is the layer underneath, charging per connected number with no seats.
• EasyCoexistence vs TrengoTrengo is a multichannel team inbox priced per user. EasyCoexistence charges per connected number and delivers WhatsApp to your existing helpdesk.
• EasyCoexistence vs RasayelRasayel is a WhatsApp sales inbox priced per user. EasyCoexistence delivers the conversation straight into your CRM, charging per connected number.
• EasyCoexistence vs CallbellCallbell is a small-team WhatsApp inbox priced per user. EasyCoexistence charges per connected number, so headcount never enters the bill.
• EasyCoexistence vs BaileysBaileys is an open-source linked-device library, which breaches WhatsApp's terms. EasyCoexistence connects the same number through Meta's own API.
• EasyCoexistence vs WPPConnectWPPConnect automates WhatsApp Web in a browser session, against WhatsApp's terms. EasyCoexistence uses Meta's official Cloud API through Coexistence.
• EasyCoexistence vs Evolution APIEvolution API wraps unofficial WhatsApp libraries behind a REST interface. EasyCoexistence uses Meta's official Cloud API, so the number cannot be banned.
• EasyCoexistence vs WhapiWhapi is a hosted unofficial gateway, so the number is reached outside Meta's API. EasyCoexistence connects it officially through Coexistence.
• The best WhatsApp Coexistence providersEvery provider that supports WhatsApp Coexistence, what each charges and who each suits. Prices from their own published pages, September 2026.
• The best WhatsApp Cloud API providersWhatsApp Cloud API providers compared by how they charge: per message, per seat, or per number. Prices from their own published pages.
• The best WhatsApp MCP serversWhatsApp MCP servers compared. Most open-source ones drive an unofficial bridge that risks a ban. EasyCoexistence runs on Meta's official Cloud API.
• EasyCoexistence vs TwilioTwilio adds a published per-message fee on top of Meta's. EasyCoexistence charges a flat monthly fee per number and never touches the message bill.
• EasyCoexistence vs GupshupGupshup publishes a per-message fee on top of Meta's. EasyCoexistence charges per number, so the cost stops moving once the number is connected.
• EasyCoexistence vs InfobipInfobip is enterprise CPaaS priced per country through sales. EasyCoexistence publishes one price list and connects a number in minutes.
• EasyCoexistence vs YCloudBoth support Coexistence with no per-message markup. YCloud sells a platform in seat-based tiers; EasyCoexistence sells infrastructure per number.
• EasyCoexistence vs SleekFlowSleekFlow is a seat-priced messaging platform with a minimum seat count. EasyCoexistence charges per connected number with no seats at all.
• EasyCoexistence vs BirdBird quotes one blended per-message rate with Meta's fee inside it. EasyCoexistence charges per number and leaves the Meta invoice untouched.
• EasyCoexistence vs ZenviaZenvia sells monthly software plans plus channel packages. EasyCoexistence charges one published fee per connected number, in reais or dollars.
• EasyCoexistence vs 8x88x8 is enterprise CPaaS with good Coexistence documentation. EasyCoexistence is the self-serve product that does what those docs describe.

開始使用

連接號碼，以及接下來會發生甚麼。

• Coexistence referenceWhat Coexistence is, how messages flow, what it costs, what it cannot do, eligibility, and how to roll it back. The short reference version.
• Connecting a number, step by stepWhat happens when you connect a number through Coexistence, what the business owner has to do, and what is decided once and cannot be changed.
• Which WhatsApp features stop working after CoexistenceDisappearing messages, view once, live location and broadcast lists are switched off on a connected number. What each one means in practice.
• Which numbers are eligible for CoexistenceThe app version, the account type, the portfolio access, and what actually makes Meta refuse a number during Coexistence onboarding.
• Rate limits and messaging throughputThe four separate WhatsApp Cloud API limits: messaging tier, throughput, per-recipient pairing and management calls.
• A number stopped working: how to find out whyA checklist in the order these failures actually happen: token, webhook override, inactivity disconnection, quality, and account restriction.
• What changes in the WhatsApp Business app after connectingEverything that stays the same on the phone after a number is connected through Coexistence, and the three things that genuinely change.
• What syncs to the API, and what does notContacts and one-to-one history cross over. Groups, catalog, labels, quick replies and away messages do not. The complete list, in one place.

Meta 平台

每個號碼背後的帳戶、識別碼和驗證步驟。

• Display names on a WhatsApp business numberThe name customers see above a conversation. How approval works, what gets rejected, and which webhook reports the decision.
• Meta Business Portfolio, and what sits inside itThe company level container in Meta Business Manager. What it holds, why it matters for a client's number, and how it differs from a WABA.
• Two step verification on a WhatsApp numberThe six digit PIN set on a WhatsApp Business number, which operations require it, and what to do when nobody remembers it.
• The WhatsApp Business Account, and why overrides live on itWhat a WABA holds, why webhook overrides are applied at this level rather than per number, and what that means when a connection is removed.

發送訊息

可以發送甚麼、何時可以發送，以及 Meta 會先檢查甚麼。

• The 24 hour customer service windowWhat the customer service window is, when it opens and closes, what may be sent inside and outside it, and why replies inside it are free.
• Which WhatsApp conversations Meta charges forReplies inside the customer service window are free. What Meta charges for, who it bills, and why a provider cannot mark it up.
• Message reactions: sending and receiving emojiSending and receiving WhatsApp message reactions through the Cloud API, including how a removed reaction arrives.
• WhatsApp message templatesWhat templates are, the three categories, how variables work, how review goes, and why on Coexistence they can only be sent through the API.
• Sending a template with variablesHow to fill WhatsApp template variables correctly: positional parameters, component lists, and the errors each mistake produces.
• Sending interactive messages: buttons and listsWhatsApp interactive messages: reply buttons, list messages, their exact limits and how replies come back on your webhook.
• Sending location and contact messagesSending location pins and contact cards through the WhatsApp Cloud API, and why live location is unavailable on a Coexistence number.
• Sending media: images, video, audio and documentsSending images, video, audio and documents on the WhatsApp Cloud API: size limits, supported formats, and why uploading beats linking.
• Template categories: utility, marketing and authenticationThe three template categories, what belongs in each, how they differ on billing and review, and why the wrong category is a reliable rejection.
• Template components: header, body, footer and buttonsThe four parts of a WhatsApp message template, what each one allows, and which of them accept variables.
• The template status lifecycleEvery state a WhatsApp template passes through, from submission to permanent disabling, and which webhook reports each one.

Webhook

事件如何傳送至您的系統，以及事件包含甚麼。

• The account_alerts webhookMeta's general alerting channel for a business account. What arrives here, and why it is a prompt to look rather than a state change.
• The account_review_update webhookMeta reports the outcome of an account review here. What the decision field carries, and why a rejection is worth treating as a degraded connection.
• The account_update webhook, and every disconnection reasonaccount_update reports connection state changes. The full list of disconnection reasons Meta sends, what each means, and which ones are recoverable.
• The business_capability_update webhookHow messaging limit changes arrive. What the tier means, why it moves in both directions, and how it differs from throughput.
• WhatsApp webhook fields, and which ones go whereThe eight webhook fields a Coexistence connection uses, what each carries, and which are routed to your endpoint versus kept for monitoring.
• The history webhookThe one time chat history transfer on a Coexistence number is delivered on this field. What arrives, when, and why it happens only once.
• The message_template_quality_update webhookMeta reports a template's quality moving here, before it results in a pause. What the signal means and why it is worth acting on early.
• The message_template_status_update webhookMeta reports template approvals, rejections and disabling here. What each status means and why it removes the need to poll.
• The messages webhookEverything a customer sends arrives on this field. What the payload carries, how to acknowledge it, and why it never reaches a provider on a routed number.
• The phone_number_name_update webhookMeta reports display name approvals and rejections here. It is the only place the decision appears, and nothing shows it in the app.
• The phone_number_quality_update webhookWhat this webhook actually carries as of 2026, why the colour quality rating is not in it, and where the rating has to be read from instead.
• The smb_app_state_sync webhookContact synchronisation from the WhatsApp Business app arrives on this field. What it carries and why it is separate from message history.
• The smb_message_echoes webhookHow software sees what a human sent from the WhatsApp Business app. Only exists on Coexistence numbers, and ignoring it causes double replies.
• The template_category_update webhookMeta can move a template between utility, marketing and authentication after approval. This reports it, and it changes what each send costs.
• Verifying a WhatsApp webhook endpointMeta calls your endpoint with a GET challenge before delivering anything. What it sends, what to return, and why a wrong answer fails silently.

MCP 連接器

從 AI 助手連接至號碼。

• MCP or a webhook: which one you actually needMCP acts when asked. A webhook reacts when something happens. Why an assistant cannot answer customers on its own, and why most systems need both.
• MCP tools referenceAll eleven tools the EasyCoexistence MCP connector exposes, what each takes, and which are gated when billing lapses.

錯誤代碼

我們的用戶實際遇到的所有錯誤，均來自 Meta 發佈的參考資料。

• 100invalid parameter
• 190access token expired
• 368account restricted by policy
• 80007rate limit on the WhatsApp Business Account
• 130429throughput limit reached
• 130497recipient country not allowed
• 131000something went wrong
• 131008required parameter missing
• 131009invalid parameter value
• 131016service unavailable
• 131021sender and recipient are the same
• 131026message undeliverable
• 131031account restricted or data mismatch
• 131042business account payment issue
• 131045phone number not registered
• 131047re-engagement message
• 131048spam rate limit hit
• 131049message blocked for ecosystem health
• 131050the user has opted out
• 131051unsupported message type
• 131052media download failed
• 131053media upload failed
• 131056too many messages to one recipient
• 132000parameter count mismatch
• 132001template does not exist
• 132007template policy violation
• 132012template parameter format mismatch
• 132015template paused for quality
• 132016template is permanently disabled
• 133005incorrect two-step verification PIN
• 133006phone number not verified
• 133008too many PIN guesses
• 133010phone number not registered
• 2593107synchronization limit exceeded
• 2593108sync outside the 24 hour window
• codesWhatsApp Cloud API error codes

支援

如果這裡沒有解答您的問題，請寫信至 matheus@tonelotto.com.