{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/messaging.imessage-agent/",
    "json": "https://www.anchorterminal.com/niches/messaging.imessage-agent/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/messaging.imessage-agent/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/messaging.imessage-agent/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 3 | 49 | 7 | 7 |\n\n## What counts as done\n\nReplies 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.\n\nMeasured, for our own tests: replies arrive within 5 seconds of being sent, and the line stays active within those caps for 30 days.\n\nHow agents ask for it: put our assistant in iMessage; give the agent a blue-bubble number; text users from an iMessage line\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n\n- not this job: 360dialog WhatsApp API + MCP (360dialog GmbH): WhatsApp provider; no iMessage channel in the docs index.\n- not this job: AWS End User Messaging (Amazon Web Services, Inc.): No iMessage channel; SMS, MMS, RCS, WhatsApp and voice only.\n- 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.\n- 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.\n- not this job: ClickSend SMS API + MCP (ClickSend Pty Ltd): No iMessage channel.\n- 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.\n- not this job: Kudosity (Known Pty Ltd): No iMessage channel; RCS with SMS fallback is the closest.\n- not this job: Plivo API (Plivo Inc.): No iMessage channel.\n- not this job: Prelude (DING SAS): No iMessage channel.\n- not this job: Sinch Messaging APIs + MCP (Sinch AB (publ)): No iMessage channel in the supported channel list.\n- not this job: Telegram Bot API (Telegram Messenger Inc.): Telegram only; no iMessage or SMS fallback.\n- not this job: Telnyx API + MCP (Telnyx LLC): No iMessage channel; SMS, MMS, RCS and WhatsApp.\n- not this job: Twilio API + MCP (Twilio Inc.): No iMessage channel.\n- not this job: Vonage Messages API + MCP (Vonage Holdings Corp.): No iMessage channel; RCS with SMS failover is the closest.\n- not this job: Wati (Clare.AI Limited): WhatsApp, Instagram and Messenger only.\n- not this job: WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.): WhatsApp only.\n- not this job: YCloud (YCloud International Pte. Ltd.): No iMessage channel.\n\n## What stops agents finishing\n\n- Apple bans the line for volume or reports, with no appeal\n- proactive outbound needs an unpriced or sales-led plan\n- inbound stream stalls with no automatic recovery\n\n## Around it\n\nAfter: personal-assistants.chat-remote-control, support.handoff-to-person.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Run a consumer-facing agent over iMessage with SMS fallback",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Run a consumer-facing agent over iMessage with SMS fallback",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/messaging.imessage-agent/",
    "published": "",
    "section": "agents",
    "title": "Run a consumer-facing agent over iMessage with SMS fallback | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/messaging.imessage-agent/"
  },
  "tokens": {
    "markdown": 1250,
    "slim": 230
  },
  "version": 1
}
