Comms by Osis vs Linq

Comms by Osis supports 43 of the 77 features compared here, and Linq supports 63.

Feature comparison

Feature	Comms by Osis	Linq
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.	SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management	PartialCreate a group with its first message; adding or removing members is not documented.	SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo	PartialName a group when you create it; group photos and renames are not documented.	SupportedSet display_name and group_chat_icon on group chats.
Mentions	Not listed	SupportedGroup chats only. Notifies iMessage recipients even in a muted chat.
Tapbacks	SupportedClassic tapbacks or custom emoji, add, replace or remove; reaction webhooks for inbound.	SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies	Supportedreply_to_message_id replies inside an iMessage thread; text only.	Supportedreply_to with optional part_index. iMessage only.
Typing indicators	SupportedShow or hide typing dots on iMessage, RCS and WhatsApp.	SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts	SupportedMark a conversation read to send a receipt; comms.message.read for one-to-one chats.	SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend	PartialUnsend within Apple's 2-minute window on supported lines. No edit endpoint; inbound edits fire events.	PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects	Not listed	Supported11 screen and 4 bubble effects.
Animated text effects	Not listed	Supportedtext_decorations animations: big, small, shake, nod, explode, ripple, bloom, jitter.
Stickers	Not listed	SupportedPeel emoji or images onto messages, send stickers, or place them inline in text.
Formatted text	Not listed	SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments	SupportedUp to 32 files and 9 MiB per message, sent as base64.	SupportedUp to 10MB by URL, 100MB with pre-upload.
Live Photos	Not listed	Not listed
Rich link previews	Not listed	Supportedlink parts render as rich previews on iMessage and RCS.
Voice messages	Not listedVoice notes are documented for WhatsApp only.	SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards	SupportedSend a vCard over iMessage, SMS or WhatsApp.	SupportedSend .vcf files as media parts.
Polls	Supported2 to 12 options; votes arrive as comms.poll.voted. Tap to vote on iOS 26 and later.	SupportedCreate, add options, vote and read tallies, with poll webhooks. Not as a chat's first message.
Chat backgrounds	BetaExperimental: photo or gradient backgrounds on lines that support them.	SupportedColor, animated or photo backgrounds, in direct and group chats.
Location sharing	PartialRead locations that contacts choose to share, with update webhooks; the API cannot request a share.	SupportedRequest, read and stop Find My shares. Live location is a $79/mo add-on on Pro.
iMessage apps	Not listed	SupportedPro plan. Cards from your own Messages extension, or Linq-hosted cards (Experiences).
Live app cards	Not listed	SupportedUpdate App Card replaces a delivered iMessage app or Experience card in place.
Sender name and photo	SupportedContact card API sets name and photo, with native name and photo sharing on supported lines.	SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls	PartialAnswer inbound FaceTime audio and video calls by API and stream audio; outbound calls not documented.	Not supportedDocs say the API does not place or answer calls.
Delivery status	Supportedsent, delivered and read events, plus a list of delivery attempts.	Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check	SupportedChecks iMessage, RCS and WhatsApp for a phone number, or iMessage for an email.	Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedHosted lines; no Mac to run.	Supported
Dedicated numbers	SupportedDedicated plan: $200 a month per number.	SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers	SupportedFree and Plus plans run on a shared platform line.	SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number	SupportedPort an existing number to a dedicated line; needs approval and a supported number.	Not listed
Line pooling	Not listed	SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback	SupportedAuto routing falls back to SMS only after a clear rejection.	Supported
RCS fallback	PartialAuto routing tries RCS for plain text on supported dedicated lines with carrier enablement.	SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging	SupportedDedicated lines can start conversations.	SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number	PartialInbound phone and FaceTime calls to the line can be answered by API; outbound is not documented.	PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS	SupportedChoose sms explicitly or let auto routing fall back to it.	Supported
RCS	PartialOne plain-text message to one number, on supported dedicated lines with carrier enablement.	Supported
WhatsApp	SupportedSends from the number's WhatsApp Business account when WhatsApp is turned on for it.	BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram	Not supportedNot offered	Not supportedNot offered
Slack	Not supported	Not supported
Email	Not supportedNot offered as a channel; the capability check accepts Apple ID emails for iMessage.	Not supportedNot offered. iMessage can be sent to Apple ID email handles.
Phone calls	PartialInbound cellular calls can be answered by API, but audio relay works only for FaceTime for now.	PartialAPI does not place or answer calls; it forwards inbound calls. Calling lives in the Linq Blue app.
Apple Messages for Business	Not supportedNot offered; the site says Comms is distinct from Apple Messages for Business.	Not listedAI context page mentions it, but no product page or docs were found.
Unified channel API	SupportedOne send endpoint and message model for iMessage, RCS, WhatsApp and SMS.	PartialiMessage, RCS and SMS share one API. WhatsApp is a separate API with its own keys and SDKs.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Not listedOnly a runnable Node.js example is published.	Supported@linqapp/sdk
Python SDK	Not listed	Supportedlinq-python
Other SDKs	Not listed	SupportedOfficial Go SDK.
CLI	Not listed	Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks	Supported	Supported
Signed webhooks	SupportedHMAC-SHA256 in X-Osis-Signature.	SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server	SupportedHosted MCP server with OAuth or a scoped API key.	Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source	Not listed	PartialSDKs, CLI and adapters are Apache-2.0 or MIT on GitHub. The messaging platform is closed.
Self-hosting	Not listed	Not supportedLinq describes itself as fully managed, in contrast to self-hosted options.
Local testing	Not listed	Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers	Not listed	Not listed
Event replay	PartialUp to six delivery retries and a delivery attempts list; no replay endpoint is documented.	PartialRetries for 30 minutes; after that, re-fetch chats or ask Linq for a manual replay.
OpenTelemetry	Not listed	PartialW3C trace IDs on every response and webhook for OTel backends. No export of Linq spans by default.
No-code integrations	BetaHighLevel connector is a development preview; Marketplace approval is pending.	SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations	Not listed	SupportedVia Linq Blue: GoHighLevel, HubSpot and Salesforce.
Built for AI agents
Agent framework	SupportedHosted agents with instructions, knowledge, handoff and MCP tool connections.	PartialNo own framework. Maintains a Vercel Chat SDK adapter and OpenClaw and Hermes plugins.
Agent framework integrations	Not listed	SupportedLinq-maintained Vercel Chat SDK adapter, plus OpenClaw and Hermes Agent plugins.
Streaming replies	Not listed	Not supportedDocs say the Chat SDK adapter buffers streams into one final message.
Agent group chats	Not listed	Not listed
Human handoff	SupportedHandoff controls pause the hosted agent while a person replies in the team inbox.	Not listed
Audit logs	Not listed	SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API	SupportedList messages and conversations on your lines.	Supported
Plans and compliance
Free plan	SupportedFree: shared platform line, 100 messages a day, no card.	SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing	Supported	SupportedPro from $260/mo. Enterprise is custom.
No per-message fees	SupportedFlat plans; AI usage and answered call minutes are billed separately.	Supported
Uptime SLA	Not listed	SupportedContractual SLAs on the Enterprise plan; marketing cites 99.95%
Isolated infrastructure	Not listed	SupportedDedicated lines across 4 data centers on paid plans; Hobby uses a shared line
SOC 2 Type II	Not listed	SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR	Not listedThe privacy policy mentions GDPR rights; no DPA was found.	SupportedDPA covers GDPR and UK GDPR, with Standard Contractual Clauses.

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 Comms by Osis if you need FaceTime calls, bring your own number and human handoff.

Choose Linq if you need mentions, message effects, animated text effects and stickers.

Frequently asked questions

• Photon vs Comms by Osis
• Blooio vs Comms by Osis
• Comms by Osis vs Sendblue
• Comms by Osis vs Zernio
• Comms by Osis vs LoopMessage
• Blue Reacher vs Comms by Osis
• Chert vs Comms by Osis
• Comms by Osis vs Miss Blue
• Bland vs Comms by Osis

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