Channels

How to Use OpenClaw for Voice Calls

3 min read

Browse more in Channels.

All channels guides →

This guide shows you how to use OpenClaw for voice calls by wiring the Voice Call channel into your existing Gateway setup. You will see where Voice Call fits among other chat channels and what you need to connect telephony providers like Plivo or Twilio.

By the end, you will know how to route calls into the same agents that already handle your text chat channels.

Setup flow

Prerequisites

  • An existing OpenClaw Gateway deployment configured with at least one agent.
  • Access to a telephony provider account such as Plivo or Twilio that can connect to external webhooks.
  • Network access from your telephony provider to your OpenClaw Gateway so it can deliver Voice Call webhooks.

Steps

  1. 1

    Review supported chat and voice channels

    Start by understanding how Voice Call fits into OpenClaw’s channel model. OpenClaw treats Voice Call as one of many chat channels, all connected through the Gateway, so you can reuse the same routing and agents you already use for text.

    Scan the supported channels list to confirm Voice Call is available alongside your existing platforms.

    text
    *   [BlueBubbles](https://docs.openclaw.ai/channels/bluebubbles) — **Recommended for iMessage**; uses the BlueBubbles macOS server REST API with full feature support (bundled plugin; edit, unsend, effects, reactions, group management — edit currently broken on macOS 26 Tahoe).
    *   [Discord](https://docs.openclaw.ai/channels/discord) — Discord Bot API + Gateway; supports servers, channels, and DMs.
    *   [Feishu](https://docs.openclaw.ai/channels/feishu) — Feishu/Lark bot via WebSocket (bundled plugin).
    *   [Google Chat](https://docs.openclaw.ai/channels/googlechat) — Google Chat API app via HTTP webhook.
    *   [iMessage (legacy)](https://docs.openclaw.ai/channels/imessage) — Legacy macOS integration via imsg CLI (deprecated, use BlueBubbles for new setups).
    *   [IRC](https://docs.openclaw.ai/channels/irc) — Classic IRC servers; channels + DMs with pairing/allowlist controls.
    *   [LINE](https://docs.openclaw.ai/channels/line) — LINE Messaging API bot (bundled plugin).
    *   [Matrix](https://docs.openclaw.ai/channels/matrix) — Matrix protocol (bundled plugin).
    *   [Mattermost](https://docs.openclaw.ai/channels/mattermost) — Bot API + WebSocket; channels, groups, DMs (bundled plugin).
    *   [Microsoft Teams](https://docs.openclaw.ai/channels/msteams) — Bot Framework; enterprise support (bundled plugin).
    *   [Nextcloud Talk](https://docs.openclaw.ai/channels/nextcloud-talk) — Self-hosted chat via Nextcloud Talk (bundled plugin).
    *   [Nostr](https://docs.openclaw.ai/channels/nostr) — Decentralized DMs via NIP-04 (bundled plugin).
    *   [QQ Bot](https://docs.openclaw.ai/channels/qqbot) — QQ Bot API; private chat, group chat, and rich media (bundled plugin).
    *   [Signal](https://docs.openclaw.ai/channels/signal) — signal-cli; privacy-focused.
    *   [Slack](https://docs.openclaw.ai/channels/slack) — Bolt SDK; workspace apps.
    *   [Synology Chat](https://docs.openclaw.ai/channels/synology-chat) — Synology NAS Chat via outgoing+incoming webhooks (bundled plugin).
    *   [Telegram](https://docs.openclaw.ai/channels/telegram) — Bot API via grammY; supports groups.
    *   [Tlon](https://docs.openclaw.ai/channels/tlon) — Urbit-based messenger (bundled plugin).
    *   [Twitch](https://docs.openclaw.ai/channels/twitch) — Twitch chat via IRC connection (bundled plugin).
    *   [Voice Call](https://docs.openclaw.ai/plugins/voice-call) — Telephony via Plivo or Twilio (plugin, installed separately).
    *   [WebChat](https://docs.openclaw.ai/web/webchat) — Gateway WebChat UI over WebSocket.
    *   [WeChat](https://www.npmjs.com/package/@tencent-weixin/openclaw-weixin) — Tencent iLink Bot plugin via QR login; private chats only.
    *   [WhatsApp](https://docs.openclaw.ai/channels/whatsapp) — Most popular; uses Baileys and requires QR pairing.
    *   [Zalo](https://docs.openclaw.ai/channels/zalo) — Zalo Bot API; Vietnam’s popular messenger (bundled plugin).
    *   [Zalo Personal](https://docs.openclaw.ai/channels/zalouser) — Zalo personal account via QR login (bundled plugin).
  2. 2

    Understand how Voice Call connects through the Gateway

    Voice Call uses the same Gateway that powers your chat channels, so calls route into your agents through a unified entry point. This means you can run Voice Call alongside Telegram, Slack, or WhatsApp and let OpenClaw decide which agent handles which conversation.

    Keep in mind that Voice Call is a plugin installed separately, unlike many bundled chat plugins.

    text
    OpenClaw can talk to you on any chat app you already use. Each channel connects via the Gateway. Text is supported everywhere; media and reactions vary by channel.
    
    *   [Voice Call](https://docs.openclaw.ai/plugins/voice-call) — Telephony via Plivo or Twilio (plugin, installed separately).
  3. 3

    Plan your Voice Call provider integration

    Decide whether you want to connect Plivo or Twilio for telephony, since the Voice Call plugin supports both. Your provider will send call events into the OpenClaw Gateway, where they become channel messages that your agents can respond to.

    Check your provider’s console for webhook configuration so you can point it at your Gateway once the plugin is installed.

    text
    *   [Voice Call](https://docs.openclaw.ai/plugins/voice-call) — Telephony via Plivo or Twilio (plugin, installed separately).
  4. 4

    Run Voice Call alongside other channels

    You can enable Voice Call without disabling your existing chat channels. OpenClaw supports running multiple channels at the same time and routes messages per chat, so a phone call and a Telegram DM can hit the same agent concurrently.

    This is useful when you want a single agent brain that can talk over both voice and text.

    text
    *   Channels can run simultaneously; configure multiple and OpenClaw will route per chat.
    *   Fastest setup is usually **Telegram** (simple bot token). WhatsApp requires QR pairing and stores more state on disk.
  5. 5

    Apply channel routing and security to Voice Call

    Once Voice Call is wired in, you use the same routing and security concepts as other channels. Channel routing decides which agent handles which incoming call, and DM pairing or allowlists protect who can reach your agents.

    Reuse your existing Groups and Security configuration so Voice Call behaves consistently with your chat channels.

    text
    *   Group behavior varies by channel; see [Groups](https://docs.openclaw.ai/channels/groups).
    *   DM pairing and allowlists are enforced for safety; see [Security](https://docs.openclaw.ai/gateway/security).

Troubleshooting

Voice Call events reach the Gateway but do not hit the expected agent or channel.

OpenClaw routes per chat when you configure multiple channels, so misconfigured routing rules can send calls to the wrong place. Review your channel routing and group behavior so Voice Call is mapped to the agent and groups you expect.

bash
*   Channels can run simultaneously; configure multiple and OpenClaw will route per chat.
*   Group behavior varies by channel; see [Groups](https://docs.openclaw.ai/channels/groups).

Voice Call appears connected but callers cannot interact due to pairing or allowlist restrictions.

DM pairing and allowlists apply across channels for safety, which can block new callers if you lock things down too tightly. Adjust your pairing and allowlist configuration under the Gateway security settings so Voice Call callers are allowed to start sessions.

bash
*   DM pairing and allowlists are enforced for safety; see [Security](https://docs.openclaw.ai/gateway/security).

Frequently asked questions

Powered by Mem0

Add persistent memory to OpenClaw

Official Mem0 plugin for OpenClaw keeps context across chats and tools. Smaller prompts, lower cost, better continuity for your agents.

More in Channels