Review / Platform
Miss Blue review
An iMessage API plus a full conversation platform around it.
Miss Blue gives your business a virtual iMessage line and then gives you two ways to work it: an API for building sending and replies into your own product, and a Message Center — a shared team inbox — for people who will never touch code. It also offers CRM workflows and AI agents with human handoff, which puts it closer to a complete platform than to a bare sending endpoint.
What it is good at
- Covers both audiences — an API for developers, a no-code inbox for your front desk.
- CRM workflow and AI-agent features aim at sales follow-up, not just notifications.
- A dedicated blue line keeps business threads separate from anyone's personal number.
- Human handoff on the agent side is the right default for a channel customers reply to.
Where it will bite you
- A broader platform means more surface area to evaluate than a pure sending API.
- Several protocol-level capabilities are not stated plainly on the marketing site — confirm the ones you depend on.
- Published response-rate and revenue figures are the vendor's own; treat them as claims.
What Miss Blue claims
Reported as the vendor's own marketing claims. We have not independently reproduced these numbers, and neither should you treat them as benchmarks.
- 80% higher response rates than SMS outreach
- 37% more attributed revenue than SMS outreach
The shape of the API
Illustrative — parameter names and endpoints change. Treat this as the flavour of the integration, and copy the real thing from the official docs.
const res = await fetch("https://api.missblue.dev/v1/messages", { method: "POST", headers: { Authorization: `Bearer ${process.env.MISSBLUE_API_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ to: "+15551234567", text: "Your invoice is ready: " + tagged("https://acme.co/inv/8821", { campaign: "invoice_ready", }), }),}); if (!res.ok) throw new Error(`send failed: ${res.status}`);Tracking links with Miss Blue
UTM note
If you use the CRM workflow features, set the UTM convention once at the workflow level so campaigns launched from the inbox tag identically to campaigns launched from your code.
Whatever you send with, build the URL from one helper so tagging is consistent across every job and campaign. Open the UTM builder to generate one now.
Still weighing options?
The comparison table puts all five side by side.