Sent does not support iMessage. Its channels are SMS, WhatsApp and RCS. If you are evaluating Sent because you need blue bubbles, stop here — it is a good product and it is not this product.
This one is worth an explanation rather than a one-line correction, because Sent looks more like an iMessage vendor than most companies that actually are one.
Why everyone assumes it does
Sent raised a $12M Series A to build what it calls the messaging layer for AI agents, and reports serving over 14,000 developers and product teams. Its pitch is that you should not have to specify a channel at all — you send a message, and Sent handles routing, compliance and content transformation.
Read that pitch as a developer who wants to reach iPhone users and the conclusion is almost automatic. A messaging abstraction layer that routes to the best channel per recipient, in 2026, sounds exactly like something that would pick iMessage for an iPhone. It does not.
| Channel | Sent supports it | Notes |
|---|---|---|
| SMS | Yes | The core channel |
| Yes | Via the official Business API | |
| RCS | Yes | The rich channel on Android, and on iOS 18+ as RCS, not as a blue bubble |
| iMessage | No | Not a supported channel |
The RCS confusion does half the work here
iOS 18 added RCS support, and a great many people took that to mean RCS messages arrive as blue bubbles. They do not — they arrive as RCS, styled green. A vendor supporting RCS is therefore not a vendor supporting iMessage, no matter how the message reaches an iPhone. The full distinction is here.
Why this is not an oversight on Sent's part
Sent integrates channels that expose an official business API. SMS has one, WhatsApp has one, RCS has one. Person-to-person iMessage does not — Apple publishes no such API, which is the entire reason this website exists.
Every vendor that does send blue bubbles operates outside Apple's published terms to do it. That is a legitimate business with real customers, and it is a fundamentally different risk posture from wrapping official APIs. A company built on official integrations declining to add an unofficial one is a coherent decision, not a gap in the roadmap.
Check the channel list, not the funding round
Sent is the clearest case in this category of a company being assumed into a market by association. Well-funded, developer-facing, multi-channel, agent-focused — every signal points the right way except the one that matters, which is the published list of channels.
What to use instead
If you need to send iMessages from code, Sent is not a candidate — but there are around twenty that genuinely are. The shortest path through them:
- Start with [who sells an iMessage API](/answers/who-sells-an-imessage-api) for the full map of who is real and who is not.
- Check [what it costs](/pricing) — published entry pricing runs from a free tier to $249 per line per month, and the cheap tiers sometimes cannot send outbound.
- Read [does Apple have an iMessage API](/answers/does-apple-have-an-imessage-api) if you have not yet, because the answer is no and it shapes everything else.
- Compare the shortlist on [providers](/providers), where the feature grid shows who actually supports webhooks, group chats and SMS fallback.
If you actually wanted the multi-channel messaging API
Sent is a real product and a good one at what it does. This page is only about the messaging API it does not have — nothing here is a criticism of the thing it does sell.
Common questions
- Does Sent.dm support iMessage?
- No. Sent's published channel list is SMS, WhatsApp and RCS. There is no iMessage channel and the company does not advertise one.
- Will Sent add iMessage?
- Nothing public commits to it. Sent's model is to integrate channels that expose an official business API, and Apple does not publish one for person-to-person iMessage — so adding it would mean operating outside Apple's terms, which is a different business from the one Sent is in.
- What is the closest thing to Sent that does send iMessage?
- Chert is the nearest match on positioning — infrastructure primitives aimed at AI agents rather than an inbox for sales reps. Linq is the closest on channel breadth, covering iMessage, RCS, SMS and voice behind one API.