partner_solutions webhook reference | Developer Documentation

Start with the notice and the customer outcome

A notification about a provider relationship is different from an incoming WhatsApp message or an outgoing message result. The imported Meta partner_solutions event reference did not establish that ChatArchitect forwards those events to a customer receiver.

Identify the source and scope

• Record where the notice was received: an administrative screen, email, a developer's Meta receiver or your application's callback.
• Keep the observation time, visible event label and available business, application or solution references.
• Ask the person responsible for that system what the notice means and which account or proposed change it concerns.
• Record the customer impact separately: setup cannot finish, access changed, a message result is missing, or no service difference has been observed.

If it arrived at an application callback, identify the actual sending service and the documented event contract before changing a handler. A familiar field name is not proof that the payload follows the ChatArchitect contract.

Check the relevant evidence

For incoming chats and outgoing results, use the customer receiver guide and current API Quick Start. Those records must be tied to the observed message or request; a partner-status label does not prove that a customer's message was sent or delivered.

For an administrative relationship, compare the provider record and its scope. If another company is proposing a change, use the responsibility checklist and agree the change plan before replacing access or the working connection.

Escalate without changing the wrong workflow

Send the responsible contact a redacted notice, its source and time, the relevant number/account and the observed difference from expected behaviour. Ask whether any customer action is required and which evidence confirms it.

Do not use an unverified partner event to mark a message as delivered, close a CRM task, enable sending or switch a receiver. Any additional ChatArchitect event names, payloads and identifier mappings need the service's documented contract. Their availability remains unconfirmed here.