voice-call

• You want an AI agent to autonomously place outbound voice calls to users or external parties.
• You need to send spoken notifications, alerts, or messages programmatically (e.g. appointment reminders, incident alerts).
• You are building or testing voice-call automation and want a mock provider that requires no real network or credentials.
• You are already running OpenClaw and want to extend it with telephony capabilities using Twilio, Telnyx, or Plivo.

• You are not using the OpenClaw platform — this skill requires the OpenClaw voice-call plugin to be installed and enabled.
• You need inbound call handling or IVR flows; this skill focuses on agent-initiated outbound calls.
• You require a telephony provider not supported by the plugin (Twilio, Telnyx, Plivo, or mock are the only supported options).

Supports Twilio, Telnyx, and Plivo as telephony backends, each configurable with provider-specific credentials. Switch providers by changing the provider field in your plugin config — no code changes required.

Agents can initiate calls, continue conversations, speak messages mid-call, check call status, and explicitly end calls using dedicated actions (initiate_call, continue_call, speak_to_user, get_status, end_call).

Set provider: "mock" to run voice-call workflows entirely offline with no network requests or real credentials. Ideal for testing agent logic before connecting a live telephony provider.

Trigger calls directly from the command line with openclaw voicecall call or integrate seamlessly into agent workflows using the voice_call tool, giving flexibility for both manual and automated usage.

An agent detects a critical system event and uses initiate_call to immediately phone an on-call engineer with a spoken alert, without any human having to place the call manually.

A scheduling agent calls a list of recipients before their appointments, speaking a personalized reminder message and ending the call cleanly — all orchestrated through the voice_call tool.

Developers configure provider: "mock" to simulate the full call lifecycle during CI or local testing without incurring telephony costs or requiring real provider credentials.