Skip to main content
Prepare one reviewed outbound request before designing bulk outreach. Keep the business phone, recipient, message purpose, and agent version together in the review.
Both outbound WhatsApp routes currently return HTTP 501. Account registration and saved preferences can be reviewed, but they do not enable sending or calling. Do not retry 501 as a transient provider failure.

​
Review the request contract

You need an authorized connected account, a controlled test recipient, and an approved reason to contact that person.
1

Verify the account and recipient

Read registration, authorization expiry, and agent assignment back. Confirm the exact recipient and the applicable provider permission requirements. A phone number copied from a record is not permission to contact its owner.
2

Review the template and language

Compare the intended text and parameter order with the provider’s template. Meta’s template reference explains template components and button behavior. Review current template eligibility in the provider account. A message template does not establish permission to initiate a call.
3

Define submission and reconciliation

For a future released sender, record one application request identifier and retain the provider result. Separate queued, submitted, delivered, and failed outcomes. After an uncertain submission, reconcile before repeating it. Do not claim a Threetone idempotency header or delivery webhook that is not in the released contract.
Compare your review with the message and call reference pages. The current result is prepared request data, not a sent message or connected call.

​
Frequently asked questions

No. Validation and execution are separate. The provider execution path remains unimplemented.
Do not infer bulk execution from a single-request schema. Batch execution, recipient policy, per-recipient outcomes, and duplicate prevention require their own released workflow.