LoopMessage vs Miss Blue

Compare LoopMessage and Miss Blue side by side: iMessage features, channels, developer tools, pricing and compliance, checked on each provider's own site.

LoopMessage

iMessage, SMS, RCS and WhatsApp on one number
Starting price
$59.99/month per sender (Light)
Free plan
Sandbox: $0, 5 contacts, testing only; free shared plan for schools and non-profits

Miss Blue

Dedicated iMessage line with API, team inbox and calling
Starting price
$99/month per number (launch price)
Free plan
Free sandbox; 30-minute live demo line

LoopMessage supports 53 of the 77 features compared here, and Miss Blue supports 47.

Feature comparison

FeatureLoopMessageMiss Blue
iMessage messaging
iMessage
Supported
Supported
Group chats
SupportedSend and receive in iMessage groups; not available in the sandbox.
SupportedSend into an existing group by its chat_id and read group threads.
Group management
SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
SupportedCreate groups of 2 to 32 and add or remove members; leaving a group is not supported yet.
Group name and photo
SupportedSet group name (32 characters max) and photo with PATCH.
SupportedRename a group and set or remove its photo.
Mentions
Not listed
Not listed
Tapbacks
SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
SupportedAdd or remove the six tapbacks; tapbacks from customers appear on the message.
Threaded replies
Supportedreply_to_id on send; inbound webhooks carry a thread object.
SupportedQuoted replies with reply_to_message_id.
Typing indicators
SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
SupportedSend typing, optional auto-typing on inbound iMessage, and contact typing via webhook.
Read receipts
PartialYou can mark chats read; no read event is documented for your outbound messages.
SupportedExplicit read receipts by API; outbound messages report read.
Edit and unsend
SupportedEdit within 15 minutes, unsend within 2 minutes of sending.
PartialUnsend within Apple's 2-minute window. An edit endpoint is documented, but the FAQ says editing is not supported yet.
Message effects
Supported13 bubble and screen effects via the effect field.
Not supportedThe errors page says effects are not a supported API operation yet.
Animated text effects
SupportedMarkup for shake, nod, explode, ripple, bloom and jitter.
Not supportedThe errors page says expressive text styles and effects are not supported yet.
Stickers
PartialInbound messages can have type sticker; sending stickers is not documented.
Not listed
Formatted text
SupportedBold, italic, underline, strikethrough and text sizes in iMessage.
Not listed
Attachments
SupportedUp to 10 public HTTPS file URLs per message.
SupportedImages, video, PDFs, Office files and more up to 100 MiB, one per send, or carousels of 2 to 20 images.
Live Photos
Not listed
Not listed
Rich link previews
SupportedLinks get rich previews by default; preview: false sends plain text.
Not listed
Voice messages
SupportedSend audio files as voice messages; inbound audio is transcribed.
SupportedAudio-only sends use the native voice-note bubble by default.
Contact cards
Supportedcontact_file adds a vCard to the message.
Not listed
Polls
Not listedA helpdesk article lists polls among features, but no poll API is documented.
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
PartialInbound messages can have type location; sending a location is not documented.
SupportedSend Find My requests, read the sharing state and watch live fixes over Server-Sent Events.
iMessage apps
Not listed
Not listed
Live app cards
Not listed
Not listed
Sender name and photo
Not listedDocs suggest sending a vCard so recipients see your name and photo.
SupportedSet and verify the number's Name and Photo Sharing profile by API.
FaceTime calls
Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
PartialFaceTime Audio only, as a $250/month add-on per line.
Delivery status
Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
Supportedpending, sent, delivered, read and failed with a reason, by webhook or per-message callback.
iMessage availability check
PartialThrough LoopLookup, a separate LoopMessage service.
SupportedLive iMessage and FaceTime registration lookup; a separate lookup reads your own past traffic.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedDedicated senders run on hardware LoopMessage rents to you.
SupportedEach number runs on a Mac that Miss Blue operates; staff provision numbers within about 48 to 72 hours.
Dedicated numbers
SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Supported$99/month per number at the launch price (normally $198).
Shared numbers
SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
SupportedShared-pool numbers are offered as a separate, labelled option.
Bring your own number
PartialYou can port a US number in; your own Apple IDs are not accepted.
SupportedTransfer an existing number in; staff complete it in about 1 to 2 weeks.
Line pooling
SupportedSender pools balance new contacts across senders and match replies to the right one.
SupportedAuto round robin spreads new contacts across a project's dedicated numbers, then keeps each on one.
SMS fallback
SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
SupportedFalls back to RCS, or to SMS where RCS is unavailable, from the same number.
RCS fallback
SupportedSame add-on uses RCS instead of SMS when the device supports it.
SupportedFalls back to RCS where the carrier and recipient support it.
Outbound-first messaging
PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
SupportedNew contacts are paced: 50 per number per day by default and 150 messages a day in total.
Calls on the iMessage number
PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
SupportedFaceTime Audio and phone calls from the number customers already message.
Other channels
SMS
SupportedSet channel to sms; needs the SMS/RCS add-on.
SupportedAs fallback from the iMessage number; the docs also describe Twilio SMS lines.
RCS
SupportedSet channel to rcs; needs the SMS/RCS add-on.
SupportedAs fallback when the carrier and recipient support it.
WhatsApp
SupportedAdd-on, +$10/mo, on the same phone number and API.
Not supportedNot offered
Telegram
Not supportedPlanned on the roadmap, not available yet.
Not supported
Slack
Not listed
Not supportedNot offered as a channel; the Slack page is an integration guide.
Email
Not listed
Not supportedNot offered as a channel; iMessage can be sent to Apple ID email addresses.
Phone calls
PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
PartialBrowser phone calls as a $75/month add-on; API keys cannot place regular phone calls.
Apple Messages for Business
Not supportedNot offered; the helpdesk contrasts LoopMessage with it.
Not supportedNot offered
Unified channel API
SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
SupportediMessage with RCS and SMS fallback, groups and calls share one API and webhook stream.
Developer tools
REST API
Supported
Supported113 endpoints across 13 resources, with an OpenAPI file.
TypeScript SDK
PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Not listedThe API is plain HTTP; no SDK package was found.
Python SDK
PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Not listed
Other SDKs
PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
Not listed
CLI
Not listed
Supportedmb, with installers for macOS, Linux and Windows.
Webhooks
SupportedRetried up to 30 times over several hours.
Supported
Signed webhooks
PartialYou set an authorization header and verify it; no HMAC signature.
SupportedHex HMAC-SHA256 over timestamp and raw body; per-message callbacks are unsigned.
MCP server
PartialDocumentation-only MCP server; no access to your account or messages.
Supportedmb mcp serves the CLI commands as MCP tools for Claude Code, Codex, Cursor and others.
Open source
PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Not supportedThe CLI repo holds builds and installers without a license; the service is closed.
Self-hosting
Not listed
Not listed
Local testing
Not listedThe sandbox needs a real iPhone or Mac to message it.
Supportedmb_sandbox_ keys simulate outcomes and signed webhooks on a virtual number, with no phone.
Custom channel providers
Not listed
Not listed
Event replay
PartialWebhook history API to fetch past events; no replay call.
PartialPer-endpoint delivery log and history sync; docs say to poll GET /v1/messages to repair missed events.
OpenTelemetry
Not listed
Not listed
No-code integrations
Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
BetaGoHighLevel connector is in beta; the Zapier, Make and n8n pages are setup guides.
CRM integrations
SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
BetaGoHighLevel connector in beta; HubSpot and Salesforce pages describe API builds set up in onboarding.
Built for AI agents
Agent framework
Not listed
PartialNo agent SDK; offers a managed conversational AI add-on and multi-step automations.
Agent framework integrations
Not listed
PartialGuide pages for Vercel AI SDK, Chat SDK, LangChain and Claude Agent SDK; no adapter package found.
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listed
Human handoff
PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
SupportedShared Message Center for human takeover, with internal notes and resolving.
Audit logs
PartialMessage, webhook and API request history kept; no account audit log found.
Not listed
Message history API
SupportedPaginated history per contact, filterable by date, direction and type.
SupportedThread history by API and a conversation sync from the line's Mac.
Plans and compliance
Free plan
SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
SupportedFree sandbox with simulated sends, plus a 30-minute live demo line by texting DEMO.
Public pricing
Supported
Supported
No per-message fees
SupportedUnlimited messages; plans cap unique active contacts per day.
Supported
Uptime SLA
Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
PartialEnterprise only: contracted service terms; no uptime figure published.
Isolated infrastructure
SupportedA dedicated sender's number and server are allocated to you alone.
SupportedDedicated numbers run on hardware assigned to you; Enterprise adds dedicated equipment.
SOC 2 Type II
Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
Not listed
GDPR
SupportedHelpdesk says data is stored following GDPR.
Not listed

Checked on each provider's own site and docs on 2026-10-25. “Not listed” means the provider does not mention it.

Pricing

LoopMessage

A free sandbox covers 5 contacts; dedicated senders start at $59.99 a month, with add-ons for a phone number, SMS/RCS fallback, WhatsApp and outbound-first.

Pricing model: flat per sender with daily contact caps, plus monthly add-ons

Source

Miss Blue

A free sandbox for testing, then $99 per dedicated number per month at the launch price (normally $198), with the usual $479 setup fee waived until October 31; FaceTime Audio ($250), phone calls ($75) or both ($300) are optional add-ons per line, and Enterprise is custom.

Pricing model: flat per line

Source

Which should you choose?

Choose LoopMessage if you need message effects, animated text effects, stickers and formatted text.

Choose Miss Blue if you need sender name and photo, FaceTime calls, CLI and local testing.

Frequently asked questions