claude whatsapp
By Beam team · Updated
Claude on SMS or WhatsApp: What's Official?
Anthropic has shipped real iMessage support for Claude three ways. SMS and WhatsApp have not shipped. Here's what each channel actually needs.
Beam is an independent messaging platform, not an Anthropic or Apple product.
Can You Actually Text Claude Over WhatsApp Right Now?
TL;DR: Anthropic has shipped real, official texting support for exactly one channel, iMessage, through three separate surfaces: a draft and hand off action in the Claude iPhone app, an Anthropic verified Claude Desktop extension, and a research preview Channels plugin for Claude Code. Neither SMS nor WhatsApp has an official two way route; WhatsApp gets the same draft and hand off treatment as any other app, and the one SMS toggle that exists ships off by default because it can be spoofed. If you want a number anyone can text and get a real reply from, you need a bridge.
We get asked this almost every week by someone who read a post, tried something on their phone, and got confused when it did not work as described. Short answer: Claude texts back over iMessage today, officially, in three shapes depending on where you set it up. SMS and WhatsApp are not on that list. Below is what each of those three surfaces actually does, and what you need to wire up if a contact's phone is not an iPhone.
Not in the way the question usually means it. Anthropic's own support article on the iPhone and iPad app describes one messaging action, deliberately generic across apps: "Draft and send messages through the Messages app or any messaging platform like WhatsApp, Slack, or Messenger" (support.claude.com: use Claude with iOS apps). Read past the verb "send," though, and the same article narrows it: Claude "does not read existing messages or emails, only creates new content," and has no direct access to your contacts. In practice the action opens WhatsApp with a draft typed in, and you still pick the recipient and tap send.
That is a real, useful feature if you want help wording a message. It is not a channel someone else can message and get an answer from; there is no inbound side to it. If a customer sends your business a WhatsApp message today, nothing Anthropic ships will read it, let alone reply.
We have not found an official Anthropic WhatsApp integration anywhere in the docs, the connector directory, or the Claude Code plugin list, and none of the three sources behind this piece mention one. That absence is the actual news here. There is no first party path yet for a customer to text your WhatsApp number and get a Claude reply, from Anthropic or from a bridge. More on what that means near the end.
Does Claude Have Any Official SMS Number?
No, and the one place SMS shows up at all is easy to misread as support. Claude Code's Channels feature is a research preview that lets an MCP plugin push events into a running terminal session, and Anthropic ships three default plugins: Telegram, Discord, and iMessage (code.claude.com/docs/en/channels). The iMessage plugin reads your Mac's Messages database directly and sends replies through AppleScript, and it technically shares that database with regular green bubble SMS, since the Messages app stores both in the same place.
That plugin has a setting called IMESSAGE_ALLOW_SMS, and its README is specific about why it defaults to off: "SMS sender IDs are spoofable, a forged SMS from your own number would otherwise bypass access control" (github.com/anthropics/claude-plugins-official, imessage plugin README). In plain terms, anyone can fake who an SMS appears to come from, so a stranger could spoof your own number and talk to your own session. Anthropic's answer was to ship the SMS path off, not to build a trusted SMS channel, which is the opposite of an endorsement.
So the honest answer: no dedicated SMS number, no supported SMS inbox, and the one place SMS touches an official plugin is a flag that exists specifically to be left alone.
What Has Anthropic Actually Shipped for iMessage?
This is the part most posts get wrong by treating "Claude and iMessage" as one feature. It is three, built for different jobs, and knowing which one you are reading about saves confusion.
The first is the iPhone app action above: draft, preview, hand off to Messages, tap send yourself. No reading, no autonomous reply, works the same for iMessage as it does for WhatsApp.
The second is a Claude Desktop extension called Read and Send iMessages. It is listed as Anthropic verified and made by Anthropic, shipped in March 2026, and is macOS only because it uses the same Apple automation features the Channels plugin relies on (claude.com/connectors/read-and-send-imessages). It gives Claude Desktop four tools, send_imessage, search_contacts, read_imessages, and get_unread_imessages, so you can ask it to summarize what you missed or draft and send a reply from a desktop chat. This one genuinely reads and sends, but it is tied to whichever Apple ID is signed into Messages on that Mac. It manages your own conversations, not a shared number other people text in on.
The third is the Channels iMessage plugin covered above: also two way, but built for texting yourself, or an allowlisted contact, while whichever Claude Code session is open on that Mac responds through the same chat.db and AppleScript mechanism. Self chat bypasses the access list automatically; everyone else is added by hand. Because it is a research preview, the flags that control it do not even show up in claude --help yet.
All three are real, and all three are iMessage specific. None is a business texting line, and none covers SMS or WhatsApp as anything beyond what the first one does: draft now, send yourself, read nothing back.
How Do the Three Official Surfaces Compare?
| Surface | Channel | What it needs | What it actually does | What it does not do |
|---|---|---|---|---|
| Claude iPhone app | iMessage, WhatsApp, Slack, Messenger (same action for all) | An iPhone, the Claude app | Drafts a message and hands it to the app you pick | Does not read replies, does not run without you tapping send |
| Claude Desktop connector | iMessage only | A Mac, Claude Desktop, the connector enabled | Reads and sends iMessages tied to that Mac's signed in Apple ID | Does not cover a shared number, does not cover SMS or WhatsApp |
| Claude Code Channels plugin | iMessage (SMS toggle exists, off by default) | A Mac, Bun, Full Disk Access, the --channels flag |
Two way chat bridge; self chat works immediately | Preview only, one person's Mac has to stay running, others need allowlisting |
| Telegram and Discord plugins | Telegram, Discord | Same Channels setup as iMessage | Proves Anthropic already ships two way bridges | Still not SMS or WhatsApp |
That last row matters. Anthropic already ships two working bridges for other platforms, so SMS and WhatsApp are not missing because the pattern is hard. They are missing because nobody has shipped that specific plugin yet. Treat any claim otherwise as outdated or wrong.
Diagram: three lanes labeled iPhone app, Desktop connector, and Code Channels plugin, all feeding into a single box labeled "iMessage only." Below that box, two separate boxes labeled SMS and WhatsApp sit outside the lanes with a dashed border and the label "no official two way route," with an arrow pointing from both boxes to a smaller box labeled "needs a bridge."
So What Do You Actually Need for Real SMS or WhatsApp Style Reach?
Here is the actual gap, and it splits in two depending on which channel you mean.
For SMS, the gap has a real answer: a bridge. We run Claude iMessage to connect a Claude client to a real phone line through Beam, and that line picks whichever channel a recipient can actually receive: iMessage for an eligible iPhone, RCS for an Android phone whose carrier supports it, SMS everywhere else. An agency owner connects a Claude client to a Beam workspace through Developer access, using a bearer authenticated connection, and once that connection has sending permission and the workspace has an active line, Claude can read an inbound thread and reply through it, whichever of those three channels carried the message. The recipient never installs anything. They text a saved number like they would text anyone else.
For WhatsApp, we will not overstate this: there is no equivalent bridge today, from Anthropic or from us. Beam connects iMessage, RCS and SMS to Claude. It does not connect WhatsApp. If a workflow genuinely requires a customer on WhatsApp specifically, nothing ships that cleanly yet, and anyone telling you otherwise is either describing the draft and hand off action, which does not read replies, or something unverified. If the real requirement is "a contact can text a number and a Claude powered agent answers," and WhatsApp is not a hard requirement, the SMS and iMessage bridge above answers that same need.
Worth repeating plainly: Beam is an independent messaging platform, not an Anthropic or Apple product. It connects to Claude through the workspace integration above, and nothing about that changes how Claude's own apps and extensions behave on their own.
How Do You Set Up a Working Claude Texting Bridge, Step by Step?
Use this order. Skipping ahead to a test message before permissions and a line are in place is the most common way this breaks on day one.
- Decide whether you need SMS reach at all, or whether iMessage alone covers your audience. If everyone you reach carries an iPhone, the Desktop connector or Channels plugin above may be enough.
- In Beam, open Settings, then Developer access, then MCP and API. Name the connection and grant permissions deliberately: sending and automation each require an explicit grant, and the token cannot be shown again once you leave the screen.
- Point your Claude client at that token: a bearer authenticated connection for Claude Code, or a local stdio bridge script for a desktop client that supports one.
- Before granting anything further, ask the client to read back the workspace name and confirm it matches what you expect.
- Confirm the workspace has an active assigned line. A token alone does not activate a sending number.
- Send a real test from a phone you do not control to a number you know lacks iMessage, so the test exercises the SMS fallback, not blue bubble delivery again.
- Check the message status inside Beam rather than a confirmation line inside Claude. Accepted is not delivered, and delivered is not read.
A single successful test proves less than it feels like it proves. Before you hand a number to anyone else, run this once:
Before calling a Claude texting setup reliable:
- Confirmed which channel carried each recent test message, not assumed from the phone used
- Tested a phone with no iMessage and, separately, one with no RCS, not just your own iPhone
- Confirmed Claude's reply lands in the same thread as the inbound message on both tests
- Checked delivery status directly, not a "sent" message inside Claude
- Written down which parts are official Anthropic surfaces and which are bridged, so support knows where to look later
That last line matters more than it looks. When something breaks, the first question is always whether it is an Anthropic limit or a bridge issue, and teams that cannot answer that quickly waste the first part of every support call finding out.
So Which Claude Texting Claims Should You Actually Trust?
Check any tutorial promising a quick WhatsApp bot or a hidden SMS trick against the three real surfaces above: the iPhone draft and hand off action, the Desktop connector, and the Channels research preview plugin. If a claim does not map onto one of those, or onto a bridge explicit about which channels it covers, treat it as unverified. For a plain walkthrough built for someone who has never touched a developer setting, see our guide on texting Claude as a non technical person. If your audience leans Android, our breakdown of Claude's Android SMS fallback covers the same channel priority from the other device's side. And for the bridge side of this same setup in more technical detail, see beamtexting.com/imessage-api.
Before you connect
What do teams ask before they connect?
Can I text Claude over WhatsApp today the way I'd text a business?
Not through anything Anthropic has shipped. The Claude iPhone app can draft a WhatsApp message and hand it to the WhatsApp app for you to send, the same as it does for Slack or Messenger, but it does not read a WhatsApp reply or run as something a customer can message and get an automatic answer from. If you need a number people can message and get a real reply from, that has to come from a bridge, and right now that kind of bridge covers iMessage, RCS and SMS, not WhatsApp.
Does Claude have its own SMS number?
No. The closest thing is a setting inside the iMessage plugin for Claude Code's research preview Channels feature, called IMESSAGE_ALLOW_SMS, and it ships turned off by default because SMS sender IDs can be spoofed, which would let anyone fake a message from your own number and slip past the access control. That is not a supported general purpose SMS setup, it is an opt in risk a developer can choose to accept on their own Mac.
How much does a Claude texting bridge cost, and how long does setup take?
Beam does not publish prices on this page, text our team directly for a quote that matches your use case. Setup time is the short part: creating a connection token and pointing a Claude client at it takes minutes. What takes longer is confirming the workspace has an active line and testing a real SMS fallback, rather than trusting a sent message inside Claude. Budget an afternoon for that full pass.
Do I need A2P 10DLC registration to text Claude through a bridge?
It depends on the channel the message actually travels over, not on Claude. iMessage and RCS are not subject to the carrier A2P 10DLC process. Plain SMS, the fallback channel that covers a recipient with neither of those, still falls under the applicable carrier A2P rules for the number type involved, and normal consent and opt out rules apply no matter which channel ends up carrying a given message.
Our team is not technical. Can they just text Claude without installing anything?
Yes, as long as someone has already set up the receiving end. The people texting in never install anything or open Claude directly, they text a saved number the way they would text anyone else. One of our own clients put it plainly on a call: their team could not handle an AI interface, they just needed to know if people could text it instead. That is exactly what a bridge is for. The setup work sits in the one time connection step, not in how anyone uses it afterward.
Keep exploring
Which guides go deeper?
Where do these facts come from?
Checked November 2026.