Skip to main content
Identify which operation failed before changing account settings. Setup problems and unavailable runtime paths need different responses.
Account setup has a current configuration workflow. Messaging and calling remain planned, and the outbound routes return HTTP 501. Reconnecting an account does not implement those routes.

​
Start with the observed result

Have the workspace and phone identifiers, the attempted action, its time, and any error code. Exclude authorization codes, tokens, registration PINs, and customer message bodies from shared diagnostics.
1

Read the saved account

Follow account setup. Confirm registration, is_token_expired, and assigned_agent_id. Check the selected workspace before concluding that a connection disappeared.
2

Resolve uncertain setup outcomes

Refresh the account list and inspect the record before importing again. Use Refresh registration status to check registration. Use Retry phone registration only when the current account offers it. Re-read the resulting state rather than relying on a success notification alone.
3

Escalate with bounded evidence

Record the operation, safe identifiers, response status, and whether the failure concerns setup or execution. For a future provider submission, preserve its message identifier and returned error. Do not report delivery from account registration or from local preference changes.
For later payload diagnosis, compare the selected operation with Meta’s official Cloud API reference collection and Threetone’s outbound contract. Their supported request shapes are not interchangeable.

​
Frequently asked questions

No. Deletion changes the account connection and may affect provider setup. It does not release outbound execution.
No. Registration, authorization, provider submission, delivery, and agent processing are separate states.