# Run a consumer-facing agent over iMessage with SMS fallback

> Run a consumer-facing agent over iMessage with SMS fallback: 0 companies fully do it, 3 with a limit, 49 carry the tag. Every listing in Messaging APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/messaging.imessage-agent/
- Markdown: https://www.anchorterminal.com/niches/messaging.imessage-agent/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/messaging.imessage-agent/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/messaging.imessage-agent/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 3 | 49 | 7 | 7 |

## What counts as done

Replies reach iMessage users and fall back to SMS or RCS for non-iMessage numbers in the same call, within the provider's documented daily caps.

Measured, for our own tests: replies arrive within 5 seconds of being sent, and the line stays active within those caps for 30 days.

How agents ask for it: put our assistant in iMessage; give the agent a blue-bubble number; text users from an iMessage line

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Linq (Linq App Inc.)**: Every send falls back iMessage, RCS, SMS in one call, capability checks exist, and acc-62 runs eight Linq lines after an Apple ban elsewhere. Latency isn't published or measured here, and lines past about 7,000 messages a day can be flagged.
- **Photon (Something Great Inc.)**: Managed iMessage lines with documented caps (5,000 messages a server and 50 new conversations a line a day) and deliverability guidance. Stable has no SMS fallback in the same call, latency isn't published, and a 2-hour full outage was logged on 2 September 2026.
- **Sendblue (Round One, Inc.)**: One send uses iMessage and falls back to SMS (was_downgraded, service fields), and daily caps per line are published. acc-59 measured replies regularly over 20 seconds, well past the 5-second bar.

- not this job: 360dialog WhatsApp API + MCP (360dialog GmbH): WhatsApp provider; no iMessage channel in the docs index.
- not this job: AWS End User Messaging (Amazon Web Services, Inc.): No iMessage channel; SMS, MMS, RCS, WhatsApp and voice only.
- not this job: Bandwidth Messaging API + MCP (Bandwidth Inc.): No iMessage channel. RCS with SMS fallback exists through the multi-channel endpoint, but not iMessage.
- not this job: Bird API + MCP (Bird B.V.): Bird has Apple Messages for Business, where the customer starts from an entry point; it is not a phone-number iMessage line and has no SMS fallback in the same call.
- not this job: ClickSend SMS API + MCP (ClickSend Pty Ltd): No iMessage channel.
- not this job: Infobip API + MCP (Infobip Ltd): Apple Messages for Business is offered, which customers start from Apple entry points; it isn't a phone-number iMessage line, though Messages API failover can move to SMS.
- not this job: Kudosity (Known Pty Ltd): No iMessage channel; RCS with SMS fallback is the closest.
- not this job: Plivo API (Plivo Inc.): No iMessage channel.
- not this job: Prelude (DING SAS): No iMessage channel.
- not this job: Sinch Messaging APIs + MCP (Sinch AB (publ)): No iMessage channel in the supported channel list.
- not this job: Telegram Bot API (Telegram Messenger Inc.): Telegram only; no iMessage or SMS fallback.
- not this job: Telnyx API + MCP (Telnyx LLC): No iMessage channel; SMS, MMS, RCS and WhatsApp.
- not this job: Twilio API + MCP (Twilio Inc.): No iMessage channel.
- not this job: Vonage Messages API + MCP (Vonage Holdings Corp.): No iMessage channel; RCS with SMS failover is the closest.
- not this job: Wati (Clare.AI Limited): WhatsApp, Instagram and Messenger only.
- not this job: WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.): WhatsApp only.
- not this job: YCloud (YCloud International Pte. Ltd.): No iMessage channel.

## What stops agents finishing

- Apple bans the line for volume or reports, with no appeal
- proactive outbound needs an unpriced or sales-led plan
- inbound stream stalls with no automatic recovery

## Around it

After: personal-assistants.chat-remote-control, support.handoff-to-person.

## Where this comes from

Weight 7 of 100 in Messaging APIs: 7 of 69 accounts; Hacker News Launch HN threads and one customer engineering blog; three listings (Sendblue, Linq, Photon) serve only this job

As data: https://www.anchorterminal.com/api/v1/use-cases/messaging.imessage-agent.json, or the MCP tool get_use_case with id messaging.imessage-agent. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
