WhatsApp Coexistence 詞彙表
WhatsApp Coexistence 相關詞彙容易混淆,實際上很多混亂源於兩人用同一個詞指不同事物。以下是本網站採用的定義,並連結至詳細說明各詞彙的頁面。
- Coexistence
Meta's official mode for running the WhatsApp Business app and the Cloud API on one number at the same time. Not a separate API: the same Cloud API, onboarded so the app keeps working.
WhatsApp Coexistence- Cloud API
Meta's hosted WhatsApp Business Platform API. Every send, template and webhook on this site runs through it.
Cloud API or Coexistence- WhatsApp Business app
The app a business uses on a phone. Distinct from the consumer WhatsApp app, and a number must be on it before Coexistence can connect it.
- WhatsApp Business AccountWABA
The Meta object that holds phone numbers and templates. Sits inside a Business Portfolio. Webhook overrides are applied at this level rather than per number.
- Business Portfolio
The company level container in Meta Business Manager. Holds one or more WhatsApp Business Accounts. A client's number stays in their portfolio, not a provider's.
Meta Tech Provider- Phone number id
Meta's identifier for one connected number. Sending targets this rather than the number itself, and it appears in every inbound webhook payload.
- Embedded Signup
Meta's own onboarding popup. Picks the portfolio, the account and the number, and for Coexistence includes a code scanned in the WhatsApp Business app.
How a number connects- Tech Provider
A Meta status permitting a company to connect other businesses' numbers through its own approved app. Free to obtain, gated on business verification and App Review. Not an endorsement.
What it means- BSPBusiness Solution Provider
A company selling a messaging platform, usually a shared inbox. Overlaps with Tech Provider but describes the product rather than the Meta status.
Coexistence or a BSP- Webhook destinationwebhook override
Where Meta delivers a WhatsApp Business Account's events. Set as an override on an app's subscription, which is why removing a connection uninstalls it.
WhatsApp webhooks- hub.challenge
A value Meta sends in its verification GET. The endpoint must return it as the raw body. Returning JSON instead is the most common reason a webhook never receives anything.
Webhook verification- messages
The webhook field carrying what customers send. Part of the message path, which is what a webhook override routes away from a provider.
- smb_message_echoes
The webhook field carrying what a team sends from the WhatsApp Business app. Only exists on Coexistence numbers, and is how software sees a human's replies.
- Customer service windowthe 24 hour window
Twenty four hours from the customer's last message, during which free text delivers. Outside it, only an approved template does.
Error 131047- Template
A message submitted to Meta for review in advance. The only thing that delivers outside the customer service window, and on a Coexistence number it can only be sent through the API.
Error 132001- Quality rating
Green, yellow or red, assigned by Meta from how recipients react. Falls before it costs anything, and nothing announces the fall.
Error 131048- Messaging tier
How many unique customers a number may start conversations with per day. Moves in both directions. Distinct from throughput, which is a rate.
- Throughput
Messages per second a number may send. Fixed by Meta on a Coexistence number rather than scaling with quality and tier.
Error 130429- Linked device
The consumer WhatsApp client signed in elsewhere, as WhatsApp Web does. What unofficial tools automate, what WhatsApp's terms prohibit, and what gets numbers banned.
Unofficial API risks- MCPModel Context Protocol
How an AI assistant reaches a tool it does not own. Request and response only: an MCP server cannot be woken by an incoming message.
WhatsApp MCP server
為甚麼詞彙會造成這麼多問題?
因為當中有幾個詞彙所指的是不同層級的事物,但看起來都像處於同一層級。
Business Portfolio 內含 WhatsApp Business Account,而 WhatsApp Business Account 內含多個電話號碼,每個號碼都有 phone number id。在日常對話中,這四者都會被稱為帳戶,因此「檢查帳戶是否正常運作」一句話,可能代表四種不同的檢查。本平台的兩個二十四小時時段也有同樣問題,它們衡量互不相關的事物,卻經常被混為一談。
另一半原因是,Meta 和服務供應商對同一事物使用不同詞彙,而各服務供應商之間也沒有統一說法。本頁在有 Meta 原有詞彙時會採用該詞彙,並在詞彙由我們定義時直接說明。
哪些區分在實際使用中最重要?
有三項,而且每一項都曾令某人浪費一天時間。
客戶服務時段和同步時段都是二十四小時,但兩者完全無關。前者決定免費文字訊息能否送達,時間由客戶上次發送訊息起計。後者決定仍能否提取聊天記錄,時間則由啟用流程起計。
已連接裝置不是 API。它是登入於其他地方的消費者 WhatsApp 用戶端,也正是非官方工具自動操作的對象,並會導致號碼被封鎖。
Webhook 目的地也不是號碼上的設定,而是應用程式訂閱帳戶時的覆寫設定。因此,移除連接後它會消失,重新連接時必須再次設定。
常見問題
Coexistence 是不同於 Cloud API 的另一個 API 嗎?
不是。Coexistence 是將號碼啟用至 Cloud API 的方式,同時保留 WhatsApp Business 應用程式在該號碼上的運作。端點、訊息格式及規則完全相同。
Business Portfolio 和 WABA 有甚麼分別?
Business Portfolio 是 Meta Business Manager 內公司層級的容器。WhatsApp Business Account 位於其中,並持有電話號碼。一個 Business Portfolio 可以持有多個 WABA。
BSP 和 Tech Provider 是同一回事嗎?
兩者有重疊,但指的是不同事物。Tech Provider 是 Meta 授予的身分,容許公司透過自己的應用程式連接其他企業的號碼。BSP 通常指銷售訊息平台的公司,而該公司未必持有這項身分。
MCP 與 WhatsApp 有甚麼關係?
兩者本身沒有必然關係。MCP 是讓 AI 助手存取工具的協定,而 WhatsApp MCP 伺服器會將號碼公開為其中一項工具。它不能接收訊息,只能在收到要求時執行操作。
準備開始嗎?
幾分鐘內設定 WhatsApp Coexistence,而非幾個月。應用程式在手機上仍可繼續運作。
開始免費試用7 天內不收取任何費用。隨時取消。