Claw Messenger vs LoopMessage

Claw Messenger supports 32 of the 77 features compared here, and LoopMessage supports 53.

Feature comparison

Feature	Claw Messenger	LoopMessage
iMessage messaging
iMessage	SupportedOnly phone numbers registered to the account can reach the agent	Supported
Group chats	PartialGrowth plan and up; every participant must be a registered number	SupportedSend and receive in iMessage groups; not available in the sandbox.
Group management	PartialCreate a group by sending to several numbers; no add or remove member calls	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.
Group name and photo	Not listedDocs only describe receiving group rename events	SupportedSet group name (32 characters max) and photo with PATCH.
Mentions	Not listed	Not listed
Tapbacks	SupportedSend and receive, including custom emoji reactions	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.
Threaded replies	SupportedreplyTo on send; inbound messages carry replyTo	Supportedreply_to_id on send; inbound webhooks carry a thread object.
Typing indicators	Supported	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.
Read receipts	SupportedMark as read on send; read status events on receive	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	Not listed	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	SupportedGeneric media attachments from HTTPS URLs	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 supportedFAQ: native voice-note bubbles are not verified; audio goes as a plain file	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	Not listed	Not listedDocs suggest sending a vCard so recipients see your name and photo.
FaceTime calls	Not supportedFAQ: no voice calls; text and media only	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.
Delivery status	Supportedaccepted, delivered, read and failed status events	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.
iMessage availability check	Not listedRouting picks the channel automatically; no reachability check is documented	PartialThrough LoopLookup, a separate LoopMessage service.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedProvider runs the line; agents run on Linux, Docker, Windows or cloud	SupportedDedicated senders run on hardware LoopMessage rents to you.
Dedicated numbers	SupportedAgency tier ($199/month per subtenant); self-serve uses shared numbers	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.
Shared numbers	SupportedSelf-serve plans send from a shared number that may change between messages	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.
Bring your own number	Not listedFAQ says numbers come from a pool; bringing your own is not mentioned	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	SupportediMessage with automatic RCS and SMS fallback	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.
RCS fallback	Supported	SupportedSame add-on uses RCS instead of SMS when the device supports it.
Outbound-first messaging	SupportedSelf-serve plans start up to 20 new conversations per rolling 24 hours	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.
Calls on the iMessage number	Not supportedFAQ: voice calls are not supported	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.
Other channels
SMS	Supportedservice: SMS on send	SupportedSet channel to sms; needs the SMS/RCS add-on.
RCS	Supportedservice: RCS on send	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	Not supported	Not listed
Email	Not supported	Not listed
Phone calls	Not supportedFAQ: voice calls are not supported	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 call routes across iMessage, RCS and SMS	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.
Developer tools
REST API	SupportedREST for sends and number routes; WebSocket is the main event channel	Supported
TypeScript SDK	PartialOnly framework packages on npm (OpenClaw plugin, n8n node, MCP); no general SDK	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.
Python SDK	PartialOnly LangChain and CrewAI tool packages on PyPI; no general SDK	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.
Other SDKs	Not supportedProvider lists its SDK story as REST and WebSocket from any language	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.
CLI	Not listed	Not listed
Webhooks	PartialDocs: self-serve inbound is WebSocket only; webhooks are for approved managed setups	SupportedRetried up to 30 times over several hours.
Signed webhooks	SupportedHMAC-signed	PartialYou set an authorization header and verify it; no HMAC signature.
MCP server	Supported@emotion-machine/claw-messenger-mcp, five tools	PartialDocumentation-only MCP server; no access to your account or messages.
Open source	Not supportedCore service is not published; only MIT starter repos and plugins	PartialOnly the n8n node is MIT on GitHub; the platform is closed.
Self-hosting	Not supportedProvider lists itself as hosted	Not listed
Local testing	Not listedSetup test sends a real message to a phone you control	Not listedThe sandbox needs a real iPhone or Mac to message it.
Custom channel providers	Not listed	Not listed
Event replay	SupportedInbound messages are stored and redelivered on reconnect; sync replays since a time	PartialWebhook history API to fetch past events; no replay call.
OpenTelemetry	Not listed	Not listed
No-code integrations	Partialn8n node for self-hosted n8n, send only; no Zapier or Make	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.
CRM integrations	Not supportedProvider: no native HubSpot, Salesforce or GoHighLevel connector	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.
Built for AI agents
Agent framework	PartialPlugins for OpenClaw, Hermes, LangChain and CrewAI; no framework of its own	Not listed
Agent framework integrations	SupportedOwn packages for LangChain, CrewAI, OpenClaw, Hermes and n8n	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listed	Not listed
Human handoff	Not listed	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	Partialsync replays saved inbound messages since a timestamp; no history API	SupportedPaginated history per contact, filterable by date, direction and type.
Plans and compliance
Free plan	Not supportedNo free tier; 7-day trial with a card	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.
Public pricing	Supported	Supported
No per-message fees	PartialFlat plans with hard monthly message caps; Agency charges $0.005 per extra message	SupportedUnlimited messages; plans cap unique active contacts per day.
Uptime SLA	Not supportedTerms: high availability is a goal, uptime is not guaranteed	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.
Isolated infrastructure	SupportedAgency subtenants get their own line, key and routing	SupportedA dedicated sender's number and server are allocated to you alone.
SOC 2 Type II	Not supportedProvider: no public certifications yet	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.
GDPR	Not listed	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 Claw Messenger if you need agent framework and agent framework integrations.

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

Frequently asked questions

• Photon vs Claw Messenger
• Claw Messenger vs Linq
• Blooio vs Claw Messenger
• Claw Messenger vs Sendblue
• Chert vs Claw Messenger
• BlueBubbles vs Claw Messenger
• Claw Messenger vs MessageBlue
• Claw Messenger vs Twilio
• Bird vs Claw Messenger

• Photon vs LoopMessage
• LoopMessage vs Linq
• Blooio vs LoopMessage
• LoopMessage vs Sendblue
• Chert vs LoopMessage
• BlueBubbles vs LoopMessage
• LoopMessage vs MessageBlue
• LoopMessage vs Twilio
• Bird vs LoopMessage
• LoopMessage vs Telnyx