telephony

To provision a Twilio phone number for SMS and AI calls, configure your Twilio credentials within the environment. The skill persists the owned number and state locally, enabling continuous automated outreach and notifications.

Yes, you can poll inbound SMS messages without a webhook server. The skill directly queries Twilio for incoming messages, allowing automated notifications and verifications without requiring external server infrastructure or endpoint configuration.

Yes, Vapi supports importing an owned Twilio number for higher-quality AI outbound calls. The skill manages this import process and automatically stores the resulting Vapi phone_number_id locally for persistent call-based workflows.

The best way to manage Twilio and Bland.ai credentials is persisting them in a dedicated environment file. The skill stores telephony state and credentials locally, ensuring cross-session continuity for automated outreach and call interactions.

You need Twilio and Bland.ai credentials because Twilio provisions the persistent phone number and handles SMS/MMS, while Bland.ai or Vapi drives the AI outbound calls. Both integrations establish a persistent agent identity for notifications.

You should not use a persistent Twilio number if your automated outreach requires no state continuity between sessions or lacks valid Twilio credentials. The skill relies on persistent local state and active API keys for all telephony operations.