> ## 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.

# Messaging and calls

> Prepare WhatsApp messaging and calling requirements without treating account setup or saved preferences as released execution.

Threetone plans to support WhatsApp conversations. Account authorization, phone registration, agent assignment, message processing, and calling must work together before the channel can be used with customers.

<Note>
  The documented outbound message and call endpoints currently return HTTP 501. This page describes preparation and release requirements. It is not a working send-message or call tutorial.
</Note>

## Messaging preparation

Before a messaging release, define the supported incoming and outgoing message types, template and language handling, delivery status, conversation continuity, and failure behavior. Confirm the provider's current consent and template requirements for the intended use. Do not assume that an approved account or a saved preference grants every messaging capability.

Keep tool credentials out of message content and prompts. Review [personalization](/agents-platform/configure/personalization/dynamic-variables) and [knowledge](/agents-platform/configure/knowledge-base/overview) against the data the channel is allowed to use. Stored example values do not demonstrate live variable substitution.

## Calling preparation

Before a calling release, verify the supported direction, provider permissions, phone registration, agent speech configuration, caller identity, connection failures, and stored call records. A phone usable for messaging is not automatic proof of calling access.

Record the exact agent version and provider account used in a controlled test. Confirm the result through the supported provider and conversation records before claiming that a call connected or an external action completed.

## Release checks

| Check | Evidence required before a working walkthrough |
| - | - |
| Account access | Intended workspace, provider account, phone, and valid authorization. |
| Registration | Confirmed phone registration or an explicit supported provider state. |
| Incoming handling | Verified event ingestion, duplicate handling, routing, and conversation ownership. |
| Outgoing messages | Verified provider submission, delivery outcomes, and safe handling of retries and uncertain results. |
| Calls | Verified permissions, session initiation, connection, termination, and saved records. |
| Settings | Demonstrated enforcement of enabled messaging and other released preferences. |

The existing public API reference includes [outbound messages](/api-reference/agents-platform/send-outbound-message-via-whatsapp) and [outbound calls](/api-reference/agents-platform/start-outbound-call-via-whatsapp). Schema presence does not establish working execution. Do not retry HTTP 501 as though it were a temporary delivery failure.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can enabling messaging make the current outbound endpoint work?" id="faq-whatsapp-messaging-setting">No. The preference stores future behavior. The current outbound implementation remains unavailable.</Accordion>
  <Accordion title="Is an account authorization enough for a call?" id="faq-whatsapp-call-permissions">No. Provider calling permissions, phone state, agent configuration, and runtime execution must be verified separately for the released channel.</Accordion>
  <Accordion title="Where should I start today?" id="faq-whatsapp-current-start">Review [account setup](/agents-platform/deploy/whatsapp/connect-account) if that workflow is enabled in the deployed dashboard, then prepare the configuration and controlled test cases for the future channel release.</Accordion>
</AccordionGroup>


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