Multi-Partner Solution — Embedded creation | Developer Documentation

Check the entry point when a setup screen looks unfamiliar

ChatArchitect customers use its prepared WhatsApp connection. ChatArchitect does not provide partners with a supported method for embedding their own Meta signup in a website. The old embedded partner-solution code on this page described a separate provider application, not a replacement for the supplied customer flow.

Identify what you opened

1. Record the link or tool that opened the screen, the displayed application/company name and the task you intended to complete.
2. Check whether the screen asks to connect your business number or to create a relationship between provider applications.
3. If the purpose is unclear, ask the company that sent the link to identify the request and its relationship to your ChatArchitect setup. Send a redacted screenshot and the point where the screens diverged.

Do not add a JavaScript button or grant another application's permissions merely to reproduce a screenshot from imported documentation.

Return to the confirmed customer flow

Use the entry point supplied for your ChatArchitect connection. Follow the signup overview and connection troubleshooting guide; confirm the intended business assets before authorizing access. If the account or number cannot be selected, use the comparison of the account view and signup choice rather than creating an alternative asset to bypass the mismatch.

If an implementer has already embedded separate Meta code, ask them to explain which service it implements and agree how it will be corrected. Existing websites and working connections should be reviewed before making changes.

Check completion in the connected system

Returning from a login or consent screen does not prove that the sending integration is ready. Record the selected business account and number, configure the intended tool, and perform the agreed incoming/reply check. Report the stage that did not finish instead of treating a third-party confirmation screen as a ChatArchitect result.

Historical Meta reference illustrations

These original illustrations show the separate Meta provider workflow retained from the former reference. They do not establish current screens, eligibility, a ChatArchitect customer control or supported parallel connections. Use the confirmed customer instructions above for your setup.