Blue Reacher vs LoopMessage

Blue Reacher supports 50 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

Feature	Blue Reacher	LoopMessage
iMessage messaging
iMessage	SupportedOne-to-one iMessage sends and replies over REST and webhooks.	Supported
Group chats	PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.	SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management	PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
Group name and photo	PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.	SupportedSet group name (32 characters max) and photo with PATCH.
Mentions	Not listed	Not listed
Tapbacks	PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies	PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.	Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators	PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts	Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.	PartialYou can mark chats read; no read event is documented for your outbound messages.
Edit and unsend	Not listed	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.
Message effects	Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.	Supported13 bubble and screen effects via the effect field.
Animated text effects	Not listed	SupportedMarkup for shake, nod, explode, ripple, bloom and jitter.
Stickers	Not listed	PartialInbound messages can have type sticker; sending stickers is not documented.
Formatted text	Not supportedDocs say there is no Markdown rendering on any channel.	SupportedBold, italic, underline, strikethrough and text sizes in iMessage.
Attachments	SupportedOne file per message for now. Images and video up to 100 MB, audio and PDF up to 25 MB.	SupportedUp to 10 public HTTPS file URLs per message.
Live Photos	Not listed	Not listed
Rich link previews	SupportedA bare URL renders as a preview card on iMessage, built on the recipient's device.	SupportedLinks get rich previews by default; preview: false sends plain text.
Voice messages	PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.	SupportedSend audio files as voice messages; inbound audio is transcribed.
Contact cards	PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.	Supportedcontact_file adds a vCard to the message.
Polls	Not listed	Not listedA helpdesk article lists polls among features, but no poll API is documented.
Chat backgrounds	Not listed	Not listed
Location sharing	Not listed	PartialInbound messages can have type location; sending a location is not documented.
iMessage apps	Not listed	Not listed
Live app cards	Not listed	Not listed
Sender name and photo	Not listedDocs say recipients see only the number until they save your contact card.	Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls	PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status	Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check	PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.	PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedEach line is an Apple ID on Apple hardware run by Blue Reacher.	SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers	SupportedEvery line is a dedicated number with a custom area code.	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers	Not supportedDocs say each line is yours alone, never shared and never recycled.	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number	SupportedPricing lists port-in support for an existing number.	PartialYou can port a US number in; your own Apple IDs are not accepted.
Line pooling	SupportedOmit the line on a send and load balancing picks one; the site calls it smart routing.	SupportedSender pools balance new contacts across senders and match replies to the right one.
SMS fallback	Supported	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback	PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.	SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging	SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
Calls on the iMessage number	PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS	PartialOnly as automatic fallback from the same line.	SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS	PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.	SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp	Not supportedNot offered	SupportedAdd-on, +$10/mo, on the same phone number and API.
Telegram	Not supported	Not supportedPlanned on the roadmap, not available yet.
Slack	Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.	Not listed
Email	Not supportedNot offered. Docs say there is no email-address sender option.	Not listed
Phone calls	PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
Apple Messages for Business	Not supportedNot offered; the site describes it as a separate Apple product.	Not supportedNot offered; the helpdesk contrasts LoopMessage with it.
Unified channel API	SupportediMessage and SMS fallback share one send endpoint and message model.	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Python SDK	SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Other SDKs	Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
CLI	Supportedbluereacher-cli on npm: send, status, conversations and capability checks.	Not listed
Webhooks	Supported	SupportedRetried up to 30 times over several hours.
Signed webhooks	SupportedHMAC-SHA256 in X-BlueReacher-Signature.	PartialYou set an authorization header and verify it; no HMAC signature.
MCP server	SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.	PartialDocumentation-only MCP server; no access to your account or messages.
Open source	PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.	PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting	Not listed	Not listed
Local testing	SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.	Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers	Not listed	Not listed
Event replay	PartialRetries for about a day; undelivered events are kept and support replays them on request.	PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry	Not listed	Not listed
No-code integrations	SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
CRM integrations	SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
Built for AI agents
Agent framework	PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.	Not listed
Agent framework integrations	PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listed	Not listed
Human handoff	SupportedPause or snooze the AI assistant per contact while a person replies.	PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
Audit logs	PartialDocs mention an exportable opt-out audit trail; no general activity log is documented.	PartialMessage, webhook and API request history kept; no account audit log found.
Message history API	SupportedConversation history per contact, cursor-paginated.	SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan	SupportedFree public sandbox key; simulator only, no real messages sent.	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing	Supported	Supported
No per-message fees	Supported	SupportedUnlimited messages; plans cap unique active contacts per day.
Uptime SLA	Not listed	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Isolated infrastructure	SupportedDedicated lines per customer, never shared; workspaces logically isolated.	SupportedA dedicated sender's number and server are allocated to you alone.
SOC 2 Type II	Not supportedTrust page says controls map to SOC 2 but the independent attestation is not complete.	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
GDPR	SupportedGDPR page and a published DPA with Standard Contractual Clauses.	SupportedHelpdesk says data is stored following GDPR.

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

Pricing

Which should you choose?

Choose Blue Reacher if you need FaceTime calls, CLI, local testing and agent framework.

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

Frequently asked questions

• Photon vs Blue Reacher
• Blue Reacher vs Linq
• Blooio vs Blue Reacher
• Blue Reacher vs Sendblue
• Blue Reacher vs Zernio
• Blue Reacher vs Chert
• Blue Reacher vs Miss Blue
• Bland vs Blue Reacher
• Blue Reacher vs BlueBubbles

• Photon vs LoopMessage
• LoopMessage vs Linq
• Blooio vs LoopMessage
• LoopMessage vs Sendblue
• LoopMessage vs Zernio
• Chert vs LoopMessage
• LoopMessage vs Miss Blue
• Bland vs LoopMessage
• BlueBubbles vs LoopMessage