ClawdTalk

What is ClawdTalk?

ClawdTalk is a voice-calling layer for your existing “Clawdbot” (OpenClaw) that lets a bot handle phone calls instead of only text. Your bot continues to receive and send structured messages, while ClawdTalk adds speech-to-text, text-to-speech, and two-way calling so callers can speak and hear spoken replies.

The core purpose is to connect your bot to real phone calls: you install the skill, verify a number, and then call your Clawdbot like a phone line. Calls can include PIN protection, and the system is described as using a persistent outbound WebSocket connection rather than requiring a publicly exposed gateway.

Key Features

• Two-way calling (bot-to-phone and phone-to-bot): Call your bot from a phone number or ask your bot “call me”; both directions work out of the box.
• Speech-to-text with transcripts: The caller’s speech is transcribed and the transcript is used as the bot’s text input.
• Natural-sounding text-to-speech (Telnyx NaturalHD): Voice output is generated with “natural-sounding” text-to-speech (listed as Telnyx voices), aiming for clear, human-like audio.
• Server-side PIN protection: Set a PIN to reject calls that don’t present the required PIN; the caller validation is enforced server-side.
• WebSocket-based private connection: ClawdTalk uses a persistent outbound WebSocket connection so your bot does not need a publicly exposed gateway; it’s intended to work behind NAT and firewalls.
• HD voice support: Calls to the bot are described as supporting HD Voice using an AMR-WB codec (wideband quality).

How to Use ClawdTalk

1. Connect your Clawdbot (OpenClaw). ClawdTalk positions itself as the voice layer that sits alongside your bot.
2. Install the ClawdTalk skill and verify your number (the site describes this as part of the setup).
3. (Recommended) Configure PIN protection. During sign-up, you establish the PIN and set call access rules.
4. Start calling your bot. Use the provided phone number to call your Clawdbot, or use a “call me” flow triggered by your bot.
5. Observe call transcripts and bot responses. The bot receives call events (including the caller’s text) and sends back a text response that is spoken to the caller.

Use Cases

• DevOps / incident response calls: A bot can translate a command from a caller into an action (e.g., “roll back to the last stable release and notify the team”) and then read back the result in the same call.
• Personal assistant reminders and info lookup: Users can ask for time-based or personal data (e.g., reading a calendar or sleep score) and receive a spoken summary.
• Shopping and checkout assistance: Call your bot to add items to a grocery order and confirm totals or delivery timing.
• Smart home control: Ask the bot to set thermostat targets, turn lights on/off, and lock doors; the bot responds with confirmations.
• Team workflows that currently span multiple chat tools: The site contrasts “without” ClawdTalk (messages spread across multiple apps) with a single call workflow that can deliver a structured response.

FAQ

What does ClawdTalk add to my bot? ClawdTalk adds voice calling capabilities—speech-to-text, text-to-speech, and two-way phone calling—while your bot continues handling the underlying text interactions.

Do I need to expose my bot to the public internet? The site describes using a persistent outbound WebSocket connection to keep the bot private and avoid needing a publicly exposed gateway.

Can calls be restricted to authorized callers? Yes. ClawdTalk supports PIN protection, with server-side enforcement to reject calls without the required PIN.

Will callers get transcripts? The described call flow includes reading the transcript and using the transcription as the bot’s input; “full transcripts” are referenced in the plan details.

Is there an option for my own phone number? The pricing section states that you can “order your own number,” though exact availability depends on the chosen plan.

Alternatives

• Text-only bot frameworks (no phone integration): If your goal is primarily chat-based automation (e.g., Slack/Telegram-style bots), text-only platforms avoid telephony and focus on message-driven workflows.
• Call/SIP-to-webhook voice gateways: Instead of a dedicated “bot voice layer,” teams can route inbound/outbound calls to webhooks or application servers, then implement transcription and TTS themselves.
• Speech-to-text + text-to-speech APIs combined with telephony: Another approach is building a custom phone calling app using separate STT/TTS and a telephony provider, giving flexibility but requiring more integration work.
• Unified contact center voice automation: For organizations looking for broader call-center features (routing, reporting, agent assist), contact-center automation tools can offer voice workflows beyond a developer-centric “bot voice” integration.