voice-call

Programmatic voice call automation requires configuring provider credentials for Twilio, Telnyx, or Plivo, then passing a valid destination phone number and message payload to initiate outbound dialing and manage call lifecycle.

Yes, the voice call management functionality includes status checking capabilities, allowing your automated communication workflows to monitor active calls, verify connection states, and programmatically terminate calls when needed.

Yes, Plivo is fully supported alongside Twilio, Telnyx, and a mock provider for testing. You must supply specific provider configurations for your chosen telephony platform to successfully route and manage outbound calls.

Before initiating outbound telephony calls, you must configure a supported telephony provider (Twilio, Telnyx, or Plivo) and possess a valid destination phone number. Specific provider credentials and configurations are required to authenticate and route calls.

You can programmatically terminate active voice calls using the call management termination command. This enables automated communication workflows to end ongoing calls when conversations complete or specific duration thresholds are met.

A mock provider enables testing automated voice call workflows without incurring telephony costs or placing actual outbound calls, simulating call initiation, status checking, and termination behaviors for development and integration validation purposes.