our assessment of imessage infrastructure providers, and their use cases

As an independent user of these tools, we wanted to share our assessment of what each iMessage infrastructure provider is best at and for.

There are 128 agents in the store and 15 infrastructure providers powering them. Here is the table, the four questions that separate them, and what to test.

How fast can you get to a first message?

Linq, Sendblue, and LoopMessage all publish a sandbox you can reach without a contract, and the caps differ. Sendblue's free tier is a shared number capped at 10 verified contacts, LoopMessage's is five, and Linq publishes a full sandbox with five-minute setup. Blooio provisions lines self-serve. Chert and Messages for Business both start with a conversation, which puts days or weeks in front of your first line of code.

Which providers allow outbound on the plan you can buy?

Sendblue's $100 line is inbound-first and outbound is enterprise-tier, so an agent that sends the first message cannot run on the published price. Messages for Business is inbound-only by design. Linq, Blooio, Chert, Tuco, and Photon support outbound at entry. LoopMessage bans cold outreach by policy.

Which have a SOC 2 Type II report?

The badge and the report are different objects. Linq publishes Type II and produces the report in security review, with message content inaccessible to Linq itself. Sendblue lists SOC 2 at enterprise. The rest disclose nothing. Once you are selling to a company with a vendor questionnaire, this ends the shortlist before any feature does.

Who backs uptime contractually?

Linq publishes 99.95% with remedies in the agreement, the only contractual uptime SLA we have found here. Tuco claims 99.9% and Photon guarantees uptime on Spectrum Cloud, both as marketing figures. Blooio cites 99% delivery, which measures a different thing.

What to test before you sign

Send your agent a tapback instead of a reply. Providers that drop reactions instead of delivering them as events make your agent re-ask a question the user answered with a thumbs up.

Then instrument delivery receipts rather than trusting a 200. The failure teams describe to us most often is a silent send failure, where the API returns success and the message never arrives, which we have heard reported on Photon and Sendblue. Your own metrics look clean while it happens.

Picking by use case

Developer shipping to production, or an enterprise agent. Linq A sandbox gets you to a first message in minutes, and one send path covers iMessage, RCS, SMS, and voice, so Android recipients do not need a second integration. Flat per-line pricing means a longer conversation costs nothing extra. It is also the only provider here with a contractual uptime SLA and a Type II report, which is what an enterprise security review asks for. Pricing is unpublished, so expect a sales conversation a weekend project does not need.

Reply-only agent. Sendblue or Blooio Sendblue's $100 line is built inbound-first, so you pay for the shape you need instead of an outbound tier you will not use. Blooio's inbound plan is the same trade at a lower commitment.

Sales team where a rep is the user. Sendblue, or Tuco Sendblue has the widest CRM integration list, which matters when the rep works in Salesforce or HubSpot rather than an API. Tuco gives each rep a dedicated device and number, so one rep's list cannot damage another's deliverability.

Agency serving many clients. Blooio White-label resale under your own brand, public per-line pricing you can mark up, and a workflow built around the CRM stack most agencies already run.

Budget or non-US users. LoopMessage The lowest real entry point at $59.99/mo, and WhatsApp sits in the same API as iMessage, so one integration covers users outside Apple's ecosystem.

One agent across iMessage, WhatsApp, Telegram, and Slack. Photon's Spectrum An MIT-licensed TypeScript SDK that puts every channel behind one interface, so you write agent logic once and delivery becomes a config choice.

Voice agent that also texts. AgentPhone, or Saperly AgentPhone returns calls and messages in one webhook format with transcription, so both share a handler. Saperly attaches consent records, AI disclosure, and an audit trail to the number itself, which is the part legal asks about. Neither sends iMessage, so pair with a provider above.

Teams willing to bet on a new entrant. Chert A clean developer-first API where the team helps build your first integration, which is worth real money early. No published pricing and no certifications disclosed, so you are trading vendor maturity for attention. We see potential here, but it's unproven as of yet.

Prototype. BlueBubbles, or a free sandbox BlueBubbles is open source and free, and reading it is the fastest way to understand what the commercial providers abstract away. You own the hardware and the uptime, so keep it away from users.

Messages for Business. Large brand with a support org. Apple puts a Messages button on your Maps listing and search results, which is free distribution nothing else offers. It cannot start a conversation, so run it alongside a provider.

Principles

Verify outbound on the plan you will pay for. Sandbox and entry tier differ on several of these.

Ask for the audit report, not the badge. Type II and its window mean one thing. "SOC 2" means four.

Trust receipts, not response codes. A 200 is not a delivery.

Prefer flat per-line pricing for anything conversational. Metered pricing taxes the behavior that makes an agent good.