Search Results

ChatArchitect scope: Native Meta product catalogs, product cards, shopping carts and catalog order events are not supported by ChatArchitect. Review catalog availability in ChatArchitect when this imported payment reference mentions product messages. Confirm s...

ChatArchitect scope: Native Meta product catalogs, product cards, shopping carts and catalog order events are not supported by ChatArchitect. Review catalog availability in ChatArchitect when this imported payment reference mentions product messages. Confirm s...

Connect WhatsApp through ChatArchitect Embedded Signup Use the prepared WhatsApp connection in ChatArchitect to authorize the intended business account and connect a phone number. ChatArchitect supplies this setup flow. Customers and partner developers do not ...

Complete or troubleshoot WhatsApp signup in ChatArchitect Use this checklist when the prepared Continue with Facebook connection has been interrupted, returned an error or finished without a usable connection in your sending tool. It covers the customer setup ...

Automatic lead and purchase events: ChatArchitect availability ChatArchitect does not support Automatic Events API: automatic identification of leads or purchases in conversations started from Click-to-WhatsApp ads, followed by reporting those events to Meta C...

Why automatic_events is not a ChatArchitect callback workflow ChatArchitect does not support automatic detection of leads or purchases from Click-to-WhatsApp conversations and reporting those events to Meta Conversions API. Do not expect the Meta automatic_ev...

Who sets up a WhatsApp connection with ChatArchitect? Use this guide when your business wants to connect WhatsApp to a CRM, help desk or custom application through ChatArchitect. ChatArchitect supplies the ready-made connection. Customers and partner developer...

Check the WhatsApp business account used by your connection Before configuring the sending tool, confirm which business portfolio, WhatsApp business account and phone number you intend to connect. This customer checklist helps you identify the assets selected ...

Use the credentials for your ChatArchitect connection A custom service connected through ChatArchitect uses the App key/App ID and Secret supplied by ChatArchitect. The API quick start calls these credentials APP_ID and APP_SECRET and uses them as the Basic ...

Match the business number to the intended integration Keep a clear record of the business phone number your team will use with ChatArchitect. The business number, its display name, the selected WhatsApp account and the recipient's number describe different par...

Check billing for your ChatArchitect WhatsApp connection For WhatsApp messaging through ChatArchitect, the customer pays ChatArchitect under the applicable plan and separate commercial terms. Meta's provider credit-line documentation describes an internal plat...

Manage the receiver for your ChatArchitect connection A custom application uses a receiver to get incoming customer messages and later results of outgoing attempts from ChatArchitect. Start with the webhook overview and the API quick start for the documented r...

Meta provider reference: provider application registration and review. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/...

Meta provider reference: starting a Meta Solution Partner implementation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App k...

Meta provider reference: measurement-partner documentation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and ...

Meta provider reference: a Meta provider programme upgrade. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and ...

Meta provider reference: review of a Meta developer application. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID...

Meta provider reference: partner-initiated account creation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and...