> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp

> Prepare a WhatsApp Business account connection, review phone registration and agent assignment, and understand planned messaging and calling.

WhatsApp is a planned conversation channel for Threetone agents. The current dashboard supports the account-connection and settings workflow when the deployment has Meta Embedded Signup configured. Account setup and conversation execution have separate availability requirements.

<Note>
  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.
</Note>

## Choose a guide

<CardGroup cols={2}>
  <Card title="Connect an account" icon="link" href="/agents-platform/deploy/whatsapp/connect-account">Authorize the intended business account, review phone registration, and save its agent assignment.</Card>
  <Card title="Messaging and calls" icon="comments" href="/agents-platform/deploy/whatsapp/messaging-and-calls">Review the planned channel and the checks required before sending messages or making calls.</Card>
</CardGroup>

## Account setup and runtime availability

| Area | Current documented behavior |
| - | - |
| Account authorization | A configured HTTPS dashboard can start Meta Embedded Signup and submit the authorized account to Threetone. |
| Phone registration | The account exposes a registration state, refresh action, and a retry action when available. |
| Agent assignment | Account settings can store the selected agent or No agent. |
| Messaging preferences | Settings store messaging, audio-response, and typing-indicator preferences for future support. |
| Outbound messages and calls | Provider execution is not implemented; the public routes return HTTP 501. |
| Incoming messages and calls | An account connection is not evidence of a verified incoming conversation workflow. |

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](/agents-platform/configure/overview), [language settings](/agents-platform/configure/voice-and-language/overview), and [tools](/agents-platform/configure/tools/overview). 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

<AccordionGroup>
  <Accordion title="Can I prepare an account before messaging is available?" id="faq-whatsapp-account-preparation">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.</Accordion>
  <Accordion title="Does Phone registered mean the agent is live?" id="faq-whatsapp-registration-vs-runtime">No. Registration, authorization, agent assignment, and runtime execution are separate checks.</Accordion>
  <Accordion title="Are message and call instructions available now?" id="faq-whatsapp-outbound-availability">The current outbound routes return HTTP 501. The [planned messaging and calls guide](/agents-platform/deploy/whatsapp/messaging-and-calls) records what must be verified before adding a working execution walkthrough.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.