Before you begin
Open Threetone over HTTPS, select the intended workspace, and use an account permitted to manage the connection. Have access to the WhatsApp Business account you intend to authorize. The deployed dashboard must have Meta Embedded Signup enabled and configured. Allow its authorization popup to open.If Import account is disabled, check the workspace, deployment configuration, and whether the authorization SDK has loaded. Do not paste a provider token into another settings field to bypass a disabled import workflow.
Recording pending: Connect and review a WhatsApp account using controlled demo data. Follow the written guide below.
Authorize and inspect
1
Start the account flow
Open WhatsApp accounts and select Import account. Check the selected workspace before continuing.
2
Review the Meta authorization
Follow the provider popup, select the intended business account and phone, and review the requested access. Finish the supported authorization flow. Do not copy its authorization code or a provider token into a prompt, support message, or recording.
3
Read the account back
Return to the account list and open the connected phone’s entry. Confirm the business account, phone number, and registration status. If the completion result was uncertain, refresh and inspect the list before starting another import.
Screenshot pending: WhatsApp account details with synthetic account identifiers, phone registration status, and Agent selection.
Review registration and authorization
The status badge distinguishes Phone registered, Registering phone, Registration unconfirmed, Registration needs attention, and Registration not checked. Authorization expired takes precedence when the stored authorization has expired. Use Account actions > Refresh registration status to inspect registration. Retry phone registration is offered for an unconfirmed or action-required state. Follow any returned error and inspect the refreshed account. A registration retry does not restore expired authorization or start agent execution. The WhatsApp Manager action opens the provider’s account management interface. Review provider-owned account details there rather than inferring them from a Threetone status badge.Save the intended account settings
Use Agent to select the intended saved agent or No agent. The selection saves the assignment immediately. Reopen the account to confirm it. The Messaging preferences section currently saves these future preferences:- Enable messaging records whether the assigned agent should respond when messaging becomes available.
- Enable audio message response records whether future audio-message replies should use audio.
- Enable typing indicator records the requested future read/typing feedback.
Disconnect deliberately
Inspect dependencies and the phone’s use by other providers before using Account actions > Delete account. Review the confirmation’s described Cloud API disconnection and connection removal before proceeding. Threetone’s account removal does not mean that the WhatsApp Business Account, phone number, or message history is deleted from Meta. If removal returns an uncertain provider outcome, inspect the account and resolve that state before reimporting. Keep provider account management separate from local resource cleanup.Frequently asked questions
Why is Import account unavailable?
Why is Import account unavailable?
The workflow needs a selected workspace, valid deployment signup configuration, a loaded authorization SDK, and HTTPS. Check those prerequisites and the current release before retrying.
Does assigning an agent start incoming responses?
Does assigning an agent start incoming responses?
No. The assignment is saved configuration. Incoming handling needs its own released and verified message or call runtime.
Can I repeat the import after an unclear result?
Can I repeat the import after an unclear result?
Refresh the account list and inspect the saved registration and authorization state first. Avoid treating an uncertain result as proof that nothing was created.