Skip to main content

WhatsApp Business Account - Subscribed Apps API | Developer Documentation

Check the message receiver after changing a connected tool

Use this checklist when a CRM, application or receiving endpoint has changed and messages or results appear in the wrong place. Identify the actual ChatArchitect receiver arrangement for that connection before changing additional settings.

Record the old and intended routes

  • The connected business number and the workspace or application it should serve.
  • The old receiving tool or endpoint, its owner and whether it should remain active.
  • The intended receiving tool or endpoint and the person responsible for its handler.
  • The agreed change time and a way to compare the observed results.

For a CRM or help desk, ask the integration owner or support to confirm its receiving configuration. For a custom application, use the receiver guide and the documented ChatArchitect registration and event examples. Confirm the scope of the change before replacing a working CRM callback.

Test incoming messages and outgoing results separately

TestEvidence to compare
An agreed contact sends a distinctive messageWhich endpoint or tool receives it and which conversation displays it.
The connected tool sends an appropriate replyThe request reference and any later result received for that attempt.
The old receiver should no longer handle the routeObserved behavior in the old tool or endpoint against the agreed change plan.

Record the business number, direction, time and references that the tools actually expose. Do not infer that every event shares the same routing or that all integrations support parallel receivers.

Locate where the result stops

If the expected callback arrives but the CRM conversation is missing, ask the application owner to check how that handler processes and stores the event. If the callback itself is missing, ask support to confirm the receiving arrangement for the connection before changing account-level Meta subscriptions.

A list of Meta applications subscribed to a WhatsApp account does not establish the ChatArchitect receiver URL or the CRM workspace receiving its events. Customer App key and Secret do not authorize that Meta subscription API. Keep any separate Meta developer implementation with its own responsible team.

Close the change with evidence

Confirm the intended incoming conversation and outgoing result against the agreed tests, identify any remaining old route and record who owns unresolved differences. For a reporting mismatch, use the report comparison guide.

No comments to display