iBlueText vs LoopMessage

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

iBlueText

Hosted or self-hosted iMessage lines with iPhone lookup
Starting price
$29/month (self-hosted, 1 line); $99/month per hosted line
Free plan
No-card trial: 100 lookups, 10 verifications and 10 iMessages; self-hosted 3-day trial

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

iBlueText supports 43 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

FeatureiBlueTextLoopMessage
iMessage messaging
iMessage
SupportedHosted lines on iBlueText's Macs and iPhones, or self-hosted on your own Macs
Supported
Group chats
Not listedNot mentioned in the API docs
SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management
Not listed
SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
Group name and photo
Not listed
SupportedSet group name (32 characters max) and photo with PATCH.
Mentions
Not listed
Not listed
Tapbacks
SupportedSend six tapbacks to inbound messages and receive reaction.received. Not on SIP-on rented Macs.
SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies
Supportedreply_to quotes an inbound message; falls back to a normal message if Apple refuses
Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators
PartialSend only, in existing iMessage threads; no inbound typing events documented
SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts
PartialReceive only: message.read and read_at when the recipient has read receipts on
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
Supported8 screen and 4 bubble effects on /send
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 listed
SupportedBold, italic, underline, strikethrough and text sizes in iMessage.
Attachments
SupportedPhotos, video, voice memos, vCards and PDFs, up to 5 files of 5 MB each
SupportedUp to 10 public HTTPS file URLs per message.
Live Photos
Not listed
Not listed
Rich link previews
SupportedGoHighLevel page cites real link previews; no API option documented
SupportedLinks get rich previews by default; preview: false sends plain text.
Voice messages
SupportedVoice memos sent and received as attachments
SupportedSend audio files as voice messages; inbound audio is transcribed.
Contact cards
Supported.vcf files sent as attachments
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
PartialHosted lines can get a business sender name at setup; no API or photo option documented
Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls
PartialFaceTime audio placed from the self-hosted Bridge app, with call webhooks; no call API
Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status
Supportedqueued, sent, delivered, read and failed; plain SMS has no delivery receipt
Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check
SupportedLookup API at $0.005 a number, 400 free per line a day; also detects FaceTime
PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedHosted plan: iBlueText runs the Mac, iPhone, Apple Account and US number
SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers
SupportedEach hosted line is its own US number on a dedicated, warmed Apple ID
SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers
PartialOnly the 10 free trial messages, which are sent from iBlueText's fleet
SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number
SupportedSelf-hosted uses your own iPhones and numbers; hosted lines can use your own Apple Account
PartialYou can port a US number in; your own Apple IDs are not accepted.
Line pooling
SupportedCampaigns spread new contacts across your lines and keep existing contacts on their line
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
PartialFalls back to green; the carrier decides RCS or SMS and iBlueText reports which
SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging
SupportedCapped at 50 new iMessage and 50 new SMS contacts a day per line, 15 in the first 5 days
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 line's Apple ID via the self-hosted Bridge app; no phone calls
PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS
SupportedSMS and MMS from the line's number; self-hosted can add Android phones or your own Twilio
SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS
PartialGreen messages go as RCS or SMS as the carrier decides; RCS cannot be selected
SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp
SupportedYour own number paired by QR code ($19/mo add-on) or a hosted number from $49/mo
SupportedAdd-on, +$10/mo, on the same phone number and API.
Telegram
Not supportedNot offered
Not supportedPlanned on the roadmap, not available yet.
Slack
Not supported
Not listed
Email
Not supported
Not listed
Phone calls
Not supportedNot offered; calls are FaceTime audio only
PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
Apple Messages for Business
Not supportedNot offered
Not supportedNot offered; the helpdesk contrasts LoopMessage with it.
Unified channel API
PartialiMessage and SMS share /send; WhatsApp has its own endpoint; inbound shares one webhook
SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API
SupportedOpenAPI 3.1 spec published
Supported
TypeScript SDK
Not listedNone found; docs say no SDK is needed
PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Python SDK
Not listed
PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Other SDKs
Not listed
PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
CLI
Not listed
Not listed
Webhooks
SupportedReplies, opt-outs and opt-in status events, per account or per line
SupportedRetried up to 30 times over several hours.
Signed webhooks
SupportedX-IBT-Signature: HMAC-SHA256 of the raw body
PartialYou set an authorization header and verify it; no HMAC signature.
MCP server
Supportedibluetext-mcp on npm, 30 tools
PartialDocumentation-only MCP server; no access to your account or messages.
Open source
Not supportedBridge is licensed per line and cannot be resold; only the npm MCP package is MIT
PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting
SupportediBlueText Bridge runs on your own Macs from $29/mo; messages stay on your hardware
Not listed
Local testing
Not listed
Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers
PartialSelf-hosted Bridge can route SMS through your own Twilio account
Not listed
Event replay
PartialWebhooks retried 3 times over about 12 minutes; conversations API has a since filter
PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel and Wix apps; Zapier, Make and n8n through webhooks
Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
CRM integrations
SupportedNative GoHighLevel only; HubSpot and Salesforce through the API and webhooks
SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
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
SupportedPause or resume the built-in AI per conversation; it steps back 24 hours after a manual reply
PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
Audit logs
PartialPortal API log lists every API call for 30 days
PartialMessage, webhook and API request history kept; no account audit log found.
Message history API
SupportedConversations API returns two-way transcripts
SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan
PartialOne-time allowance: 100 lookups, 10 verifications and 10 iMessages, no card
SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing
Supported
Supported
No per-message fees
SupportedFlat per line; lookups and verifications cost $0.005 each
SupportedUnlimited messages; plans cap unique active contacts per day.
Uptime SLA
Not supportedTerms provide the service as is, with no guarantee of availability
Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Isolated infrastructure
PartialSelf-hosted runs on your own Macs; hosted runs many lines per Mac
SupportedA dedicated sender's number and server are allocated to you alone.
SOC 2 Type II
Not listed
Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
GDPR
Not listedPrivacy policy mentions GDPR rights where applicable; no DPA found
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

iBlueText

Hosted lines cost $99 a month each plus a one-time setup fee from $249, self-hosted Bridge plans run from $29 a month for 1 line to $999 for 100 lines, and lookups cost $0.005 each.

Pricing model: flat per line, plus prepaid credits for lookups and verifications

Source

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

Which should you choose?

Choose iBlueText if you need sender name and photo, FaceTime calls, self-hosting and custom channel providers.

Choose LoopMessage if you need group chats, group management, group name and photo and edit and unsend.

Frequently asked questions