OrbiLattice – AI Property Signals to Orchestrated Action

Twilio

Choose and validate the workspace's administrative Twilio connection. Calling, messaging, phone-number selection, and compliance approval remain separate workflows.

Twilio provider connectionAdministrative setup only

Loading Twilio connection…

A validated connection cannot place calls or send messages. Provider-specific identity, compliance, callback, quota, cost, and approval checks remain separate.

Connect an existing Twilio account

Sign in at Twilio instead of copying an Auth Token. Twilio bills that account directly. Linking is inspection-only here and does not select a sender or enable messaging.

Account not connected

Number action required

Compliance action required

Messaging not enabled

Twilio Connect is not configured in this environment. Manual BYOK and platform-managed setup remain available.

Provider setup help Recover a blocked setup

Connection source

Platform-managedUse the account administered by OrbiLattice; availability and validation are checked separately.

Use my Twilio account (BYOK)Validate and store a workspace-owned Account SID and Auth Token.

Selecting managed credentials changes only the administrative connection source. It does not enable provider actions.

Sanitized operation history

No provider connection operations recorded yet.

Calling and messaging readiness is separate

Administrative validation can confirm credentials and observe a bounded owned-number result. It does not authorize an SMS or call.

Consent and DNC: not proven

Disclosure: not proven

Signed callbacks: not proven

Quota: not proven

Provider cost: not proven

If a provider effect is ever uncertain, reconcile its receipt before retrying.