LoopMessage vs Sendblue

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

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

Sendblue

iMessage API and CRM texting for sales and agents
Starting price
$100/month per line
Free plan
Free sandbox: shared number, up to 10 verified contacts, no webhooks

LoopMessage supports 53 of the 77 features compared here, and Sendblue supports 58.

Feature comparison

FeatureLoopMessageSendblue
iMessage messaging
iMessage
Supported
Supported
Group chats
SupportedSend and receive in iMessage groups; not available in the sandbox.
BetaGroup API is in beta on select plans. AI Agent plan can only reply in existing groups.
Group management
SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
BetaAdd and remove participants in iMessage groups via the beta groups API.
Group name and photo
SupportedSet group name (32 characters max) and photo with PATCH.
SupportedRename groups and set group photos on supported lines.
Mentions
Not listed
Not listed
Tapbacks
SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
PartialSend classic tapbacks or any emoji. No inbound reaction events documented.
Threaded replies
Supportedreply_to_id on send; inbound webhooks carry a thread object.
Supportedreply_to on V2 iMessage lines, in direct and group chats.
Typing indicators
SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
SupportedSend and receive. iMessage 1:1 only, not in groups.
Read receipts
PartialYou can mark chats read; no read event is documented for your outbound messages.
PartialCan mark chats read (1:1). Outbound statuses stop at DELIVERED, with no read status.
Edit and unsend
SupportedEdit within 15 minutes, unsend within 2 minutes of sending.
Not supportedDocs say editing is not supported via API and delete does not unsend.
Message effects
Supported13 bubble and screen effects via the effect field.
Supported13 send_style values.
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.
Not listed
Formatted text
SupportedBold, italic, underline, strikethrough and text sizes in iMessage.
Not listed
Attachments
SupportedUp to 10 public HTTPS file URLs per message.
SupportedUp to 100MB on iMessage, 5MB on SMS.
Live Photos
Not listed
Not listed
Rich link previews
SupportedLinks get rich previews by default; preview: false sends plain text.
PartialDocs say links expand only after the recipient saves your contact.
Voice messages
SupportedSend audio files as voice messages; inbound audio is transcribed.
SupportedSend .caf files to render as inline voice notes.
Contact cards
Supportedcontact_file adds a vCard to the message.
SupportedSend .vcf files via media_url.
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.
SupportedFind My request, read and live watch. Dedicated iMessage lines only.
iMessage apps
Not listed
SupportedApp Cards for your own Messages extension. V2 lines, not on the free plan.
Live app cards
Not listed
PartialUpdates go out as new messages in the same App Card session; Sendblue says the original is not edited.
Sender name and photo
Not listedDocs suggest sending a vCard so recipients see your name and photo.
SupportedName and Photo Sharing profile per line, shared into direct iMessage chats.
FaceTime calls
Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
PartialOutbound FaceTime audio over WebRTC (Agora). Needs a purchased FaceTime line.
Delivery status
Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
SupportedStatus callbacks from REGISTERED through SENT or DELIVERED.
iMessage availability check
PartialThrough LoopLookup, a separate LoopMessage service.
SupportedLookup API checks a phone number or email for iMessage.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedDedicated senders run on hardware LoopMessage rents to you.
Supported
Dedicated numbers
SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Supported
Shared numbers
SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
SupportedFree sandbox uses a shared number with verified contacts only.
Bring your own number
PartialYou can port a US number in; your own Apple IDs are not accepted.
PartialOnly by porting the number in, which adds 3 to 5 days.
Line pooling
SupportedSender pools balance new contacts across senders and match replies to the right one.
SupportedNumber pooling with sticky sending. Automatic line selection needs account enablement.
SMS fallback
SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
Supported
RCS fallback
SupportedSame add-on uses RCS instead of SMS when the device supports it.
SupportediMessage, then RCS, then SMS. RCS on V2 lines.
Outbound-first messaging
PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
SupportedFull outbound on Enterprise or Blue Ocean; Free and AI Agent plans are inbound-first
Calls on the iMessage number
PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
SupportedDashboard calls and FaceTime from the texting number; API calls via your Twilio caller ID.
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.
SupportedV2 lines.
WhatsApp
SupportedAdd-on, +$10/mo, on the same phone number and API.
Not supportedNot offered
Telegram
Not supportedPlanned on the roadmap, not available yet.
Not supported
Slack
Not listed
Not listed
Email
Not listed
Not supportedNot offered. iMessage can be sent to Apple ID email addresses.
Phone calls
PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
PartialNo native calling API. Dashboard calls, outbound via your Twilio caller ID, inbound forwarding.
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.
SupportedOne API for iMessage, RCS and SMS, the only channels offered.
Developer tools
REST API
Supported
Supported
TypeScript SDK
PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Supportedsendblue on npm.
Python SDK
PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Supportedsendblue on PyPI.
Other SDKs
PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
PartialGo, Rust and Ruby packages, listed as community packages.
CLI
Not listed
Supported@sendblue/cli: signup, messaging, contacts and webhooks.
Webhooks
SupportedRetried up to 30 times over several hours.
Supported
Signed webhooks
PartialYou set an authorization header and verify it; no HMAC signature.
PartialSends your shared secret in an sb-signing-secret header. No HMAC signature.
MCP server
PartialDocumentation-only MCP server; no access to your account or messages.
Supportedsendblue-api-mcp via npx.
Open source
PartialOnly the n8n node is MIT on GitHub; the platform is closed.
PartialSDKs and CLI are MIT or Apache-2.0 on GitHub. The messaging platform is closed.
Self-hosting
Not listed
Not listedSold as a hosted service on Sendblue's Apple devices; self-hosting is not mentioned.
Local testing
Not listedThe sandbox needs a real iPhone or Mac to message it.
Not listed
Custom channel providers
Not listed
Not listed
Event replay
PartialWebhook history API to fetch past events; no replay call.
PartialNo replay. Docs say to repair gaps by listing messages updated since a timestamp.
OpenTelemetry
Not listed
Not listed
No-code integrations
Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
SupportedZapier, Make and GoHighLevel. Docs FAQ says n8n resources are coming soon.
CRM integrations
SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
SupportedGoHighLevel, HubSpot, Salesforce, Close and Monday.com.
Built for AI agents
Agent framework
Not listed
PartialNo own framework. Maintains a Vercel Chat SDK adapter.
Agent framework integrations
Not listed
SupportedSendblue-maintained Vercel Chat SDK adapter.
Streaming replies
Not listed
Not supportedDocs say message editing is not supported via the API.
Agent group chats
Not listed
BetaA line can add another of your own dedicated lines to a group, via the beta groups API.
Human handoff
PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
SupportedShared team inboxes with assignment, and agents that escalate to a rep.
Audit logs
PartialMessage, webhook and API request history kept; no account audit log found.
PartialSecurity page says all API requests are logged. No customer-facing audit log documented.
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.
SupportedFree sandbox: shared number, up to 10 verified contacts, no webhooks.
Public pricing
Supported
SupportedAI Agent plan at $100/mo per line. Enterprise is custom.
No per-message fees
SupportedUnlimited messages; plans cap unique active contacts per day.
Supported
Uptime SLA
Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Supported99.99% uptime SLA on the Enterprise plan
Isolated infrastructure
SupportedA dedicated sender's number and server are allocated to you alone.
SupportedA dedicated HIPAA instance for HIPAA customers
SOC 2 Type II
Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
SupportedSOC 2 Type II, report on request.
GDPR
SupportedHelpdesk says data is stored following GDPR.
SupportedPrivacy policy says Sendblue adheres to GDPR. DPAs on request.

Checked on each provider's own site and docs on 2026-10-25. “Not listed” means the provider does not mention it.

Pricing

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

Sendblue

A free sandbox for testing, the AI Agent plan at $100 per line per month for inbound-first use, and custom Enterprise pricing for outbound and volume.

Pricing model: flat per line, no per-message fees

Source

Which should you choose?

Choose LoopMessage if you need edit and unsend, animated text effects, stickers and formatted text.

Choose Sendblue if you need iMessage apps, live app cards, sender name and photo and FaceTime calls.

Frequently asked questions