Meta Tech Provider

Glosari WhatsApp Coexistence

Istilah berkaitan WhatsApp Coexistence mudah mengelirukan. Kekeliruan biasanya berlaku apabila dua orang menggunakan satu perkataan untuk perkara yang berbeza. Ini ialah definisi yang digunakan oleh laman ini, setiap satunya dipautkan ke halaman yang menerangkannya dengan lebih lanjut.

Tiada penyimpanan mesejAplikasi Perniagaan + Cloud APIMCP untuk Claude dan ChatGPTHidup dalam 2 minit

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

Mengapa perbendaharaan kata ini begitu mengelirukan?

Kerana beberapa istilah ini menamakan perkara pada tahap berbeza, tetapi semuanya kelihatan seperti berada pada tahap yang sama.

Business Portfolio mengandungi WhatsApp Business Account, yang mengandungi nombor telefon, setiap satunya dengan phone number id. Dalam perbualan, keempat-empatnya dipanggil akaun. Ayat seperti semak sama ada akaun berfungsi boleh bermaksud empat pemeriksaan yang berbeza. Perkara yang sama berlaku pada dua tetingkap dua puluh empat jam di platform ini. Kedua-duanya mengukur perkara yang tidak berkaitan dan sering tertukar.

Sebahagian lagi berpunca daripada Meta dan penyedia yang menggunakan istilah berbeza untuk perkara yang sama. Penyedia juga tidak semestinya bersetuju antara satu sama lain. Halaman ini menggunakan perbendaharaan kata Meta sendiri apabila tersedia, dan menyatakan dengan jelas apabila sesuatu istilah ialah istilah kami.

Apakah perbezaan yang benar-benar penting dalam amalan?

Tiga, dan setiap satunya pernah menyebabkan seseorang kehilangan masa sehari.

Tetingkap khidmat pelanggan dan tetingkap penyegerakan kedua-duanya berlangsung selama dua puluh empat jam, tetapi tidak berkaitan antara satu sama lain. Satu menentukan sama ada teks bebas boleh dihantar, dikira dari mesej terakhir pelanggan. Satu lagi menentukan sama ada sejarah chat masih boleh ditarik masuk, dikira dari pendaftaran.

Peranti terpaut bukan API. Ia ialah klien WhatsApp pengguna yang dilog masuk di tempat lain. Inilah yang diautomatikkan oleh alat tidak rasmi dan yang menyebabkan nombor disekat.

Destinasi webhook pula bukan tetapan pada nombor. Ia ialah penggantian pada langganan app kepada akaun. Sebab itu ia hilang apabila sambungan dibuang dan perlu ditetapkan semula apabila sambungan dibuat semula.

Soalan lazim

Adakah Coexistence API yang berbeza daripada Cloud API?

Tidak. Coexistence ialah cara mendaftarkan nombor ke Cloud API sambil memastikan app WhatsApp Business terus berfungsi padanya. endpoint, format mesej dan peraturannya sama.

Apakah perbezaan antara Business Portfolio dan WABA?

Business Portfolio ialah bekas peringkat syarikat dalam Meta Business Manager. WhatsApp Business Account berada di dalamnya dan menyimpan nombor telefon. Satu portfolio boleh menyimpan beberapa WABA.

Adakah BSP sama dengan Tech Provider?

Kedua-duanya bertindih, tetapi menerangkan perkara yang berbeza. Tech Provider ialah status Meta yang membenarkan syarikat menyambungkan nombor perniagaan lain melalui app sendiri. BSP biasanya merujuk kepada syarikat yang menjual platform pemesejan, dan mungkin mempunyai status itu atau tidak.

Apakah kaitan MCP dengan WhatsApp?

Tiada kaitan secara semula jadi. MCP ialah protokol untuk memberikan pembantu AI akses kepada alat, dan pelayan WhatsApp MCP mendedahkan nombor sebagai salah satu alat itu. Ia tidak boleh menerima mesej, sebaliknya hanya bertindak apabila diminta.

Sedia untuk bermula?

Sediakan WhatsApp Coexistence dalam beberapa minit, bukan berbulan-bulan. Aplikasi terus berfungsi pada telefon.

Mulakan Percubaan PercumaTiada caj selama 7 hari. Batalkan pada bila-bila masa.

Teruskan membaca

GuideWhatsApp Coexistence: the app and the API on one numberCoexistence is Meta's official mode for running the WhatsApp Business app and the Cloud API on one number at the same time.ReferenceWhat changes in the WhatsApp Business app after connectingAlmost nothing changes on the phone.ReferenceThe 24 hour customer service windowThe customer service window opens when a customer messages your number and lasts 24 hours.GuideWhat being a Meta Tech Provider means, and why it mattersA Meta Tech Provider runs its own Meta app on a verified Business Manager and can connect other businesses' WhatsApp numbers through it.GuideCan you use the WhatsApp Business app and the API on the same number?Yes.GuideHow to connect WhatsApp to an API without losing your chatsYour chats live on the phone and connecting to the API does not move them.