twilio-setup

To configure Twilio voice call webhooks, you must set the VoiceUrl and StatusCallback to your assistant's public ingress endpoints, ensuring inbound call routing and status events reach your system.

Yes, Twilio setup stores your auth token securely as a credential rather than in chat plaintext. Non-secret values like the Account SID are collected normally, but sensitive authentication data is protected in secure credential storage.

Yes, you can use an existing phone number for Twilio voice routing. The setup supports selecting an existing trial number, purchasing a new voice-enabled local number, or manually entering a number you already own to connect to your assistant.

To connect Twilio to an assistant behind a public ingress, you need your Twilio Account SID, an auth token credential, and a voice-enabled incoming phone number. The setup verifies public ingress behavior and updates webhook routing to your assistant endpoints.

Phone number provisioning for Twilio voice calls works by letting you search for and purchase a new voice-enabled local number, select an existing trial number, or manually enter a number you already own to establish your inbound call routing.

Twilio status callbacks fail to reach your assistant if the StatusCallback URL is not correctly set to your public ingress endpoint or if the managed tunnel behavior is not properly verified. The setup process ensures these webhook URLs are correctly configured to route events.