Skip to main content

Embedded Signup | Developer Documentation

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 install their own Meta Embedded Signup implementation through ChatArchitect.

This overview helps you choose the right account and understand the result of setup. For screen-by-screen number instructions, use the phone-number guide and illustrated connection guide. For an interrupted or incomplete setup, use the completion and troubleshooting guide.

Start the prepared connection

Open the WhatsApp connection setup supplied by ChatArchitect and select Continue with Facebook. Continue through the Meta form, select the intended business portfolio, add the number and complete verification by SMS or voice call. Use the actual prompts shown for your account.

The connection flow and the sending integration are separate parts of setup. After completing the form, return to ChatArchitect and check that the intended number is available in the connection. Then configure the supported CRM, help desk or application that will use it.

Check the business account before authorizing access

Identify the business portfolio, WhatsApp Business account and phone number your team intends to use. Have the person responsible for those assets confirm the selection before continuing. If the expected portfolio or account is missing, resolve access with that person or ChatArchitect support before creating another account.

Read the requested access and terms on the authorization screen. Keep a record of the business and number chosen for the connection so you can check the same assets after returning. A successful login by itself is not a check that the intended number is connected or that the selected CRM can send messages.

Use the credentials for your ChatArchitect connection

A ChatArchitect customer uses the connection's App key and Secret in the supported sending tool. Follow the ChatArchitect credentials guide and the instructions for your integration. The customer setup does not require creating a Meta developer app, writing a JavaScript login callback or obtaining a Meta System User access token.

For a custom application, continue with the ChatArchitect API preparation guide. Confirm which connection the credentials belong to and keep the Secret in the application's secure configuration. The Meta provider setup described in imported technical references does not define the customer's ChatArchitect API request or callback format.

Check an existing number and the sending conditions

If the number already belongs to another WhatsApp account or provider, confirm the supported route before changing it. ChatArchitect supports continued use of WhatsApp Business app on a connected number; the entry route and history or contact synchronization need their own confirmation. Use the coexistence guide for that scope.

Number verification, Meta business verification and readiness to send are separate checks. Use the messaging-limits guide to distinguish Meta's messaging restriction from the ChatArchitect plan. Completing signup does not establish a specific allowance, an automatic limit increase or support for every feature listed in a Meta reference.

Check the ChatArchitect commercial terms

The customer pays ChatArchitect under its applicable terms. Check the ChatArchitect pricing explanation and current plan page for the service you are connecting.

Ask for clarification if a billing screen or imported provider guide appears to describe a different arrangement. Do not use a provider credit-line instruction as the billing procedure for your ChatArchitect connection.

Verify the supported workflow with a small test

Agree a permitted test with a recipient and use the intended connection in your supported tool. Check the message rules, the send result and the receiving conversation. If replies are part of the workflow, check where your chosen integration receives them.

For a custom application, prepare its send and reply handling using the current ChatArchitect API instructions. A test account, artificial phone number or developer helper mentioned in Meta's provider documentation does not establish a customer test route through ChatArchitect.

Keep a completion record

Record the selected portfolio, WhatsApp account, connected number and sending integration. If setup is incomplete, retain the affected step, time with time zone and exact error for ChatArchitect support. Share a redacted screenshot if useful; omit passwords, verification codes, security PINs and Secret values.

Use the signup completion guide to separate an unfinished Meta form, a missing connection in ChatArchitect and a problem in the sending tool. Meta's provider overview describes the platform implementation for organizations building their own onboarding.