What is the difference between Comms by Osis and LoopMessage?

Comms by Osis supports 43 of the 77 features compared here, and LoopMessage supports 53. Comms by Osis adds polls, chat backgrounds, sender name and photo, FaceTime calls and agent framework. LoopMessage adds message effects, animated text effects, stickers, formatted text and rich link previews.

How much do Comms by Osis and LoopMessage cost?

Comms by Osis: Free on a shared line with 100 messages a day, Plus at $50 a month on a shared line, Dedicated at $200 a month per number with $0 setup, and custom Enterprise; AI usage is billed separately. 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.

Does LoopMessage support polls?

LoopMessage does not list polls on its site or in its docs.

Does LoopMessage support chat backgrounds?

LoopMessage does not list chat backgrounds on its site or in its docs.

Does LoopMessage support sender name and photo?

LoopMessage does not list sender name and photo on its site or in its docs.

Comms by Osis vs LoopMessage

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

Comms by Osis

iMessage, RCS, SMS and WhatsApp API with hosted agents

Starting price: $50/month (shared line); $200/month per dedicated number
Free plan: Free: shared platform line, 100 messages a day, no card

Visit Comms by Osis Read more

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

Visit LoopMessage Read more

Comms by Osis supports 43 of the 77 features compared here, and LoopMessage supports 53.

Where Comms by Osis is ahead

Where LoopMessage is ahead

and 7 more in the table below.

Feature comparison

Feature	Comms by Osis	LoopMessage
iMessage messaging
iMessage	Supported	Supported
Group chats	SupportedGroups of 2 to 31 people from a dedicated line with group support. Not on the shared line.	SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management	PartialCreate a group with its first message; adding or removing members is not documented.	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
Group name and photo	PartialName a group when you create it; group photos and renames are not documented.	SupportedSet group name (32 characters max) and photo with PATCH.
Mentions	Not listed	Not listed
Tapbacks	SupportedClassic tapbacks or custom emoji, add, replace or remove; reaction webhooks for inbound.	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies	Supportedreply_to_message_id replies inside an iMessage thread; text only.	Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators	SupportedShow or hide typing dots on iMessage, RCS and WhatsApp.	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts	SupportedMark a conversation read to send a receipt; comms.message.read for one-to-one chats.	PartialYou can mark chats read; no read event is documented for your outbound messages.
Edit and unsend	PartialUnsend within Apple's 2-minute window on supported lines. No edit endpoint; inbound edits fire events.	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.
Message effects	Not listed	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	SupportedUp to 32 files and 9 MiB per message, sent as base64.	SupportedUp to 10 public HTTPS file URLs per message.
Live Photos	Not listed	Not listed
Rich link previews	Not listed	SupportedLinks get rich previews by default; preview: false sends plain text.
Voice messages	Not listedVoice notes are documented for WhatsApp only.	SupportedSend audio files as voice messages; inbound audio is transcribed.
Contact cards	SupportedSend a vCard over iMessage, SMS or WhatsApp.	Supportedcontact_file adds a vCard to the message.
Polls	Supported2 to 12 options; votes arrive as comms.poll.voted. Tap to vote on iOS 26 and later.	Not listedA helpdesk article lists polls among features, but no poll API is documented.
Chat backgrounds	BetaExperimental: photo or gradient backgrounds on lines that support them.	Not listed
Location sharing	PartialRead locations that contacts choose to share, with update webhooks; the API cannot request a share.	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	SupportedContact card API sets name and photo, with native name and photo sharing on supported lines.	Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls	PartialAnswer inbound FaceTime audio and video calls by API and stream audio; outbound calls not documented.	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status	Supportedsent, delivered and read events, plus a list of delivery attempts.	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check	SupportedChecks iMessage, RCS and WhatsApp for a phone number, or iMessage for an email.	PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedHosted lines; no Mac to run.	SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers	SupportedDedicated plan: $200 a month per number.	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers	SupportedFree and Plus plans run on a shared platform line.	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number	SupportedPort an existing number to a dedicated line; needs approval and a supported number.	PartialYou can port a US number in; your own Apple IDs are not accepted.
Line pooling	Not listed	SupportedSender pools balance new contacts across senders and match replies to the right one.
SMS fallback	SupportedAuto routing falls back to SMS only after a clear rejection.	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback	PartialAuto routing tries RCS for plain text on supported dedicated lines with carrier enablement.	SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging	SupportedDedicated lines can start conversations.	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
Calls on the iMessage number	PartialInbound phone and FaceTime calls to the line can be answered by API; outbound is not documented.	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS	SupportedChoose sms explicitly or let auto routing fall back to it.	SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS	PartialOne plain-text message to one number, on supported dedicated lines with carrier enablement.	SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp	SupportedSends from the number's WhatsApp Business account when WhatsApp is turned on for it.	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 supportedNot offered as a channel; the capability check accepts Apple ID emails for iMessage.	Not listed
Phone calls	PartialInbound cellular calls can be answered by API, but audio relay works only for FaceTime for now.	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
Apple Messages for Business	Not supportedNot offered; the site says Comms is distinct from Apple Messages for Business.	Not supportedNot offered; the helpdesk contrasts LoopMessage with it.
Unified channel API	SupportedOne send endpoint and message model for iMessage, RCS, WhatsApp and SMS.	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Not listedOnly a runnable Node.js example is published.	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	Supported	SupportedRetried up to 30 times over several hours.
Signed webhooks	SupportedHMAC-SHA256 in X-Osis-Signature.	PartialYou set an authorization header and verify it; no HMAC signature.
MCP server	SupportedHosted MCP server with OAuth or a scoped API key.	PartialDocumentation-only MCP server; no access to your account or messages.
Open source	Not listed	PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting	Not listed	Not listed
Local testing	Not listed	Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers	Not listed	Not listed
Event replay	PartialUp to six delivery retries and a delivery attempts list; no replay endpoint is documented.	PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry	Not listed	Not listed
No-code integrations	BetaHighLevel connector is a development preview; Marketplace approval is pending.	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
CRM integrations	Not listed	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
Built for AI agents
Agent framework	SupportedHosted agents with instructions, knowledge, handoff and MCP tool connections.	Not listed
Agent framework integrations	Not listed	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listed	Not listed
Human handoff	SupportedHandoff controls pause the hosted agent while a person replies in the team inbox.	PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
Audit logs	Not listed	PartialMessage, webhook and API request history kept; no account audit log found.
Message history API	SupportedList messages and conversations on your lines.	SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan	SupportedFree: shared platform line, 100 messages a day, no card.	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing	Supported	Supported
No per-message fees	SupportedFlat plans; AI usage and answered call minutes are billed separately.	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	Not listed	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 listedThe privacy policy mentions GDPR rights; no DPA was found.	SupportedHelpdesk says data is stored following GDPR.

Feature

Comms by Osis

LoopMessage

iMessage messaging

iMessage

Group chats

Groups of 2 to 31 people from a dedicated line with group support. Not on the shared line.

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

Group management

PartialCreate a group with its first message; adding or removing members is not documented.

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

Group name and photo

PartialName a group when you create it; group photos and renames are not documented.

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

Mentions

Not listed

Tapbacks

Classic tapbacks or custom emoji, add, replace or remove; reaction webhooks for inbound.

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

Threaded replies

reply_to_message_id replies inside an iMessage thread; text only.

reply_to_id on send; inbound webhooks carry a thread object.

Typing indicators

Show or hide typing dots on iMessage, RCS and WhatsApp.

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

Read receipts

Mark a conversation read to send a receipt; comms.message.read for one-to-one chats.

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

Edit and unsend

PartialUnsend within Apple's 2-minute window on supported lines. No edit endpoint; inbound edits fire events.

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

Message effects

Not listed

13 bubble and screen effects via the effect field.

Animated text effects

Not listed

Markup 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

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

Attachments

Up to 32 files and 9 MiB per message, sent as base64.

Up to 10 public HTTPS file URLs per message.

Live Photos

Not listed

Rich link previews

Not listed

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

Voice messages

Not listedVoice notes are documented for WhatsApp only.

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

Contact cards

Send a vCard over iMessage, SMS or WhatsApp.

contact_file adds a vCard to the message.

Polls

2 to 12 options; votes arrive as comms.poll.voted. Tap to vote on iOS 26 and later.

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

Chat backgrounds

BetaExperimental: photo or gradient backgrounds on lines that support them.

Not listed

Location sharing

PartialRead locations that contacts choose to share, with update webhooks; the API cannot request a share.

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

iMessage apps

Not listed

Live app cards

Not listed

Sender name and photo

Contact card API sets name and photo, with native name and photo sharing on supported lines.

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

FaceTime calls

PartialAnswer inbound FaceTime audio and video calls by API and stream audio; outbound calls not documented.

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

Delivery status

sent, delivered and read events, plus a list of delivery attempts.

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

iMessage availability check

Checks iMessage, RCS and WhatsApp for a phone number, or iMessage for an email.

PartialThrough LoopLookup, a separate LoopMessage service.

Focus and Notify Anyway

Not listed

Numbers and delivery

Managed lines

Hosted lines; no Mac to run.

Dedicated senders run on hardware LoopMessage rents to you.

Dedicated numbers

Dedicated plan: $200 a month per number.

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

Shared numbers

Free and Plus plans run on a shared platform line.

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

Bring your own number

Port an existing number to a dedicated line; needs approval and a supported number.

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

Line pooling

Not listed

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

SMS fallback

Auto routing falls back to SMS only after a clear rejection.

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

RCS fallback

PartialAuto routing tries RCS for plain text on supported dedicated lines with carrier enablement.

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

Outbound-first messaging

Dedicated lines can start conversations.

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

Calls on the iMessage number

PartialInbound phone and FaceTime calls to the line can be answered by API; outbound is not documented.

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

Other channels

SMS

Choose sms explicitly or let auto routing fall back to it.

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

RCS

PartialOne plain-text message to one number, on supported dedicated lines with carrier enablement.

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

Sends from the number's WhatsApp Business account when WhatsApp is turned on for it.

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

Not supportedNot offered

Not supportedPlanned on the roadmap, not available yet.

Slack

Not supported

Not listed

Not supportedNot offered as a channel; the capability check accepts Apple ID emails for iMessage.

Not listed

Phone calls

PartialInbound cellular calls can be answered by API, but audio relay works only for FaceTime for now.

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

Apple Messages for Business

Not supportedNot offered; the site says Comms is distinct from Apple Messages for Business.

Not supportedNot offered; the helpdesk contrasts LoopMessage with it.

Unified channel API

One send endpoint and message model for iMessage, RCS, WhatsApp and SMS.

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

Developer tools

REST API

TypeScript SDK

Not listedOnly a runnable Node.js example is published.

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

Webhooks

Retried up to 30 times over several hours.

Signed webhooks

HMAC-SHA256 in X-Osis-Signature.

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

MCP server

Hosted MCP server with OAuth or a scoped API key.

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

Open source

Not listed

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

Self-hosting

Not listed

Local testing

Not listed

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

Custom channel providers

Not listed

Event replay

PartialUp to six delivery retries and a delivery attempts list; no replay endpoint is documented.

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

OpenTelemetry

Not listed

No-code integrations

BetaHighLevel connector is a development preview; Marketplace approval is pending.

n8n, Zapier, Pipedream, HighLevel and LeadConnector.

CRM integrations

Not listed

HighLevel CRM and LeadConnector; no HubSpot or Salesforce found.

Built for AI agents

Agent framework

Hosted agents with instructions, knowledge, handoff and MCP tool connections.

Not listed

Agent framework integrations

Not listed

Streaming replies

Not listed

Agent group chats

Not listed

Human handoff

Handoff controls pause the hosted agent while a person replies in the team inbox.

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

Audit logs

Not listed

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

Message history API

List messages and conversations on your lines.

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

Plans and compliance

Free plan

Free: shared platform line, 100 messages a day, no card.

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

Public pricing

No per-message fees

Flat plans; AI usage and answered call minutes are billed separately.

Unlimited messages; plans cap unique active contacts per day.

Uptime SLA

Not listed

Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.

Isolated infrastructure

Not listed

A 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 listedThe privacy policy mentions GDPR rights; no DPA was found.

Helpdesk 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

Comms by Osis

Free on a shared line with 100 messages a day, Plus at $50 a month on a shared line, Dedicated at $200 a month per number with $0 setup, and custom Enterprise; AI usage is billed separately.

Pricing model: flat monthly per plan or dedicated line; AI usage and call minutes extra

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