voice-call

To start a voice call, the Eggent voice-call plugin must be enabled and configured with provider credentials and a fromNumber under plugins.entries.voice-call.config. You can then initiate calls through Twilio, Telnyx, Plivo, or mock backends.

Yes, you can use the mock backend to test voice call workflows. The voice-call plugin supports mock backends alongside Twilio, Telnyx, and Plivo, allowing you to simulate sales, support, and notification workflows without real telephony costs.

Before initiating a voice call, you need to enable the voice-call plugin and configure it under plugins.entries.voice-call.config with your chosen provider's credentials and a valid fromNumber. This setup is required for Twilio, Telnyx, Plivo, and mock backends.

Yes, the voice-call plugin supports call status inspection and control flows. You can monitor active calls and manage continuing or ending calls consistently across Twilio, Telnyx, Plivo, and mock backends for various workflows.

The best way to manage automated sales and support voice calls is using the Eggent voice-call plugin, which provides unified controls for initiating, continuing, and ending calls across Twilio, Telnyx, Plivo, or mock backends with consistent commands.

Voice calls fail when the plugin is not properly configured. Ensure the voice-call plugin is enabled and that plugins.entries.voice-call.config contains valid provider credentials and a fromNumber for your selected Twilio, Telnyx, Plivo, or mock backend.