Skip to main content
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.
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.

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 and knowledge 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

The existing public API reference includes outbound messages and outbound calls. Schema presence does not establish working execution. Do not retry HTTP 501 as though it were a temporary delivery failure.

Frequently asked questions

No. The preference stores future behavior. The current outbound implementation remains unavailable.
No. Provider calling permissions, phone state, agent configuration, and runtime execution must be verified separately for the released channel.
Review account setup if that workflow is enabled in the deployed dashboard, then prepare the configuration and controlled test cases for the future channel release.