Can Claude Send Text Messages? Who Sends Decides the Rules

Updated 19 min read How we research

TL;DR: You can watch Claude send text messages today, and the three paths are not interchangeable. On iOS and Android, Anthropic’s help pages say Claude drafts the message and pre-fills it in your messaging app, you tap send, and Claude does not read existing messages or emails, only creates new content. On macOS there is a real send. Anthropic’s own Read and Send iMessages connector, added in March 2026, exposes send_imessage, read_imessages, get_unread_imessages and search_contacts, drives the Messages app through macOS automation, requires explicit macOS permission prompts, and states plainly that it is not affiliated with or endorsed by Apple. Through the API, Claude still never sends anything itself. Anthropic documents that client tools run in your application, that Claude responds with stop_reason tool_use, and that your code runs the operation and sends back a tool_result. That split is the whole buying decision, because CTIA’s Messaging Principles and Best Practices classify traffic by who the sender is rather than by which app sent it. If the sender is a business, an organization, or an individual acting on behalf of one, the messaging is Non-Consumer, and CTIA states that automation used in whole or in part by a Non-Consumer to facilitate messaging is not typical Consumer operation. The Consumer attributes CTIA publishes run to 15 to 60 messages a minute, 1,000 a day, one telephone number per Consumer, 100 recipients per message, a one to one ratio of outgoing to incoming, and 25 repetitive messages, and a footnote says that clearing those numbers still does not make a business sender a Consumer. So pick the number before you pick the integration. A personal thread has nowhere to put the seven opt-in details CTIA tells senders to retain, and no way to produce them a year later.

Claude Can Send Text Messages Three Different Ways

Somebody on your team has already tried it. They asked Claude for a follow-up text after a rough call, liked what came back, pasted it into their phone and sent it, and then asked the obvious next question, which is whether the whole desk could work that way. That is where this stops being a question about the model. It becomes a question about your phone system.

There are three live paths and they differ in one specific way. Not quality. Not speed. What separates them is which telephone number the message leaves from and who owns that number, which sounds like a detail and turns out to decide the opt-out, the record, the deliverability and whether a second rep can ever pick up the thread.

  • The mobile apps. Claude writes the message and hands it to your phone’s messaging app. Your thumb sends it, from your personal number.
  • The macOS connector. Claude operates the Messages app on your Mac and sends without you touching the keyboard, still from your personal Apple identity.
  • The API or an automation layer. Claude decides and drafts. Separate code you control sends the message from a business number that is registered to send it.

Those are three different senders wearing one familiar name. Everything downstream, the opt-out, the record, the deliverability, the thing you hand a reviewer eighteen months from now, follows from which one a rep used. Work the paths in order.

On Your Phone, Claude Drafts the Text Message and You Send It

Start with the version most reps meet first. Anthropic’s help article for iOS says Claude can draft and send messages through the Messages app or any messaging platform such as WhatsApp, Slack or Messenger. Read the steps underneath and the word send does a lot of quiet work. You ask Claude to draft. Claude prepares a preview. You tap the message card, which opens Messages with the content already filled in. You review it, change what you want, and send it the normal way.

The Android article describes the same shape for your default messaging app and third-party apps. Both pages say no permission is needed, because the hand-off runs on the device’s built-in sharing system. Both pages also carry the same boundary. Claude does not read existing messages or emails, only creates new content.

So what did you actually buy here? A faster first draft. Nothing else moved.

That is worth saying out loud, because the demo is genuinely good and the conclusion people draw from it is wrong. The rep still opens the thread, still reads what Claude wrote, still decides whether the customer will take it that way, and still presses send, which means every constraint that was already on the rep is still on the rep. There is no queue, no list, no schedule, no retry, no suppression check. One rep, one message, one thumb. If the pitch inside your company is that this frees the team from texting, that is not what the demo showed and it is not what the documentation says.

Useful, though, and worth keeping for what it is. A rep who stalls on wording after a rough call, opens a thread, types two words, deletes them and goes to get coffee instead now has a draft in front of them in seconds, which removes the pause rather than the work. That is a real fix for a real behavior and it costs nothing to allow.

Watch Claude Send Text Messages From a Mac

Now the part that changes the question, because this is where the demo stops being a demo.

Anthropic publishes a connector called Read and Send iMessages, made by Anthropic and added in March 2026. It exposes four tools: send_imessage, search_contacts, read_imessages and get_unread_imessages. It works by using macOS automation features to interact with the Messages app, and it requires explicit permission through macOS security prompts before it touches Messages or Contacts. The listing also says it is not affiliated with or endorsed by Apple.

Read that tool list again. Send, search contacts, read, and read unread. What does that combination give you that the phone apps do not? A loop. Claude can look up a contact, send, read what came back and send again without a person in the middle, and that is a different product from the one on your phone.

Two details in that description are load-bearing and most write-ups skip both.

First, it drives the Messages app rather than calling a messaging API, so whatever identity that Mac is signed in with is the identity on every message it sends, and whatever the Messages app can do on that one machine is the hard ceiling on the whole arrangement.

Second, Anthropic states that it is not affiliated with or endorsed by Apple. An automation that operates a consumer app is not the same thing as a supported business messaging channel, and the connector page does not pretend otherwise, which is more candour than most write-ups about it manage.

Here is the failure mode, and notice that it is not a legal abstraction. Say a rep connects it on a Friday, texts nine customers from their own number over the weekend and books two meetings, which is a good weekend by any standard. Monday the rep is out. Three of those nine reply. Nobody else can see the thread, because the thread is on a laptop in somebody’s kitchen, which means the manager cannot read it, the CRM has no record that it happened, and the next rep to touch those accounts starts from nothing. That is not a compliance problem yet. That is a hole in the pipeline.

Who Sends the Text Message Decides Which Rules Apply

The compliance problem arrives next, and it does not care which laptop was used.

A translucent glass channel passing through an opening in a thick glass plate, smooth on one side of the plate and finely ribbed on the other, on a pale violet ground

CTIA publishes the Messaging Principles and Best Practices, the document the wireless carriers work from. It sorts all messaging into two buckets, Consumer and Non-Consumer, and the executive summary states the test in one sentence. If the Message Sender is a business, organization, or other entity, or an agent, representative, or other individual acting on behalf of a business, organization, or other entity, the messaging is considered Non-Consumer.

Read the clause about the individual again, because that is the half most teams skip. A rep texting a customer about a renewal is an individual acting on behalf of a business, which is the exact wording, so the traffic is Non-Consumer before anyone asks what it was sent from. The handset does not change that. The Apple ID does not change that. The classification follows the sender and not the device.

CTIA then addresses automation directly, which is unusual and lucky for anyone trying to answer this question. It grants the sensible case first. Some Consumers use automation to help them respond, and it gives the example of an auto-reply that tells a caller the person is busy or driving. That kind of help with composing and sending falls inside typical Consumer operation. Then comes the boundary. Automation used in whole or in part by a Non-Consumer to facilitate messaging is not typical Consumer operation.

That sentence was written before this connector existed and it lands on it exactly. Which case are you in? An assistant that drafts your reply to a friend is the auto-reply case and nobody minds. The same assistant working a customer list on behalf of your employer is the other case, and CTIA draws that line in terms rather than leaving it to interpretation.

One practical note on scope. Those principles are voluntary industry best practices, not a statute, and they say so. They are also what the carriers who deliver your messages use, which makes them the operating rules whatever their legal weight. For the statutory layer, read the four separate rulebooks that govern a marketing text rather than treating carrier policy as law.

The Consumer Thresholds a Sales Desk Blows Past

CTIA also publishes what typical Consumer operation looks like in numbers. These are the attributes it lists.

  • Throughput of 15 to 60 messages per minute. A Consumer typically cannot originate or receive more than about one message per second.
  • Volume of 1,000 per day. Only in unusual cases do Consumers send or receive more than a few hundred in a day, and a Consumer cannot typically send or receive continuously over a long period.
  • One telephone number assigned to or used by a single Consumer.
  • 100 distinct recipients per message. A Consumer typically sends to a limited number of recipients, with ten given as the example.
  • A one to one ratio of outgoing to incoming messages per telephone number, with some latitude either way, because Consumer messages are conversational.
  • 25 repetitive messages. Typical Consumer behavior is not to send essentially or substantially repetitive messages.

Look at the balance line and the repetition line together, because those are the two a sales desk breaks first and neither of them is about volume. A rep working a follow-up list sends many messages and hears back from a few, which is the exact opposite of the one to one ratio CTIA describes as conversational. The same rep sends a near-identical message to forty people, which is the repetition attribute. How much traffic does that take? A quiet Tuesday does it.

Now the part that stops the obvious workaround. CTIA attaches a footnote saying that even where traffic satisfies the throughput, volume and balance numbers consistent with typical consumer operation, it still qualifies as Non-Consumer messaging because it is sent by a Non-Consumer. So throttling does not buy reclassification. Staying under 1,000 a day does not make a business sender a Consumer. The attributes are illustrative and the sender is determinative.

This is the whole reason to read the thresholds at all, and it is the opposite of how most people read them. They are not a speed limit you can drive under. They describe someone you are not.

What a Personal Thread Cannot Record About a Text Message

Set the classification aside for a second and ask the operational question instead. What has to exist on the day somebody asks why a particular contact got a particular text?

Two shallow frosted glass trays on a pale violet ground, the left one empty and the right one holding a loose fan of thin translucent cards

CTIA lists what Message Senders should retain to document opt-in consent, where applicable. The timestamp the consent was acquired. The medium it came through, such as a web form, a paper sign-up or a text keyword. A capture of the experience, meaning the language and the action used to secure it. The specific campaign the opt-in was for. The IP address used to grant it. The Consumer phone number it covers. And the identity of the individual who consented.

Seven items. Where do any of them live in an iMessage thread?

There is no field for the timestamp of consent, because a thread only knows when a message was sent and has no opinion about when permission was given. There is no campaign, because a personal thread has no campaigns. There is no capture of the opt-in language, because the opt-in happened somewhere else entirely and nothing carried it across. The thread holds exactly one of the seven, the phone number, and it holds that one by accident.

CTIA also says an opt-in should not be transferable or assignable and should apply only to the campaigns and the specific Message Sender it was obtained for. A customer who agreed to appointment reminders from your company agreed to those, from that sender. A text from a rep’s personal number is a different sender making a different ask. The registration and delivery mechanics behind that rule are worth reading separately, because they are where most teams first notice something is wrong.

And notice how this failure presents itself, because it does not present as an error. The rep’s tool reports that the message went, the customer may well reply, and every dashboard anyone looks at stays green for as long as nobody asks a specific question. Nothing surfaces until the day somebody asks for the record, and on that day the answer is that there is no record, there is a laptop.

What does that cost you in an ordinary week, before any of the serious scenarios? A rep leaves and takes nine live conversations with them. A manager coaching a struggling rep can read every call and none of the texts, which is half a diagnosis. Two reps text the same customer inside the same hour because neither of them can see the other’s thread. The opt-out somebody sent on Saturday afternoon sits unread in one personal inbox while the rest of the team keeps messaging that contact on Monday.

Build a Claude Text Message Path That Leaves a Record

So build the other path. It is not harder, it is just explicit.

Start from how the Claude API actually works, because it already splits the job the way you need it split. Anthropic’s tool use documentation says client tools run in your application. Claude responds with stop_reason tool_use and one or more tool_use blocks. Your code runs the operation and sends back a tool_result.

Translate that out of the documentation and onto the desk. Claude never sends the text message. Claude asks for a text message to be sent, and something you wrote decides whether to honor the request. That is not a limitation you are working around. That is the seam you want.

So where should the opt-out check live? Not in the prompt, where it is a probability that a model remembered an instruction, but in the few lines of code sitting between the tool_use block and the send, where it is a yes or a no and you can read it in a log afterwards. Same for the business-hours rule, the per-contact frequency cap, and the check that this contact actually opted in to this campaign. A model that is right almost every time is the wrong place for a rule that has to be right every time.

On the Kixie side, the connection is a custom build and the Claude integration page says exactly that. Kixie does not have a native Claude integration. Teams connect Claude and Kixie with custom builds on the Kixie API and webhooks, or through Zapier, Make or n8n. Never let anyone describe that as one-click or built in.

The outbound half is one documented request. Kixie’s Send SMS automation takes a POST to the app event endpoint with a business ID, a target number, the message, and an API key, and it sends from the business’s own numbers. The documentation puts it on the Professional billing tier or higher as of November 15, 2026. Because the key travels in the request, put a small server between Claude and Kixie rather than placing the key inside a tool definition a user can read.

The inbound half is what makes it a conversation instead of a broadcast. Kixie’s webhooks post call and message events to a URL you own, so a reply can reach your code, your code can update the CRM, and Claude can be handed the thread as context for the next draft. Kixie’s webhooks and API surface is where that side gets configured.

What changes once the send runs through a business number? The message becomes part of a campaign registered for that purpose, the reply lands in a shared inbox that a second rep can answer, and the thread is logged against the contact in the CRM so the manager can read it and the next rep inherits it instead of starting cold. A stop request hits a suppression list that every connected tool reads, rather than one phone that happens to be on aeroplane mode. Kixie’s business texting feature page covers the A2P 10DLC side of that, which is the registration layer the carriers check.

None of that is Claude’s job and none of it should be. Claude is good at the sentence. The number is good at the record. Keep them in their lanes.

What to Check Before You Let Claude Send Text Messages

Before anyone connects anything, settle these. They take an afternoon and they decide everything after it.

  • Which number does the message leave from? Answer this first. If the answer is a rep’s personal number, stop and finish the other questions anyway, because the answers will change your mind.
  • Who is the sender, in CTIA’s terms? If a person is texting on behalf of the company, the traffic is Non-Consumer whatever handset is involved.
  • Where is the opt-in record? Name the system and the field. If you cannot name both, you do not have one.
  • What happens when somebody replies stop? Trace it. The suppression has to be enforced by the system that sends, not by the model that drafts, and every connected tool has to read the same list.
  • Who else can see the thread tomorrow? If the answer is one rep and one laptop, the conversation is not in your pipeline.
  • What does the rep no longer do by hand? If the honest answer is only typing, you have a drafting aid, and you should buy it as one.

Then run it on a small list of people who agreed to be on it and read every message that goes out for the first week. Not because the drafts will be bad. Because the first time your rules and your workflow disagree with each other, and they will, you want to find that out on ten contacts rather than on four hundred.

The useful version of this is boring, and that is the point. Claude reads the call summary, drafts the follow-up and proposes it, your code checks the suppression list and the campaign before anything leaves, the business number sends it, and the reply comes back through a webhook into a shared inbox where somebody other than the original rep can answer it. Nobody is impressed by the demo. The record survives the rep.

For a worked build of the same shape on the other major model, the ChatGPT SMS bot teardown walks the costs and the consent handling end to end.

Claude Text Message FAQs

Can Claude send a text message on its own?

Not through the API. Anthropic documents that client tools run in your application, that Claude replies with stop_reason tool_use, and that your code runs the operation. On macOS the Read and Send iMessages connector does send, but it does so by operating the Messages app on your Mac after you grant macOS permission. On iOS and Android, Claude drafts and pre-fills and you press send.

Does the macOS iMessage connector work for business texting?

No, not as your business texting channel, even though it genuinely does send real messages. The classification is the problem. CTIA treats messaging sent by an individual acting on behalf of a business as Non-Consumer, and says automation used by a Non-Consumer to facilitate messaging is not typical Consumer operation. There is also nowhere in a personal thread to keep the opt-in details CTIA tells senders to retain.

Can Claude read the replies to a text message?

Only on macOS, and in a build you wire yourself. On iOS and Android the answer is no, and both help pages say so, because Claude does not read existing messages or emails and only creates new content. The macOS connector exposes read_imessages and get_unread_imessages, so it can. In a custom build, replies reach Claude only if you route them there, usually through an inbound message webhook.

Do we still need 10DLC registration if Claude writes the texts?

Yes, and the question has the dependency backwards. Registration attaches to the number and the campaign, not to whoever or whatever wrote the words. A model drafting the copy changes nothing about what the carriers check.

Is iMessage the same as SMS for business messaging rules?

Treat them as different channels with the same obligation. An iMessage between two Apple devices does not travel the same path as an SMS, and the macOS connector drives the consumer Messages app rather than a business messaging service. The sender test that puts you in Non-Consumer territory does not turn on the transport.

What is the smallest useful version of this?

Let reps use the mobile app to draft, and send everything outbound from the business number through your normal texting tool. You get the speed benefit on day one and you change nothing about the record. Add the API path later, when you have a rule you want enforced in code.

Sources

  • Anthropic, Read and Send iMessages connector listing, for the connector being made by Anthropic, added March 2026, the send_imessage, search_contacts, read_imessages and get_unread_imessages tools, the use of macOS automation features to interact with the Messages app, the explicit macOS security permission prompts, and the statement that it is not affiliated with or endorsed by Apple Inc. https://claude.com/marketplace/connectors/read-and-send-imessages. Reviewed November 15, 2026.
  • Anthropic Help Center, Use Claude with iOS apps, for drafting and sending through the Messages app or platforms such as WhatsApp, Slack and Messenger, the review and tap-to-send steps, the use of the device built-in sharing system, and the statement that Claude does not read existing messages or emails and only creates new content. https://support.claude.com/en/articles/11869619-use-claude-with-ios-apps. Reviewed November 15, 2026.
  • Anthropic Help Center, Use Claude with Android apps, for the same draft and hand-off behavior on the default messaging app and third-party apps, the note that no permissions are required because it uses the Android sharing system, and the same limit on reading existing messages. https://support.claude.com/en/articles/11869629-use-claude-with-android-apps. Reviewed November 15, 2026.
  • Anthropic, Tool use with Claude, for client tools running in your application, Claude responding with stop_reason tool_use and one or more tool_use blocks, and your code running the operation and sending back a tool_result. https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview. Reviewed November 15, 2026.
  • CTIA, Messaging Principles and Best Practices, May 2023, section 4 on Consumer and Non-Consumer traffic classification, for the sender test covering a business, organization or other entity or an individual acting on behalf of one, the Consumer messaging automation clause, Exhibit I attributes of typical Consumer operation at 15 to 60 messages per minute, 1,000 per day, one telephone number, 100 distinct recipients, a one to one outgoing to incoming ratio and 25 repetitive messages, the footnote that meeting those numbers does not reclassify a Non-Consumer sender, the opt-in documentation items in section 5, and the rule that an opt-in is not transferable or assignable. https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf. Reviewed November 15, 2026.
  • Kixie, Send SMS developer documentation, for the POST request to the app event endpoint with businessid, target, message and apikey, the sms event name, and the Professional billing tier requirement. https://www.kixie.com/developer/automation-send-sms/. Reviewed November 15, 2026.

Sources verified and content reviewed by the Kixie Research Team on November 15, 2026.

Ready to close more deals with Kixie?

See how Kixie's AI-powered tools can transform your sales and support operations.

Start Free Trial

Kixie Research Team is the organizational byline for content created and maintained by Kixie’s staff writers and editors through a shared research and editorial process. The team covers sales technology, outbound calling workflows, CRM integrations, and revenue operations. This shared byline reflects organizational accountability; it does not mean every article reflects hands-on testing. Individual pages identify their sources, methods, and limitations.

How we research, source, and update this article

How Kixie researches, sources, and updates articles like this one is described in our editorial standards.

If you spot an error or an outdated detail, request a correction.

Third-party sources linked in this article

This list is generated automatically from the third-party links referenced in the article above.