Give Your OpenClaw Agent a Phone Number: SMS, Voice, and the iPhone Problem (2026)
Yesterday on r/openclaw, a builder posted “Unfortunately one of my customers has an iPhone. Is there a way to send SMS?” Earlier in the week r/clawdbot saw two “my agent now has a phone number” posts within a few days of each other. Telegram is the default OpenClaw channel — but enough customers do not use it that builders are wiring SMS, voice, and phone-number routing into their agents. Here is how.
This post walks through the four most common wiring options (Twilio, Vonage/Sinch, Telnyx, WhatsApp Business), the iPhone-friendly path end to end, five CrewClaw templates that plug into phone-number setups out of the box, and the gotchas — A2P 10DLC, voice latency, carrier filtering — that bite people who skip the compliance docs. No fluff, no “agentic SMS revolution” framing. Just the wiring.
Why Telegram Alone Does Not Cut It
Telegram is the OpenClaw default for good reasons — bots are free, setup is five minutes with BotFather, group support is solid, and there is no per-message cost. For internal tooling and dev-facing agents, Telegram is enough. The problem starts the moment your agent has to talk to people who do not already live in Telegram.
- Customer does not have Telegram. Most iPhone users in the US, Canada, UK, and Australia do not have Telegram installed. Asking them to install a new app to talk to your agent is friction you will not win.
- Inbound voice calls. Vending-machine restock, on-call support, contractor dispatch, after-hours triage — these are voice-first use cases. Telegram does not handle inbound phone calls from a regular phone.
- SMS works on every phone. If the device can boot, it can receive SMS. It is the actual lowest common denominator across iOS, Android, dumbphones, satellite phones, and landlines that fall back to TTS readouts.
- A phone number is a trust signal. “Text us at +1-415-555-0142” reads more legitimate to non-technical buyers than “DM @YourBot on Telegram.” You can argue this is irrational, but the conversion data does not care.
Most builders end up with two channels — Telegram for power users and internal use, SMS or WhatsApp for the public-facing surface. The OpenClaw side does not change; you add another channel adapter that listens on a webhook and calls the same agent logic.
Option A: Twilio + Webhook (Most Popular)
Best for: Any English-speaking market — US and Canada in particular. The default pick if you have not picked anything yet.
~$1/mo + $0.01/SMS
US number $1.15/mo. International varies.
30 min
Buy number, set webhook URL, deploy handler.
SMS + Voice
Same number can do both with different webhooks.
Excellent
Reference SDKs in Node, Python, Go, Ruby.
The standard flow has three steps:
- Twilio receives an inbound SMS, fires a POST to your webhook URL with the From, To, and Body fields.
- Your webhook handler (Node/Python on the same box as your OpenClaw agent) hands the message to the agent, gets a reply.
- Handler responds with TwiML, or calls the Twilio REST API with the reply text. SMS goes out.
Twilio is the most popular because the docs are genuinely good and most agent templates already have a Twilio adapter. The downside is price — international SMS gets expensive fast, and the per-minute voice rate is higher than Telnyx. See the Customer Support template for a pre-wired example.
Option B: Vonage or Sinch (Twilio Alternatives)
Best for: EU and APAC traffic where Twilio's international SMS pricing is rough.
Similar to Twilio
Better international rates in EU/SEA.
30-45 min
Webhook flow nearly identical to Twilio.
SMS + Voice
Plus Verify (OTP) APIs out of the box.
Geography
Local numbers in 80+ countries.
If your customer base is mostly in Europe or Southeast Asia, run the numbers — Vonage and Sinch can come in 20-40% cheaper per SMS for those geographies. The integration shape is identical: buy number, set webhook, parse inbound POST, reply via REST. Most OpenClaw adapter packages support both providers with a one-line config change.
Option C: Telnyx (Voice-Quality Focus)
Best for: Any inbound voice use case — receptionists, support hotlines, on-call dispatch.
Lower per-minute
Voice ~30-50% cheaper than Twilio at scale.
45 min
Their console is less polished but functional.
Voice-first
SMS works too, voice is the strength.
Own network
Telnyx operates its own carrier infrastructure.
Telnyx makes sense when voice quality and per-minute price matter — if your agent is taking 200 phone calls a day, the savings vs Twilio voice add up to real money. The trade is a less polished developer experience; the SDKs and docs are functional, not delightful. Pair with the Phone Receptionist template for a starting point.
Option D: WhatsApp Business API (When “Phone Number” Means WhatsApp)
Best for: LATAM, India, EU, and any B2C audience where WhatsApp is the assumed messaging channel.
Free per-msg on opt-in
Conversation fee applies (~$0.005-0.08).
Days
Meta verification + business display name approval.
WhatsApp only
Number can still receive SMS separately.
2B+ users
Default messenger in dozens of countries.
For B2C in LATAM, India, and most of Europe, WhatsApp is the channel — SMS is dead-letter mail by comparison. The integration is via the WhatsApp Business API (through Twilio, Sinch, or 360dialog), not direct from Meta unless you are a large account. Inbound messages hit a webhook, your agent responds via REST, exactly like SMS — but the user opens WhatsApp instead. The CrewClaw WhatsApp Business template ships with the webhook handler and template-message scaffolding already in place.
The iPhone-Friendly Path, End to End
Walking through the exact flow that solves the r/openclaw question — an iPhone customer who does not have Telegram, needs to receive messages from your agent:
- User opts in. Either they text a keyword to your short-link number (“Text JOIN to +1-415-555-0142”) or they enter their phone number into a signup form on your site with an explicit consent checkbox. Save the consent record — you will need it if a carrier ever audits you.
- Webhook delivers to your OpenClaw agent. Twilio posts the inbound message to a URL you control. Your handler — a tiny Express or FastAPI route — extracts the From, To, Body, normalizes them, and passes them as a message event into your OpenClaw agent runtime.
- Agent thinks and responds. Standard OpenClaw flow — the agent reads the message, calls tools, generates a reply. No special branching for SMS vs Telegram; the channel adapter handles outbound routing.
- Reply goes back via Twilio SMS. The handler calls
client.messages.create()with the From (your Twilio number), To (the customer's phone), and Body. The iPhone gets the SMS on the same thread it sent in on. - Optional: voice support. Add a second webhook URL for inbound voice. Answer with TwiML
<Gather input="speech">, hand the transcript to your agent, stream the reply back as TTS via Twilio's<Say>or pipe an LLM TTS provider for better voice quality.
Total wiring time on a fresh OpenClaw project: about 90 minutes if you have done it before, half a day if it is your first time. The OpenClaw agent code does not change — you are bolting on a new outbound and inbound channel, not rewriting the brain.
5 CrewClaw Templates That Pair Well With Phone-Number Wiring
These templates already assume an outside-the-org user as the channel partner. Drop in your Twilio (or Vonage / Telnyx / WhatsApp) credentials and ship.
- Customer Support (Ally) — Inbound support over SMS, escalation to a human via Slack. Most-deployed phone-number template.
- Helpdesk (Fix) — Triage incoming tickets, route to the right queue, send status updates by SMS as the ticket moves.
- Sales Assistant — Qualify inbound leads, book demos, confirm appointments by SMS the day before.
- WhatsApp Business — WhatsApp-native conversations with order updates, FAQ replies, and opt-in marketing flows.
- Phone Receptionist — Voice-first agent that answers your business line, takes messages, books calls, and emails you the transcript.
Browse the full set: crewclaw.com/agents
Cost Math: What You Actually Pay
The per-SMS price looks tiny but volume gets you. Here is the realistic monthly cost across three sizes — Twilio US pricing in 2026, excluding any A2P 10DLC fees.
| Profile | SMS volume | Number cost | SMS cost | Total/mo |
|---|---|---|---|---|
| Hobby | 50/mo | $1.15 | $0.40 | ~$1.50 |
| Solo SaaS | 500/mo | $1.15 | $4.00 | ~$6 |
| Small B2C | 5,000/mo | $1.15 | $40-50 | ~$51 |
Add a $5/mo VPS to run the OpenClaw agent and roughly $3-10/mo in LLM API spend for a low-volume agent (Claude Haiku-class or similar). Even at small-B2C volume, the all-in monthly cost sits under $70 — well below most managed agent-platform subscriptions.
Gotchas Nobody Mentions Until Day 3
- A2P 10DLC registration (US). If you are sending application-to-person SMS to US numbers — and that is what every automated agent does — you must register your brand and each campaign with The Campaign Registry. Unregistered traffic gets throttled and filtered. Budget $4-15/mo plus a one-time brand fee, and expect 1-3 days for approval.
- International roaming surprises. Sending to a UK number from a US Twilio number costs significantly more than US-to-US. Sending to India is cheaper through a local provider than from a US number. If your traffic is international, audit your provider's rate card by destination country before you scale.
- Voice latency kills the conversation. If your LLM round-trip is over 2 seconds, callers think the line dropped and hang up. Use a small fast model for the first acknowledgement (“One moment...”) while a bigger model thinks, or stream TTS so audio starts playing before the full reply is generated.
- Carrier spam filtering on day one. A brand-new Twilio number sending automated traffic from minute one will get flagged. Warm it up — send a few legitimate messages a day for the first week, then ramp. This applies even to compliant registered numbers.
- GDPR consent for EU traffic. Storing a phone number is processing PII. You need a lawful basis (usually explicit consent at signup), a privacy policy that names what you do with the number, and a deletion path. Same applies to UK GDPR, slightly different rules in CA (CCPA) and Brazil (LGPD).
Get a Phone-Ready OpenClaw Agent
CrewClaw ships pre-built agent templates that drop into Twilio, Vonage, Telnyx, or WhatsApp Business. $9 single agent, $19 starter (3 agents), $29 team (5 agents). One-time pricing, no subscription.
FAQ
How do I send SMS to an iPhone with OpenClaw?
iPhones treat SMS exactly like any other phone — there is no special API. You wire a Twilio (or Vonage, Sinch, Telnyx) phone number to your OpenClaw agent, the agent calls the provider's REST API with the customer's number and a message body, and the SMS arrives on the iPhone. iMessage upgrades happen automatically between two Apple devices, but you do not need to think about that as a sender — your provider sends SMS, the carrier delivers it, the iPhone renders it. The only OpenClaw-specific step is adding an outbound channel adapter alongside your Telegram one.
Is it cheaper to use Telegram than Twilio?
By an order of magnitude. Telegram bots are free — you pay zero per message, zero for the bot username, zero for the API. Twilio charges roughly $1/month per US phone number plus about $0.01 per SMS segment (more for MMS, more for international). For a hobby agent that gets 50 messages a month, Twilio runs about $1.50/month — fine. For a B2C agent with 5,000 messages a month, you are looking at $50+ in SMS costs alone. Telegram stays free at any volume. The reason to use SMS is reachability, not cost.
Can my agent take phone calls, not just SMS?
Yes. Twilio Voice, Telnyx, and Vonage all expose a webhook that fires when an inbound call hits your number. You answer with TwiML (or each provider's equivalent), play TTS audio, capture the caller's speech with built-in speech-to-text, and pass that to your OpenClaw agent. The agent's reply gets streamed back as TTS. The hard part is latency — if your LLM takes 3 seconds to respond, the caller will think the line dropped. Keep the round-trip under 1.5 seconds or use streaming TTS to fill the gap.
What about WhatsApp — is it really a phone number?
Yes and no. WhatsApp Business API requires a real phone number you control, registered through Meta's verification flow. Once registered, that number becomes a WhatsApp identity — it can also still receive SMS, but most B2C senders use it exclusively for WhatsApp. The big win is cost: opt-in user-initiated conversations in WhatsApp are free per message (you pay a flat conversation fee). The big friction is verification — Meta can take days to approve, and they want a business display name and a use-case description.
Will my number get banned for sending too many automated messages?
Possibly, especially in the US. US carriers run A2P 10DLC — Application-to-Person 10-Digit-Long-Code — which requires you to register your business, register each campaign (use-case), and label messages. Unregistered numbers get throttled to a few messages per day and start getting filtered as spam. Registration is a $4-15/mo line item plus a one-time brand registration fee. International numbers have different rules; the EU is friendlier on volume but stricter on consent under GDPR. Read your provider's compliance docs before your first marketing campaign.
Deploy a Ready-Made AI Agent
Skip the setup. Pick a template and deploy in 60 seconds.
Or Get the Whole Team
Multi-agent crews pre-configured to work together. Cheaper than buying singles.
Automate Content Pipeline: 4-Agent SEO + Writing + Social Team
Automate content pipeline end-to-end with 4 AI agents that handle keyword research, drafting, scheduling, and social distribution for solo founders and lean teams.
AI DevOps Automation: 3-Agent CI/CD, Code Review, and QA Team
AI DevOps automation team that runs CI/CD monitoring, PR review, and regression testing on autopilot for solo developers and small startup engineering teams.