My Phone Just Became a Real Personal Assistant#

I've spent the last week calling my AI assistant from my car.

Not texting it. Not opening an app. Calling it, out loud, like it's a coworker with a phone number.

"What's on my calendar today?" — it reads me my day. "Show me my open tickets" — it walks through my Jira queue. All hands-free, at 65 mph on the freeway.

It sounds obvious. It took surprisingly long for anyone to build it this way.

The Problem: Access, Not Intelligence#

Every AI assistant I've tried is a chat window with extra steps.

Siri sets timers. ChatGPT answers questions but doesn't know what's on my calendar or what tickets are assigned to me. The "assistant" part always stops at the boundary of my actual work tools.

And even when an agent can do real things, it usually lives on my laptop. I'm not at my laptop. I'm driving, walking the dog, standing in a grocery line with both hands full.

So the gap for me was never the model. It was access.

ClawdTalk Is a Phone Number for Your Agent#

ClawdTalk, built by the Telnyx team, fixes the access problem — and it does it with the oldest universal API we have: the phone call.

The setup gives your OpenClaw agent a real phone number through Telnyx. You dial it. Your call becomes a voice session with your agent.

Because the agent already has skills attached, the call is actually useful:

• Calendar reminders, spoken to you
• Jira updates while you're away from your desk
• Web search results read back mid-walk

SMS support is coming soon, per the team.

My Honest Take#

The voice part is the least interesting feature.

Voice interfaces have been "almost there" for a decade. What makes this setup useful is that the thing on the other end of the line can do things. The phone call is just a transport layer. The product is the skills.

That's also why most voice assistants disappointed me and this one doesn't. They were voice front-ends with nothing behind them. This is an agent that already works, with a phone bolted onto it.

Setting It Up#

Three steps. Install the client, load the skills, prime the prompt.

1. Install the ClawdTalk client.

Grab it from GitHub — the repo is team-telnyx/clawdtalk-client — and follow the README to connect it to a Telnyx number. Telnyx handles the telephony layer, which is why the call quality doesn't feel like a 2005 conference bridge.

2. Load the skills.

The phone only matters if the agent can do something when you call. Pull these from the OpenClaw skills repo:

• Calendar skill (Google Calendar or Outlook both work)
• Jira skill
• Web search skill

Skip this step and you're just calling a chatbot with extra latency. The skills are the whole point.

3. Tell your agent how to behave on calls.

A short prompt does most of the work here:

You are available via phone. When I call, greet me and ask how I can help.

For calendar queries: "What's on my calendar today?"
For Jira updates: "Show me my open tickets"
For web search: "Search for latest news on AI agents"

Then dial your number. That's the entire interaction model.

What I Actually Use It For#

Nothing flashy. That's the point.

• Morning commute: "What's on my calendar today?" before I've touched a keyboard.
• Pre-standup: "Show me my open tickets" while the coffee brews.
• Walks: "Search for latest news on AI agents" — turns dead time into a briefing.

Every one of these used to require me to stop, pull out my phone, open an app, and type. Now they're one spoken sentence.

Where It Falls Short#

Full honesty, because you'd find out anyway:

Voice is slower than reading for dense stuff. I don't ask it to walk through a 40-line ticket. Quick status queries? Great. Deep work? Still a screen.

No SMS yet. The team says it's coming soon, and when it lands, one-off queries get even cheaper — text "my tickets" from a meeting and get an answer.

It's only as good as the skills you attach. This is a feature, not a bug, but it means setup order matters. Skills first, phone second.

The Pattern Worth Stealing#

Step back from the phone call and look at the move itself: take an agent that can already do things, then bolt on whatever access point fits your day.

Phone today. SMS soon. The same agent could sit behind a Slack bot or an email address tomorrow. The access layer is swappable. The skills are the durable part.

For mobile-first people — anyone whose workday happens between places, not at a desk — the phone number is the access layer that finally makes sense. Every phone on earth can make a call. No app store required.

If you're wiring up agents like this — skills, prompts, integrations, the unglamorous plumbing — we collect working setups and the config details behind them at papayaclaw.com. Come steal ours.