LoopMessage vs Zernio

LoopMessage supports 53 of the 77 features compared here, and Zernio supports 57.

Feature comparison

Feature	LoopMessage	Zernio
iMessage messaging
iMessage	Supported	Supported
Group chats	SupportedSend and receive in iMessage groups; not available in the sandbox.	SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.	SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo	SupportedSet group name (32 characters max) and photo with PATCH.	SupportedRename a group or change its photo, one change per call.
Mentions	Not listed	Not listed
Tapbacks	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.	SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies	Supportedreply_to_id on send; inbound webhooks carry a thread object.	SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.	PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts	PartialYou can mark chats read; no read event is documented for your outbound messages.	PartialMark a chat read inside an active two-way chat. Webhook docs list message.read for other platforms only.
Edit and unsend	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.	SupportedEdit text within 15 minutes; unsend within 2 minutes removes the bubble for the recipient.
Message effects	Supported13 bubble and screen effects via the effect field.	Supported13 screen and bubble effects, such as slam, invisibleInk, confetti and fireworks.
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.	PartialInbound stickers are typed as sticker. Sending stickers is not documented.
Formatted text	SupportedBold, italic, underline, strikethrough and text sizes in iMessage.	SupportedInline *bold*, _italic_, __underline__ and ~strikethrough~ markup renders as rich text.
Attachments	SupportedUp to 10 public HTTPS file URLs per message.	SupportedUp to 10 per message, each a public https URL of at most 256 characters.
Live Photos	Not listed	Not listed
Rich link previews	SupportedLinks get rich previews by default; preview: false sends plain text.	SupportedOn by default; linkPreview: false sends links as plain text.
Voice messages	SupportedSend audio files as voice messages; inbound audio is transcribed.	SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards	Supportedcontact_file adds a vCard to the message.	PartialcontactCard shares the sender's own card only.
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.	PartialStatic location pins only. Inbound shared locations arrive without coordinates.
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.	PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.	Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.	Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check	PartialThrough LoopLookup, a separate LoopMessage service.	Not listed
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedDedicated senders run on hardware LoopMessage rents to you.	SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.	SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.	SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number	PartialYou can port a US number in; your own Apple IDs are not accepted.	PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling	SupportedSender pools balance new contacts across senders and match replies to the right one.	Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.	SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback	SupportedSame add-on uses RCS instead of SMS when the device supports it.	SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.	SupportedOne new chat per 15 minutes per sender, warm-up from 2 to 50 a day, no links in openers.
Calls on the iMessage number	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.	PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
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.	Supported
WhatsApp	SupportedAdd-on, +$10/mo, on the same phone number and API.	Supported
Telegram	Not supportedPlanned on the roadmap, not available yet.	Supported
Slack	Not listed	Supported
Email	Not listed	Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.	SupportedInbound and outbound PSTN calls, SIP trunks, browser softphone, recording and transcription.
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.	SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API	Supported	Supported
TypeScript SDK	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.	Supported@zernio/node
Python SDK	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.	Supportedzernio-sdk
Other SDKs	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.	SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI	Not listed	SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks	SupportedRetried up to 30 times over several hours.	Supported
Signed webhooks	PartialYou set an authorization header and verify it; no HMAC signature.	SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server	PartialDocumentation-only MCP server; no access to your account or messages.	SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source	PartialOnly the n8n node is MIT on GitHub; the platform is closed.	PartialSDKs, CLI, n8n node and Chat SDK adapter are MIT or Apache-2.0. The platform is closed.
Self-hosting	Not listed	Not supportedHosted cloud service only
Local testing	Not listedThe sandbox needs a real iPhone or Mac to message it.	Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers	Not listed	Not listed
Event replay	PartialWebhook history API to fetch past events; no replay call.	Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry	Not listed	Not listed
No-code integrations	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.	Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.	SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework	Not listed	PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations	Not listed	PartialVercel Chat SDK adapter (iMessage not listed) and an OpenClaw skill.
Streaming replies	Not listed	PartialChat SDK adapter streams by editing on Telegram only.
Agent group chats	Not listed	Not listed
Human handoff	PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.	PartialDashboard inbox and workflow handoff nodes; no iMessage-specific handoff documented.
Audit logs	PartialMessage, webhook and API request history kept; no account audit log found.	SupportedAppend-only log of team-management actions; Enterprise adds broader audit logs.
Message history API	SupportedPaginated history per contact, filterable by date, direction and type.	Supported
Plans and compliance
Free plan	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.	SupportedFirst 2 connected accounts free; free iMessage sandbox (5 contacts, 50 messages a day).
Public pricing	Supported	Supported$200 per iMessage sender per month, plus the connected-account fee.
No per-message fees	SupportedUnlimited messages; plans cap unique active contacts per day.	PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.	Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure	SupportedA dedicated sender's number and server are allocated to you alone.	Not listed
SOC 2 Type II	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.	SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR	SupportedHelpdesk says data is stored following GDPR.	SupportedGDPR documentation in the trust portal; public DPA.

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 LoopMessage if you need animated text effects, iMessage availability check, line pooling and isolated infrastructure.

Choose Zernio if you need sender name and photo, Telegram, Slack and CLI.

Frequently asked questions

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

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