AgentPhone vs LoopMessage

AgentPhone supports 44 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

Feature	AgentPhone	LoopMessage
iMessage messaging
iMessage	SupportediMessage lines are a separate number type (type=imessage).	Supported
Group chats	SupportediMessage groups arrive as one conversation with roster and sender; reply to the group id.	SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management	PartialStart a new group by listing recipients and rename it; adding or removing members is not documented.	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
Group name and photo	PartialGroup name can be set by API; the group icon is only readable.	SupportedSet group name (32 characters max) and photo with PATCH.
Mentions	Not listed	Not listed
Tapbacks	SupportedSix classic tapbacks, custom emoji on newer lines; inbound reactions via agent.reaction.	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies	Supportedreply_to_message_id; also on WhatsApp.	Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators	SupportedSend only, best-effort, auto-expires after a few seconds.	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts	Not listedThe pricing page mentions read receipts; no API or webhook for them 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	Supported12 screen and bubble effects via send_style.	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	SupportedImages, video and files by URL; several images arrive as a carousel on iMessage.	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	SupportedvCard files can be sent as media (listed as a supported MMS type).	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	SupportedSet or remove a background image per iMessage conversation.	Not listed
Location sharing	Not listedThe API has location endpoints returning coordinates per number, but their use is not described.	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	PartialContact card sets a display name and avatar on the iMessage number; $250/month line only.	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	PartialMessages carry a status and failure reason; no delivery or read webhooks are documented.	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check	SupportedLive check of iMessage, SMS and RCS reachability for a number before sending.	PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportediMessage lines are ordered through the API and run by AgentPhone.	SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers	SupportedUS and Canada numbers at $3/month; dedicated iMessage lines at $250/month.	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers	Not listed	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	Not listed	SupportedSender pools balance new contacts across senders and match replies to the right one.
SMS fallback	SupportedFalls back to SMS/MMS when iMessage is not available.	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback	SupportediMessage-capable numbers deliver over RCS or SMS to non-Apple recipients.	SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging	PartialOutbound iMessage lines: 50 new contacts a day per line; inbound-only lines do not start chats; SMS needs 10DLC.	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	SupportedSMS and MMS; inbound works at once, outbound needs 10DLC.	SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS	BetaRCS Business Messaging is beta and concierge-onboarded: branded sender, quick-reply chips.	SupportedSet channel to rcs; needs the SMS/RCS add-on.
WhatsApp	BetaBeta, enabled per account. Connect your own WhatsApp Business Account; Meta bills you.	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 supported	Not listed
Email	Not supported	Not listed
Phone calls	SupportedInbound and outbound calls in webhook mode or hosted AI mode; also browser web calls.	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	SupportedOne send endpoint for SMS, MMS, iMessage, RCS and WhatsApp; one agent.message webhook incl. voice.	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Supportednpm install agentphone	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Python SDK	Supportedpip install agentphone	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Other SDKs	Not listedDocs list only TypeScript and Python; an agentphone-go repo holds only a placeholder README.	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
CLI	Not listedNo own CLI found; numbers can be provisioned through the Stripe Projects CLI.	Not listed
Webhooks	SupportedProject default webhook with per-agent overrides.	SupportedRetried up to 30 times over several hours.
Signed webhooks	SupportedHMAC-SHA256 over timestamp and body, with a timestamp header for replay protection.	PartialYou set an authorization header and verify it; no HMAC signature.
MCP server	SupportedHosted MCP server (mcp.agentphone.ai) and npm package agentphone-mcp.	PartialDocumentation-only MCP server; no access to your account or messages.
Open source	Not supportedClosed platform. The MCP server and framework integrations are MIT-licensed on GitHub.	PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting	Not supportedHosted cloud service only	Not listed
Local testing	PartialBrowser web calls test a voice agent without a phone number; no message simulator found.	Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers	Not listed	Not listed
Event replay	PartialFailed webhooks retry 5 times over about 20 hours; deliveries can be listed but not replayed.	PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry	Not listed	Not listed
No-code integrations	PartialAgentPhone block in Sim's no-code workflow builder; no Zapier, Make, n8n or GoHighLevel found.	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	SupportedHosted voice mode runs calls from a system prompt; conversation state rides along in webhooks.	Not listed
Agent framework integrations	SupportedVercel Chat SDK adapter, LangChain, CrewAI and OpenAI Agents SDK tools, Google ADK guide.	Not listed
Streaming replies	PartialVoice only: NDJSON streamed webhook replies start speech on the first chunk.	Not listed
Agent group chats	PartialAgents can create and take part in iMessage groups; agent-to-agent groups are not described.	Not listed
Human handoff	PartialVoice only: cold transfer of a call to a transferNumber, by the AI or your webhook.	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	SupportedConversations with paginated messages and custom metadata; call transcripts.	SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan	Partial$5 starting credit, no card. Outbound calls need a top-up first.	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing	Supported	Supported
No per-message fees	PartialiMessage lines and WhatsApp have no per-message charge; SMS is $0.02 a segment, MMS $0.03.	SupportedUnlimited messages; plans cap unique active contacts per day.
Uptime SLA	Not supportedTerms promise no uptime; SLAs only if set in an order or separate agreement.	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Isolated infrastructure	Not listedSub-accounts isolate agents, numbers and data per client; no dedicated infrastructure offer found.	SupportedA dedicated sender's number and server are allocated to you alone.
SOC 2 Type II	PartialSOC 2 Type I report as of July 30, 2026; Type II examination in progress.	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
GDPR	SupportedPrivacy policy sets out GDPR legal bases for processing.	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 AgentPhone if you need chat backgrounds, sender name and photo, local testing and agent framework.

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

Frequently asked questions

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

• 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