What is the difference between LoopMessage and Project Blue?

LoopMessage supports 53 of the 77 features compared here, and Project Blue supports 42. LoopMessage adds threaded replies, read receipts, edit and unsend, animated text effects and stickers. Project Blue adds sender name and photo, FaceTime calls and Slack.

How much do LoopMessage and Project Blue cost?

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. Project Blue: Flat per-line pricing: $166 a month per line billed annually or $199 a month per line on a 12-month plan, with a free trial on a shared line.

Does Project Blue support threaded replies?

Project Blue does not list threaded replies on its site or in its docs.

Does Project Blue support read receipts?

Project Blue does not list read receipts on its site or in its docs.

Does Project Blue support edit and unsend?

Project Blue does not list edit and unsend on its site or in its docs.

LoopMessage vs Project Blue: Features, Pricing and Differences

Feature comparison

Feature	LoopMessage	Project Blue
iMessage messaging
iMessage	Supported	Supported
Group chats	SupportedSend and receive in iMessage groups; not available in the sandbox.	SupportedSend to groups of 2 to 32 by API. Not on trial accounts, and group sends do not sync to the CRM.
Group management	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.	PartialGroups are created by sending to a set of numbers. No add or remove member endpoints documented.
Group name and photo	SupportedSet group name (32 characters max) and photo with PATCH.	PartialgroupName can be set when a group is created. No group photo documented.
Mentions	Not listed	Not listed
Tapbacks	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.	PartialSend or remove the six classic tapbacks on inbound iMessages. Receiving reactions is not documented.
Threaded replies	Supportedreply_to_id on send; inbound webhooks carry a thread object.	Not listed
Typing indicators	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.	PartialSend only, iMessage only, into an existing conversation. Inbound typing events not documented.
Read receipts	PartialYou can mark chats read; no read event is documented for your outbound messages.	Not listed
Edit and unsend	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.	Not listed
Message effects	Supported13 bubble and screen effects via the effect field.	Supported4 bubble and 9 screen effects through the effect field. iMessage only.
Animated text effects	SupportedMarkup for shake, nod, explode, ripple, bloom and jitter.	Not listed
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, videos and vCards by URL.
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 files sent as voice memos, plus AI text-to-speech voice memos.
Contact cards	Supportedcontact_file adds a vCard to the message.	SupportedVCF files through mediaAttachmentUrl.
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.	Not listed
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, read and share a line's Share Name and Photo card by API.
FaceTime calls	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.	PartialFaceTime Audio only, outbound and inbound, on FaceTime-enabled accounts. Not on trials.
Delivery status	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.	PartialMessages carry a status field such as delivered. Webhooks cover only inbound and outbound messages.
iMessage availability check	PartialThrough LoopLookup, a separate LoopMessage service.	Supported
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedDedicated senders run on hardware LoopMessage rents to you.	SupportedNo iPhone, Mac or SIM needed. Lines are set up remotely, usually within one business day.
Dedicated numbers	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.	SupportedA dedicated line per rep, never shared. New lines are requested by API and provisioned by the team.
Shared numbers	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.	PartialTrial accounts only: a shared line that can reach verified numbers.
Bring your own number	PartialYou can port a US number in; your own Apple IDs are not accepted.	SupportedExisting numbers can be ported to Project Blue's carrier partner.
Line pooling	SupportedSender pools balance new contacts across senders and match replies to the right one.	SupportedSends without lineId are load balanced across your lines.
SMS fallback	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.	SupportedFalls back to SMS from the same line when iMessage is unavailable.
RCS fallback	SupportedSame add-on uses RCS instead of SMS when the device supports it.	Not listedHomepage describes fallback from iMessage to WhatsApp to SMS. RCS fallback is not described.
Outbound-first messaging	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.	SupportedLines are sold as outbound-ready. Guidelines rule out mass outbound iMessage.
Calls on the iMessage number	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.	SupportedDialer and FaceTime Audio calls from the same number as the messaging line.
Other channels
SMS	SupportedSet channel to sms; needs the SMS/RCS add-on.	Supported
RCS	SupportedSet channel to rcs; needs the SMS/RCS add-on.	PartialRCS for rich media was rolled out in 2026. The API lists RCS as inbound only.
WhatsApp	SupportedAdd-on, +$10/mo, on the same phone number and API.	PartialHomepage lists WhatsApp as a fallback step. No WhatsApp option in the API, and llms.txt says it is not a WhatsApp API.
Telegram	Not supportedPlanned on the roadmap, not available yet.	Not supportedNot offered
Slack	Not listed	PartialSlack notifications for inbound replies. Not a messaging channel.
Email	Not listed	Not supportedDeveloper page says it is not a general email API.
Phone calls	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.	SupportedCloud dialer with inbound, outbound, routing, recording and voicemail, plus a browser calling SDK.
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.	PartialOne send endpoint covers iMessage and SMS. Calls and FaceTime use separate endpoints.
Developer tools
REST API	Supported	SupportedREST API with Bearer keys and an OpenAPI spec.
TypeScript SDK	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.	Partial@tryprojectblue/dialer is a browser SDK for phone calls only. No messaging SDK.
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	Not listed
Webhooks	SupportedRetried up to 30 times over several hours.	SupportedInbound and outbound message events and inbound FaceTime call events.
Signed webhooks	PartialYou set an authorization header and verify it; no HMAC signature.	Not listedWebhook docs do not mention signatures.
MCP server	PartialDocumentation-only MCP server; no access to your account or messages.	SupportedRemote MCP server with OAuth 2.1, plus an optional Claude Code plugin.
Open source	PartialOnly the n8n node is MIT on GitHub; the platform is closed.	PartialThe dialer SDK is MIT licensed on npm. The platform is closed.
Self-hosting	Not listed	Not listedHosted service on Project Blue lines. Self-hosting is not mentioned.
Local testing	Not listedThe sandbox needs a real iPhone or Mac to message it.	Not listedTrial accounts send real messages to verified numbers; docs say they are not a simulator.
Custom channel providers	Not listed	Not listed
Event replay	PartialWebhook history API to fetch past events; no replay call.	Not supportedDocs say webhooks have no retries and failed deliveries are not replayed.
OpenTelemetry	Not listed	Not listed
No-code integrations	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.	SupportedGoHighLevel conversation provider with workflow actions and triggers. llms.txt also lists Zapier.
CRM integrations	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.	SupportedHubSpot and Close CRM. Salesforce is not listed.
Built for AI agents
Agent framework	Not listed	Not listed
Agent framework integrations	Not listed	Not listed
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.	PartialReps reply in the CRM inbox and can join group threads. No agent handoff controls documented.
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.	SupportedList and get messages, inbound and outbound, with filters.
Plans and compliance
Free plan	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.	PartialFree trial on a shared line to verified numbers. Some endpoints are off on trial.
Public pricing	Supported	Supported$166/month per line billed annually, or $199/month per line on a 12-month plan.
No per-message fees	SupportedUnlimited messages; plans cap unique active contacts per day.	SupportedFlat per-line pricing with unlimited texting under fair use.
Uptime SLA	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.	Not listedSite cites a 99.9% uptime record and a public status page. No contractual SLA found.
Isolated infrastructure	SupportedA dedicated sender's number and server are allocated to you alone.	PartialEach rep gets a dedicated line that is never shared. Other infrastructure is not described.
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.	PartialPrivacy policy lists GDPR and UK GDPR rights. No DPA found.

Feature

LoopMessage

Project Blue

iMessage messaging

iMessage

Group chats

Send and receive in iMessage groups; not available in the sandbox.

Send to groups of 2 to 32 by API. Not on trial accounts, and group sends do not sync to the CRM.

Group management

Create groups (needs the Init conversations add-on) and add or remove members.

PartialGroups are created by sending to a set of numbers. No add or remove member endpoints documented.

Group name and photo

Set group name (32 characters max) and photo with PATCH.

PartialgroupName can be set when a group is created. No group photo documented.

Mentions

Not listed

Tapbacks

Six tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.

PartialSend or remove the six classic tapbacks on inbound iMessages. Receiving reactions is not documented.

Threaded replies

reply_to_id on send; inbound webhooks carry a thread object.

Not listed

Typing indicators

Up to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.

PartialSend only, iMessage only, into an existing conversation. Inbound typing events not documented.

Read receipts

PartialYou can mark chats read; no read event is documented for your outbound messages.

Not listed

Edit and unsend

Edit within 15 minutes, unsend within 2 minutes of sending.

Not listed

Message effects

13 bubble and screen effects via the effect field.

4 bubble and 9 screen effects through the effect field. iMessage only.

Animated text effects

Markup for shake, nod, explode, ripple, bloom and jitter.

Not listed

Stickers

PartialInbound messages can have type sticker; sending stickers is not documented.

Not listed

Formatted text

Bold, italic, underline, strikethrough and text sizes in iMessage.

Not listed

Attachments

Up to 10 public HTTPS file URLs per message.

Images, videos and vCards by URL.

Live Photos

Not listed

Rich link previews

Links get rich previews by default; preview: false sends plain text.

Not listed

Voice messages

Send audio files as voice messages; inbound audio is transcribed.

Audio files sent as voice memos, plus AI text-to-speech voice memos.

Contact cards

contact_file adds a vCard to the message.

VCF files through mediaAttachmentUrl.

Polls

Not listedA helpdesk article lists polls among features, but no poll API is documented.

Not listed

Chat backgrounds

Not listed

Location sharing

PartialInbound messages can have type location; sending a location is not documented.

Not listed

iMessage apps

Not listed

Live app cards

Not listed

Sender name and photo

Not listedDocs suggest sending a vCard so recipients see your name and photo.

Set, read and share a line's Share Name and Photo card by API.

FaceTime calls

Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.

PartialFaceTime Audio only, outbound and inbound, on FaceTime-enabled accounts. Not on trials.

Delivery status

message_delivered and message_failed webhooks, plus a status lookup by ID.

PartialMessages carry a status field such as delivered. Webhooks cover only inbound and outbound messages.

iMessage availability check

PartialThrough LoopLookup, a separate LoopMessage service.

Focus and Notify Anyway

Not listed

Numbers and delivery

Managed lines

Dedicated senders run on hardware LoopMessage rents to you.

No iPhone, Mac or SIM needed. Lines are set up remotely, usually within one business day.

Dedicated numbers

Phone number option is +$15/mo per dedicated sender; email senders also offered.

A dedicated line per rep, never shared. New lines are requested by API and provisioned by the team.

Shared numbers

Shared senders for AI assistant use from $20/mo; free sandbox for testing.

PartialTrial accounts only: a shared line that can reach verified numbers.

Bring your own number

PartialYou can port a US number in; your own Apple IDs are not accepted.

Existing numbers can be ported to Project Blue's carrier partner.

Line pooling

Sender pools balance new contacts across senders and match replies to the right one.

Sends without lineId are load balanced across your lines.

SMS fallback

Paid add-on, +$15/mo per dedicated sender; included on shared plans.

Falls back to SMS from the same line when iMessage is unavailable.

RCS fallback

Same add-on uses RCS instead of SMS when the device supports it.

Not listedHomepage describes fallback from iMessage to WhatsApp to SMS. RCS fallback is not described.

Outbound-first messaging

PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.

Lines are sold as outbound-ready. Guidelines rule out mass outbound iMessage.

Calls on the iMessage number

PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.

Dialer and FaceTime Audio calls from the same number as the messaging line.

Other channels

SMS

Set channel to sms; needs the SMS/RCS add-on.

RCS

Set channel to rcs; needs the SMS/RCS add-on.

PartialRCS for rich media was rolled out in 2026. The API lists RCS as inbound only.

Add-on, +$10/mo, on the same phone number and API.

PartialHomepage lists WhatsApp as a fallback step. No WhatsApp option in the API, and llms.txt says it is not a WhatsApp API.

Not supportedPlanned on the roadmap, not available yet.

Not supportedNot offered

Slack

Not listed

PartialSlack notifications for inbound replies. Not a messaging channel.

Not listed

Not supportedDeveloper page says it is not a general email API.

Phone calls

PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.

Cloud dialer with inbound, outbound, routing, recording and voicemail, plus a browser calling SDK.

Apple Messages for Business

Not supportedNot offered; the helpdesk contrasts LoopMessage with it.

Not supportedNot offered

Unified channel API

iMessage, SMS, RCS and WhatsApp on one number and one API.

PartialOne send endpoint covers iMessage and SMS. Calls and FaceTime use separate endpoints.

Developer tools

REST API

REST API with Bearer keys and an OpenAPI spec.

TypeScript SDK

PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.

Partial@tryprojectblue/dialer is a browser SDK for phone calls only. No messaging SDK.

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

Webhooks

Retried up to 30 times over several hours.

Inbound and outbound message events and inbound FaceTime call events.

Signed webhooks

PartialYou set an authorization header and verify it; no HMAC signature.

Not listedWebhook docs do not mention signatures.

MCP server

PartialDocumentation-only MCP server; no access to your account or messages.

Remote MCP server with OAuth 2.1, plus an optional Claude Code plugin.

Open source

PartialOnly the n8n node is MIT on GitHub; the platform is closed.

PartialThe dialer SDK is MIT licensed on npm. The platform is closed.

Self-hosting

Not listed

Not listedHosted service on Project Blue lines. Self-hosting is not mentioned.

Local testing

Not listedThe sandbox needs a real iPhone or Mac to message it.

Not listedTrial accounts send real messages to verified numbers; docs say they are not a simulator.

Custom channel providers

Not listed

Event replay

PartialWebhook history API to fetch past events; no replay call.

Not supportedDocs say webhooks have no retries and failed deliveries are not replayed.

OpenTelemetry

Not listed

No-code integrations

n8n, Zapier, Pipedream, HighLevel and LeadConnector.

GoHighLevel conversation provider with workflow actions and triggers. llms.txt also lists Zapier.

CRM integrations

HighLevel CRM and LeadConnector; no HubSpot or Salesforce found.

HubSpot and Close CRM. Salesforce is not listed.

Built for AI agents

Agent framework

Not listed

Agent framework integrations

Not listed

Streaming replies

Not listed

Agent group chats

Not listed

Human handoff

PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.

PartialReps reply in the CRM inbox and can join group threads. No agent handoff controls documented.

Audit logs

PartialMessage, webhook and API request history kept; no account audit log found.

Not listed

Message history API

Paginated history per contact, filterable by date, direction and type.

List and get messages, inbound and outbound, with filters.

Plans and compliance

Free plan

Sandbox with 5 contacts; free shared plan for schools and non-profits.

PartialFree trial on a shared line to verified numbers. Some endpoints are off on trial.

Public pricing

$166/month per line billed annually, or $199/month per line on a 12-month plan.

No per-message fees

Unlimited messages; plans cap unique active contacts per day.

Flat per-line pricing with unlimited texting under fair use.

Uptime SLA

Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.

Not listedSite cites a 99.9% uptime record and a public status page. No contractual SLA found.

Isolated infrastructure

A dedicated sender's number and server are allocated to you alone.

PartialEach rep gets a dedicated line that is never shared. Other infrastructure is not described.

SOC 2 Type II

Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.

Not listed

GDPR

Helpdesk says data is stored following GDPR.

PartialPrivacy policy lists GDPR and UK GDPR rights. No DPA found.

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

LoopMessage vs Project Blue

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

LoopMessage

Project Blue

Where LoopMessage is ahead

Where Project Blue is ahead

Feature comparison

Pricing

LoopMessage

Project Blue

Which should you choose?

Frequently asked questions

More LoopMessage comparisons

More Project Blue comparisons