LoopMessage vs Tuco AI

LoopMessage supports 53 of the 77 features compared here, and Tuco AI supports 41.

Feature comparison

Feature	LoopMessage	Tuco AI
iMessage messaging
iMessage	Supported	Supported
Group chats	SupportedSend and receive in iMessage groups; not available in the sandbox.	Not supportedTuco's llms.txt says it has no group chats.
Group management	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.	Not supportedNo group chat support
Group name and photo	SupportedSet group name (32 characters max) and photo with PATCH.	Not supported
Mentions	Not listed	Not supported
Tapbacks	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.	SupportedSend six classic tapbacks by API; inbound reactions, including custom emoji, arrive as message.reaction.
Threaded replies	Supportedreply_to_id on send; inbound webhooks carry a thread object.	Not listed
Typing indicators	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.	PartialStart and stop typing by API, best effort. Inbound typing events not documented.
Read receipts	PartialYou can mark chats read; no read event is documented for your outbound messages.	Supportedmessage.opened webhook with readAt when the recipient has read receipts on.
Edit and unsend	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.	Not listed
Message effects	Supported13 bubble and screen effects via the effect field.	Not listed
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 2 files per message, 25 MB each. Not allowed on the first message to a contact.
Live Photos	Not listed	Not listed
Rich link previews	SupportedLinks get rich previews by default; preview: false sends plain text.	Not listed
Voice messages	SupportedSend audio files as voice messages; inbound audio is transcribed.	SupportedvoiceNote sends one audio file as a native voice note bubble.
Contact cards	Supportedcontact_file adds a vCard to the message.	Not listed
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.	Not listed
iMessage apps	Not listed	Not listed
Live app cards	Not listed	Not listed
Sender name and photo	Not listedDocs suggest sending a vCard so recipients see your name and photo.	PartialLine name and photo are set by Tuco staff, at most 3 changes per line per month.
FaceTime calls	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.	PartialFaceTime Audio calls as a $100/month per-line add-on. Tuco's llms.txt says it has no FaceTime.
Delivery status	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.	Supportedqueued, sent, delivered, failed and fallback statuses, with sent, failed and fallback webhooks.
iMessage availability check	PartialThrough LoopLookup, a separate LoopMessage service.	SupportedSingle, round-robin and bulk checks, about 70 per line per day.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	SupportedDedicated senders run on hardware LoopMessage rents to you.	SupportedEach line is a real iPhone with an eSIM that Tuco hosts. About 48 hours to activate.
Dedicated numbers	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.	SupportedOne Apple identity per line. Lines can be ordered by API.
Shared numbers	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.	Not listed
Bring your own number	PartialYou can port a US number in; your own Apple IDs are not accepted.	PartialDocs say existing numbers cannot be ported in, but a Linq migration page offers to port Linq numbers.
Line pooling	SupportedSender pools balance new contacts across senders and match replies to the right one.	SupportedSends without fromLineId round-robin across active lines.
SMS fallback	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.	PartialThrough your Twilio, GoHighLevel or webhook provider, or P2P SMS from the line once support enables it.
RCS fallback	SupportedSame add-on uses RCS instead of SMS when the device supports it.	Not supportedRCS not offered
Outbound-first messaging	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.	SupportedOutbound to opted-in contacts. Cold lists are refused, and first messages cannot carry links or files.
Calls on the iMessage number	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.	SupportedCalls go out from the same number the line texts from. 500 minutes per line per month included.
Other channels
SMS	SupportedSet channel to sms; needs the SMS/RCS add-on.	PartialSMS through your own Twilio, GHL or webhook provider, or P2P SMS from the line in its eSIM country.
RCS	SupportedSet channel to rcs; needs the SMS/RCS add-on.	Not supportedNot offered
WhatsApp	SupportedAdd-on, +$10/mo, on the same phone number and API.	Not supported
Telegram	Not supportedPlanned on the roadmap, not available yet.	PartialTelegram bot for team notifications and replies. Leads are not messaged on Telegram.
Slack	Not listed	PartialLead conversations appear as Slack threads the team can reply from. Not a channel to contacts.
Email	Not listed	SupportedmessageType email sends email, and an email bridge sends iMessages from your inbox.
Phone calls	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.	SupportedOutbound calls with recording, inbound forwarding and a click-to-call API (beta, +1 numbers only).
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 send endpoint with messageType imessage, sms or email.
Developer tools
REST API	Supported	Supported
TypeScript SDK	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.	Not listedThe iMessage API page shows npm install @tuco-ai/sdk, but no such package is on npm.
Python SDK	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.	Not listed
Other SDKs	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.	Not listed
CLI	Not listed	Not listed
Webhooks	SupportedRetried up to 30 times over several hours.	SupportedSent, failed, fallback, opened, reply, reaction, AI draft, handover, call recording and DNC events.
Signed webhooks	PartialYou set an authorization header and verify it; no HMAC signature.	SupportedHMAC-SHA256 in the X-Tuco-Signature header.
MCP server	PartialDocumentation-only MCP server; no access to your account or messages.	Supportedtuco-mcp on npm, run locally with an API key, with about 90 tools.
Open source	PartialOnly the n8n node is MIT on GitHub; the platform is closed.	Partialtuco-mcp is MIT licensed on npm. The platform is closed.
Self-hosting	Not listed	Not listedHosted on Tuco hardware. Self-hosting is not mentioned.
Local testing	Not listedThe sandbox needs a real iPhone or Mac to message it.	PartialSimulate runs a goal bot against a transcript without sending. Message sends have no sandbox.
Custom channel providers	Not listed	PartialSMS fallback can route through your Twilio, GoHighLevel or a custom webhook.
Event replay	PartialWebhook history API to fetch past events; no replay call.	Supported30-day webhook delivery log with replay from the dashboard or API, plus one automatic retry.
OpenTelemetry	Not listed	Not listed
No-code integrations	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.	SupportedGoHighLevel, n8n, Zapier and Make.com.
CRM integrations	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.	SupportedHubSpot, Salesforce, Close and Pipedrive. One CRM per workspace.
Built for AI agents
Agent framework	Not listed	SupportedHosted goal bots and Knowledge Base replies with tools, in copilot or autopilot mode.
Agent framework integrations	Not listed	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listed	Not supportedNo group chat support
Human handoff	PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.	SupportedCopilot drafts need approval, and conversation.handover fires when the AI stops for a person.
Audit logs	PartialMessage, webhook and API request history kept; no account audit log found.	SupportedActivity log of workspace changes, including MCP tool calls.
Message history API	SupportedPaginated history per contact, filterable by date, direction and type.	SupportedMessage history, conversations and replies endpoints.
Plans and compliance
Free plan	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.	Not supportedDocs say there are no free trials, paid pilots or refunds.
Public pricing	Supported	SupportedStarter $149/month, Growth $299/month, plus $335 setup per line.
No per-message fees	SupportedUnlimited messages; plans cap unique active contacts per day.	SupportedNo per-message fees. AI credits and extra call minutes are billed separately.
Uptime SLA	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.	Not listedGrowth lists a 4-hour support SLA. No uptime SLA found.
Isolated infrastructure	SupportedA dedicated sender's number and server are allocated to you alone.	SupportedEach line runs on its own iPhone and Apple ID on dedicated Mac hardware, with no VMs.
SOC 2 Type II	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.	Not supportedSecurity page says Tuco does not hold SOC 2.
GDPR	SupportedHelpdesk says data is stored following GDPR.	SupportedGDPR page with data rights and Standard Contractual Clauses. DPA availability listed.

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 LoopMessage if you need group chats, group management, group name and photo and threaded replies.

Choose Tuco AI if you need sender name and photo, FaceTime calls, Telegram and Slack.

Frequently asked questions

• 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

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