Inkbox vs LoopMessage

Inkbox supports 45 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

Feature	Inkbox	LoopMessage
iMessage messaging
iMessage	SupportedShared router service on every plan, or a dedicated line from the Startup plan.	Supported
Group chats	SupportedDedicated lines only, 2 to 8 remote participants. Shared service is 1:1.	SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management	PartialCreate a group by sending to 2 to 8 numbers. No add or remove member API in V1.	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, replace and remove 7 tapbacks including eyes; inbound tapbacks arrive by webhook.	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies	Supportedreply_to_message_id in 1:1 and group chats, with thread reads. Falls back to a plain reply.	Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators	PartialSend only, in 1:1 chats. Groups and inbound typing events are not supported.	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts	PartialSend read receipts in 1:1 chats. No read status for your own sent messages is documented.	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	Supported4 bubble and 9 full-screen send styles, in 1:1 and dedicated-line groups.	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	SupportedOne media item per message, uploads up to 10 MiB. No media before the recipient's first reply.	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 listed	SupportedSend audio files as voice messages; inbound audio is transcribed.
Contact cards	PartialThe router sends the agent's contact card on connect. Sending other vCards is not documented.	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	SupportedDedicated lines share the identity's display name and avatar automatically.	Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls	Not listedCalls run over iMessage lines, but the docs do not say whether they are FaceTime.	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status	Supportedimessage.sent, imessage.delivered and imessage.delivery_failed webhooks, per recipient in groups.	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check	SupportedReturns iMessage, SMS or RCS for any E.164 number.	PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedShared router lines and dedicated lines run by Inkbox. No Mac needed.	SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers	SupportedStartup plan includes one dedicated iMessage number. VoIP numbers for calls and SMS from Developer.	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers	SupportedFree and paid plans include shared iMessage. The human must text the router first.	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number	Not listed	PartialYou can port a US number in; your own Apple IDs are not accepted.
Line pooling	BetaOrganization-owned shared iMessage pools, beta and by request only.	SupportedSender pools balance new contacts across senders and match replies to the right one.
SMS fallback	SupportedInkbox tries iMessage first and can fall back to SMS; was_downgraded marks it.	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback	PartialDocs describe SMS fallback, and the service field can report rcs. The transport cannot be chosen.	SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging	PartialDedicated lines can start chats, up to 40 new recipients a day. Shared service needs the human to text first.	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
Calls on the iMessage number	SupportedAgents place and receive voice calls over shared and dedicated iMessage lines.	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS	SupportedSMS and MMS on dedicated VoIP numbers, US and Canada included. Group MMS is beta.	SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS	PartialOnly as a transport reported on iMessage lines; not a channel you can pick.	SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp	Not supportedNot offered	SupportedAdd-on, +$10/mo, on the same phone number and API.
Telegram	Not supported	Not supportedPlanned on the roadmap, not available yet.
Slack	BetaSlack is in beta: read, reply, files and retained history search.	Not listed
Email	SupportedEach identity gets a mailbox, with custom domains and IMAP/SMTP access.	Not listed
Phone calls	SupportedInbound and outbound calls with your own WebSocket agent or Inkbox Voice AI (beta).	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	PartialOne identity and one webhook subscription across channels, but separate APIs per channel.	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Supported@inkbox/sdk	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Python SDK	Supportedinkbox on PyPI	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Other SDKs	SupportedRust SDK (inkbox crate).	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
CLI	Supported@inkbox/cli	Not listed
Webhooks	Supported	SupportedRetried up to 30 times over several hours.
Signed webhooks	SupportedHMAC-SHA256 with a per-identity signing key.	PartialYou set an authorization header and verify it; no HMAC signature.
MCP server	SupportedRemote Streamable HTTP endpoint at inkbox.ai/mcp, with a separate ChatGPT endpoint.	PartialDocumentation-only MCP server; no access to your account or messages.
Open source	PartialSDK, CLI, skills and examples are MIT on GitHub. The service is closed.	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	SupportedDelivery log with replay. Incoming-call and Slack deliveries cannot be replayed.	PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry	Not listed	Not listed
No-code integrations	Not listed	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	PartialIdentity layer with contact memories across email, texts and calls. No conversation framework.	Not listed
Agent framework integrations	SupportedPlugins for Hermes Agent, OpenClaw, OpenCode, Codex, Claude Code and DeepSeek Harness.	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listedAgents can reach each other over A2A tasks, but not in group chats.	Not listed
Human handoff	PartialPeople can reply from the Console, and Voice AI can transfer a call. No handoff controls for agents.	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 and read conversations and threads, with search on texts and email.	SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan	SupportedFree: 3 identities, shared iMessage up to 2,000 messages a month and 3 recipients at a time.	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing	Supported	Supported
No per-message fees	PartialiMessage is capped per plan with no per-message fee. Extra SMS/MMS and call minutes cost $0.03 each.	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	PartialDedicated iMessage infrastructure is listed for Enterprise only.	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 DPA names the CCPA only; GDPR is not mentioned.	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

Which should you choose?

Choose Inkbox if you need sender name and photo, Slack, email and CLI.

Choose LoopMessage if you need group name and photo, edit and unsend, animated text effects and stickers.

Frequently asked questions

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

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