Bland vs LoopMessage

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

Bland

Voice AI platform with SMS, RCS and branded iMessage agents
Starting price
Custom (iMessage is Enterprise only); SMS from $29.99/month on the Agent Phone Plan
Free plan
Start plan: free, with credits and an inbound number, for voice

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

Bland supports 46 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

FeatureBlandLoopMessage
iMessage messaging
iMessage
PartialEnterprise plans only; Bland provisions an iMessage-capable number on request
Supported
Group chats
Not listed
SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management
Not listed
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 and receive, per the iMessage guide; no API field, the agent decides
SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies
Not listed
Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators
SupportedListed in the iMessage guide
SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts
Supported
PartialYou can mark chats read; no read event is documented for your outbound messages.
Edit and unsend
Not listedAPI deletes stored messages from a conversation; unsend on the device is not mentioned
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
SupportedGuide lists text effects; which effects and how they are set is not documented
SupportedMarkup for shake, nod, explode, ripple, bloom and jitter.
Stickers
SupportedLive Stickers, per the iMessage guide
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
SupportedPhotos, videos, PDFs and spreadsheets both ways; agents can generate files to send
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
SupportedSend and receive voice memos; inbound memos are transcribed
SupportedSend audio files as voice messages; inbound audio is transcribed.
Contact cards
Not listed
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
SupportedBranded contact with your company name and profile image
Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls
Not listed
Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status
SupportedGuide lists delivery status; messages carry sent, delivered, read or failed
Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check
Not listed
PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedBland provisions iMessage-capable numbers for Enterprise accounts
SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers
SupportedAgent Phone Plan includes one dedicated US number; Enterprise numbers by request
SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers
PartialFree credits call from a shared Bland number; texting needs your own number
SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number
PartialYour own Twilio numbers or SIP trunks for voice and SMS; not documented for iMessage
PartialYou can port a US number in; your own Apple IDs are not accepted.
Line pooling
PartialCustom Dialing picks numbers from a pool for outbound calls only
SupportedSender pools balance new contacts across senders and match replies to the right one.
SMS fallback
SupportedUses the richest channel the recipient supports and falls back to SMS
SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback
Not listedDocs say Bland picks the richest channel; an iMessage to RCS order is not stated
SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging
SupportedSend SMS creates or resumes a conversation on any channel
PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
Calls on the iMessage number
Not listed
PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS
SupportedEnterprise plans and the Agent Phone Plan; US numbers need A2P registration
SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS
PartialEnterprise only, enabled by your account executive
SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp
PartialEnterprise only; a channel value on the Messaging API, no setup guide in the docs
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 supportedNot a messaging channel; Slack is listed only as a tool integration
Not listed
Email
Not supportedNot offered as a messaging channel
Not listed
Phone calls
SupportedCore product: inbound and outbound AI phone calls, plus SIP
PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.
Apple Messages for Business
Not listedProduct page says Bland handles Apple Business Messaging registration; docs describe numbers
Not supportedNot offered; the helpdesk contrasts LoopMessage with it.
Unified channel API
PartialSMS, RCS, WhatsApp and iMessage share the /v1/sms endpoints; calls use a separate API
SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API
Supported
Supported
TypeScript SDK
PartialDocs list a Web Agent SDK for browser voice and a TTS library; no messaging SDK
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
Supportedbland-cli on npm
Not listed
Webhooks
SupportedMessage and status webhooks per number or per request, with a channel field
SupportedRetried up to 30 times over several hours.
Signed webhooks
SupportedHMAC-SHA256 in X-Webhook-Signature; asymmetric JWT signing on Enterprise
PartialYou set an authorization header and verify it; no HMAC signature.
MCP server
SupportedHosted MCP server; personal agents connected to it can place calls and send texts
PartialDocumentation-only MCP server; no access to your account or messages.
Open source
Not supportedClosed platform
PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting
PartialEnterprise: your own VPC, on-premises or air-gapped deployments
Not listed
Local testing
SupportedPathway Chat API and Testbed run agent conversations without a phone
Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers
PartialBring your own Twilio account or SIP carrier for telephony
Not listed
Event replay
PartialAutomatic webhook retries; resend endpoint for call webhooks; SMS delivery log readable
PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedZapier, Make and Pipedream on the integrations page
Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
CRM integrations
SupportedHubSpot and Salesforce
SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
Built for AI agents
Agent framework
SupportedPathways, personas and versioned agents drive voice and every messaging channel
Not listed
Agent framework integrations
PartialMCP guides for OpenClaw, Poke, Meta Muse and coding agents; no LangChain or Vercel AI SDK
Not listed
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listed
Human handoff
SupportedHand a thread to a human and resume the agent, by API or a pathway node
PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.
Audit logs
PartialEnterprise feature, not yet available for all accounts
PartialMessage, webhook and API request history kept; no account audit log found.
Message history API
SupportedList and read conversations with messages and delivery status
SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan
PartialFree Start plan with credits is for voice; messaging needs Agent Phone Plan or Enterprise
SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing
PartialVoice plans and SMS rates are public; iMessage, RCS and WhatsApp prices are not
Supported
No per-message fees
PartialSMS costs $0.02 per message; the Agent Phone Plan is flat with a 100 texts a day cap
SupportedUnlimited messages; plans cap unique active contacts per day.
Uptime SLA
SupportedPricing page lists a 99.9% uptime SLA on every plan
Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Isolated infrastructure
PartialEnterprise customers run on their own isolated infrastructure
SupportedA dedicated sender's number and server are allocated to you alone.
SOC 2 Type II
SupportedSOC 2 Type II, independently audited
Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
GDPR
SupportedGDPR compliant, with a DPA in enterprise contracts
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

Bland

Voice plans are Start (free, $0.14 a minute), Build ($299 a month) and Scale ($499 a month); SMS is $0.02 per message; the Agent Phone Plan is $29.99 a month for one number; iMessage, RCS and WhatsApp need a custom Enterprise contract.

Pricing model: per-minute voice, per-message SMS, custom Enterprise contracts

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

Which should you choose?

Choose Bland if you need sender name and photo, CLI, self-hosting and local testing.

Choose LoopMessage if you need group chats, group management, group name and photo and threaded replies.

Frequently asked questions