Outbound WhatsApp messages and calls currently return HTTP 501 in the documented implementation. Account registration and saved messaging preferences do not establish incoming message handling or working calls. This section covers account preparation and future channel requirements.
Choose a guide
Connect an account
Authorize the intended business account, review phone registration, and save its agent assignment.
Messaging and calls
Review the planned channel and the checks required before sending messages or making calls.
Account setup and runtime availability
Check both registration and authorization before preparing a channel test. A phone registration result confirms that particular registration step. It does not prove that an agent can receive, respond, or call.
Prepare the agent
Review the intended agent’s configuration, language settings, and tools. Keep its workspace and version identifiers with the account configuration. An assignment selects a saved resource; it does not release a runtime feature. Use controlled account and customer data for future tests. Keep provider authorization codes, tokens, registration PINs, and credential values out of prompts, screenshots, and documentation.Frequently asked questions
Can I prepare an account before messaging is available?
Can I prepare an account before messaging is available?
Use the account setup workflow only when it is enabled in the deployed dashboard. You can review saved account settings separately from the unavailable conversation paths.
Does Phone registered mean the agent is live?
Does Phone registered mean the agent is live?
No. Registration, authorization, agent assignment, and runtime execution are separate checks.
Are message and call instructions available now?
Are message and call instructions available now?
The current outbound routes return HTTP 501. The planned messaging and calls guide records what must be verified before adding a working execution walkthrough.