Infobip vs Linq

Infobip supports 35 of the 77 features compared here, and Linq supports 63.

Feature comparison

Feature	Infobip	Linq
iMessage messaging
iMessage	Not supportedNo iMessage support	Supported
Group chats	Not supported	SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management	Not supported	SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo	Not supported	SupportedSet display_name and group_chat_icon on group chats.
Mentions	Not supported	SupportedGroup chats only. Notifies iMessage recipients even in a muted chat.
Tapbacks	Not supported	SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies	Not supported	Supportedreply_to with optional part_index. iMessage only.
Typing indicators	Not supported	SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts	Not supported	SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend	Not supported	PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects	Not supported	Supported11 screen and 4 bubble effects.
Animated text effects	Not supported	Supportedtext_decorations animations: big, small, shake, nod, explode, ripple, bloom, jitter.
Stickers	Not supported	SupportedPeel emoji or images onto messages, send stickers, or place them inline in text.
Formatted text	Not supported	SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments	Not supported	SupportedUp to 10MB by URL, 100MB with pre-upload.
Live Photos	Not supported	Not listed
Rich link previews	Not supported	Supportedlink parts render as rich previews on iMessage and RCS.
Voice messages	Not supported	SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards	Not supported	SupportedSend .vcf files as media parts.
Polls	Not supported	SupportedCreate, add options, vote and read tallies, with poll webhooks. Not as a chat's first message.
Chat backgrounds	Not supported	SupportedColor, animated or photo backgrounds, in direct and group chats.
Location sharing	Not supported	SupportedRequest, read and stop Find My shares. Live location is a $79/mo add-on on Pro.
iMessage apps	Not supported	SupportedPro plan. Cards from your own Messages extension, or Linq-hosted cards (Experiences).
Live app cards	Not supported	SupportedUpdate App Card replaces a delivered iMessage app or Experience card in place.
Sender name and photo	Not supported	SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls	Not supported	Not supportedDocs say the API does not place or answer calls.
Delivery status	Not supported	Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check	Not supported	Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway	Not supported	Not listed
Numbers and delivery
Managed lines	Not supportedNo iMessage support	Supported
Dedicated numbers	SupportedLong numbers, toll-free and short codes in 150+ countries	SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers	PartialShared test senders only in the free trial, sending to your verified number	SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number	PartialBYOC for voice over SIP trunks; SMS numbers have to be imported	Not listed
Line pooling	Not listed	SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback	Not supportedNo iMessage support; Messages API can fail over from RCS or WhatsApp to SMS	Supported
RCS fallback	Not supportedNo iMessage support	SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging	SupportedBusiness-initiated SMS; WhatsApp needs approved templates	SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number	Not supportedNo iMessage support	PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS	Supported	Supported
RCS	Supported	Supported
WhatsApp	Supported	BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram	PartialOnly through Answers chatbots and Conversations; no Telegram channel API	Not supportedNot offered
Slack	Not listed	Not supported
Email	Supported	Not supportedNot offered. iMessage can be sent to Apple ID email handles.
Phone calls	SupportedVoice API, IVR, SIP trunking and WebRTC	PartialAPI does not place or answer calls; it forwards inbound calls. Calling lives in the Linq Blue app.
Apple Messages for Business	Supported	Not listedAI context page mentions it, but no product page or docs were found.
Unified channel API	SupportedMessages API covers SMS, MMS, RCS, WhatsApp, Viber, AMB, Instagram, LINE, Messenger; not email	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	PartialNode SDK lives in Infobip's community GitHub org and covers SMS, WhatsApp and email only	Supported@linqapp/sdk
Python SDK	Supported	Supportedlinq-python
Other SDKs	SupportedJava, C#, PHP and Go API clients, plus iOS, Android, Flutter and React Native mobile SDKs	SupportedOfficial Go SDK.
CLI	Not listedNo CLI found in the docs or on Infobip's GitHub	Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks	SupportedInbound messages and delivery reports pushed to your endpoint	Supported
Signed webhooks	SupportedOptional HMAC signature in X-Hub-Signature; Basic, OAuth and mTLS also supported	SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server	SupportedRemote MCP servers per product (SMS, WhatsApp, RCS, Viber, voice, 2FA, docs); Provision MCP early access	Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source	Not supportedClosed platform; API clients and the MCP server framework are MIT-licensed	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	PartialWeb preview and simulator for agents and chatbots built in Infobip, not for your own code	Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers	SupportedOpen Channel plugs any external messaging platform into Conversations and Inbox	Not listed
Event replay	PartialWebhooks retry 20 times over 41.5 hours, then events are lost; message logs keep 48 hours	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	SupportedZapier integration; n8n nodes on Infobip's GitHub; Microsoft Power Automate	SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations	SupportedHubSpot, Salesforce, Dynamics 365, Zoho and SugarCRM integrations	SupportedVia Linq Blue: GoHighLevel, HubSpot and Salesforce.
Built for AI agents
Agent framework	SupportedAgentOS AI Agents: LLM agents with tools, MCP, orchestration and a test Quality center	PartialNo own framework. Maintains a Vercel Chat SDK adapter and OpenClaw and Hermes plugins.
Agent framework integrations	SupportedOfficial examples for OpenAI Agents SDK, LangGraph, Semantic Kernel, Spring AI; Bot Framework adapter	SupportedLinq-maintained Vercel Chat SDK adapter, plus OpenClaw and Hermes Agent plugins.
Streaming replies	BetaVoice only, early access: realtime speech-to-speech AI agents on calls; no text streaming found	Not supportedDocs say the Chat SDK adapter buffers streams into one final message.
Agent group chats	PartialGroup MMS on US 10DLC numbers makes multi-person threads; AgentOS subagents are internal only	Not listed
Human handoff	SupportedAI agents and chatbots hand off to human agents in Conversations	Not listed
Audit logs	SupportedWeb interface user activity, searchable and exportable by API	SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API	SupportedConversations API lists thread messages; channel log APIs keep 48 hours	Supported
Plans and compliance
Free plan	Partial60-day free trial, no card, up to 100 messages per channel to your verified number	SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing	SupportedIndicative rates by country and channel	SupportedPro from $260/mo. Enterprise is custom.
No per-message fees	Not supportedBilled per message	Supported
Uptime SLA	Not listedNo SLA figure in the public terms, which promise reasonable skill and care	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	Supported	SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR	SupportedDPA covers GDPR and UK GDPR, with EU standard contractual clauses	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 Infobip if you need bring your own number, Telegram, email and Apple Messages for Business.

Choose Linq if you need iMessage, group chats, group management and group name and photo.

Frequently asked questions

• Photon vs Infobip

• 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