home / skills / openclaw / openclaw / voice-call

voice-call skill

safe

This skill helps you start and manage voice calls across providers using the OpenClaw voice-call plugin for quick, hands-free communication.

This is most likely a fork of the voiceskill123 skill from openclaw

npx playbooks add skill openclaw/openclaw --skill voice-call

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.1 KB

---
name: voice-call
description: Start voice calls via the OpenClaw voice-call plugin.
metadata:
  {
    "openclaw":
      {
        "emoji": "📞",
        "skillKey": "voice-call",
        "requires": { "config": ["plugins.entries.voice-call.enabled"] },
      },
  }
---

# Voice Call

Use the voice-call plugin to start or inspect calls (Twilio, Telnyx, Plivo, or mock).

## CLI

```bash
openclaw voicecall call --to "+15555550123" --message "Hello from OpenClaw"
openclaw voicecall status --call-id <id>
```

## Tool

Use `voice_call` for agent-initiated calls.

Actions:

- `initiate_call` (message, to?, mode?)
- `continue_call` (callId, message)
- `speak_to_user` (callId, message)
- `end_call` (callId)
- `get_status` (callId)

Notes:

- Requires the voice-call plugin to be enabled.
- Plugin config lives under `plugins.entries.voice-call.config`.
- Twilio config: `provider: "twilio"` + `twilio.accountSid/authToken` + `fromNumber`.
- Telnyx config: `provider: "telnyx"` + `telnyx.apiKey/connectionId` + `fromNumber`.
- Plivo config: `provider: "plivo"` + `plivo.authId/authToken` + `fromNumber`.
- Dev fallback: `provider: "mock"` (no network).

Overview

This skill lets your AI assistant start and manage voice calls using the OpenClaw voice-call plugin. It supports Twilio, Telnyx, Plivo, or a mock provider for development. Use it to initiate outbound calls, speak messages during a call, check call status, and end calls programmatically or from the CLI.

How this skill works

The skill wraps the voice-call plugin actions so the agent can initiate_call, continue_call, speak_to_user, end_call, and get_status. Configuration is read from plugins.entries.voice-call.config and must include provider-specific credentials and a fromNumber. In dev, set provider to mock to avoid network calls.

When to use it

Place automated outbound calls to users for alerts, reminders, or confirmations.
Integrate voice interactions into workflows where spoken responses are required.
Test voice flows locally using the mock provider before deploying.
Check the live status of a call from an agent or automation.
Programmatically end or continue an active call from the assistant.

Best practices

Enable the voice-call plugin and store credentials securely in the plugin config.
Validate provider fields: Twilio needs accountSid/authToken, Telnyx needs apiKey/connectionId, Plivo needs authId/authToken.
Use the mock provider for development to avoid using real credits or phone numbers.
Provide clear, short messages for spoken content to improve call clarity and user experience.
Check call status after initiating to handle failures or retries programmatically.

Example use cases

Send an appointment reminder: initiate_call with message and the recipient number.
Two-way support escalation: agent initiates a call, then uses speak_to_user to guide the user during the call.
Automated alerting: monitoring system triggers an initiate_call with an urgent message to on-call staff.
Interactive surveys: continue_call to play follow-up prompts during an ongoing session.
Development testing: set provider to mock to simulate calls without network activity.

FAQ

What configuration is required to use a real provider?

Populate plugins.entries.voice-call.config with provider and required credentials: Twilio (accountSid, authToken, fromNumber), Telnyx (apiKey, connectionId, fromNumber), or Plivo (authId, authToken, fromNumber).

How do I test without sending real calls?

Set provider to mock in the plugin config. The mock provider simulates calls locally with no network usage.