Tuco AI vs Zernio

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

Tuco AI

iMessage follow-up for opted-in leads from your CRM
Starting price
$149/month (Starter, 1 line) plus $335 setup
Free plan
None; docs say no free trials or refunds

Zernio

One API for iMessage, SMS, WhatsApp, social DMs and calls
Starting price
$200/month per iMessage sender
Free plan
First 2 connected accounts free; free iMessage sandbox on a shared line

Feature comparison

FeatureTuco AIZernio
iMessage messaging
iMessage
Supported
Supported
Group chats
Not supportedTuco's llms.txt says it has no group chats.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
Not supportedNo group chat support
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
Not supported
SupportedRename a group or change its photo, one change per call.
Mentions
Not supported
Not listed
Tapbacks
SupportedSend six classic tapbacks by API; inbound reactions, including custom emoji, arrive as message.reaction.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
Not listed
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
PartialStart and stop typing by API, best effort. Inbound typing events not documented.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
Supportedmessage.opened webhook with readAt when the recipient has read receipts on.
PartialMark a chat read inside an active two-way chat. Webhook docs list message.read for other platforms only.
Edit and unsend
Not listed
SupportedEdit text within 15 minutes; unsend within 2 minutes removes the bubble for the recipient.
Message effects
Not listed
Supported13 screen and bubble effects, such as slam, invisibleInk, confetti and fireworks.
Animated text effects
Not listed
Not listed
Stickers
Not listed
PartialInbound stickers are typed as sticker. Sending stickers is not documented.
Formatted text
Not listed
SupportedInline *bold*, _italic_, __underline__ and ~strikethrough~ markup renders as rich text.
Attachments
SupportedUp to 2 files per message, 25 MB each. Not allowed on the first message to a contact.
SupportedUp to 10 per message, each a public https URL of at most 256 characters.
Live Photos
Not listed
Not listed
Rich link previews
Not listed
SupportedOn by default; linkPreview: false sends links as plain text.
Voice messages
SupportedvoiceNote sends one audio file as a native voice note bubble.
SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards
Not listed
PartialcontactCard shares the sender's own card only.
Polls
Not listed
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
Not listed
PartialStatic location pins only. Inbound shared locations arrive without coordinates.
iMessage apps
Not listed
Not listed
Live app cards
Not listed
Not listed
Sender name and photo
PartialLine name and photo are set by Tuco staff, at most 3 changes per line per month.
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
PartialFaceTime Audio calls as a $100/month per-line add-on. Tuco's llms.txt says it has no FaceTime.
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
Supportedqueued, sent, delivered, failed and fallback statuses, with sent, failed and fallback webhooks.
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
SupportedSingle, round-robin and bulk checks, about 70 per line per day.
Not listed
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedEach line is a real iPhone with an eSIM that Tuco hosts. About 48 hours to activate.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
SupportedOne Apple identity per line. Lines can be ordered by API.
SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers
Not listed
SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number
PartialDocs say existing numbers cannot be ported in, but a Linq migration page offers to port Linq numbers.
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
SupportedSends without fromLineId round-robin across active lines.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
PartialThrough your Twilio, GoHighLevel or webhook provider, or P2P SMS from the line once support enables it.
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
Not supportedRCS not offered
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedOutbound to opted-in contacts. Cold lists are refused, and first messages cannot carry links or files.
SupportedOne new chat per 15 minutes per sender, warm-up from 2 to 50 a day, no links in openers.
Calls on the iMessage number
SupportedCalls go out from the same number the line texts from. 500 minutes per line per month included.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
Other channels
SMS
PartialSMS through your own Twilio, GHL or webhook provider, or P2P SMS from the line in its eSIM country.
Supported
RCS
Not supportedNot offered
Supported
WhatsApp
Not supported
Supported
Telegram
PartialTelegram bot for team notifications and replies. Leads are not messaged on Telegram.
Supported
Slack
PartialLead conversations appear as Slack threads the team can reply from. Not a channel to contacts.
Supported
Email
SupportedmessageType email sends email, and an email bridge sends iMessages from your inbox.
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
SupportedOutbound calls with recording, inbound forwarding and a click-to-call API (beta, +1 numbers only).
SupportedInbound and outbound PSTN calls, SIP trunks, browser softphone, recording and transcription.
Apple Messages for Business
Not supportedNot offered
Not supportedNot offered
Unified channel API
SupportedOne send endpoint with messageType imessage, sms or email.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Not listedThe iMessage API page shows npm install @tuco-ai/sdk, but no such package is on npm.
Supported@zernio/node
Python SDK
Not listed
Supportedzernio-sdk
Other SDKs
Not listed
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
Not listed
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
SupportedSent, failed, fallback, opened, reply, reaction, AI draft, handover, call recording and DNC events.
Supported
Signed webhooks
SupportedHMAC-SHA256 in the X-Tuco-Signature header.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
Supportedtuco-mcp on npm, run locally with an API key, with about 90 tools.
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
Partialtuco-mcp is MIT licensed on npm. The platform is closed.
PartialSDKs, CLI, n8n node and Chat SDK adapter are MIT or Apache-2.0. The platform is closed.
Self-hosting
Not listedHosted on Tuco hardware. Self-hosting is not mentioned.
Not supportedHosted cloud service only
Local testing
PartialSimulate runs a goal bot against a transcript without sending. Message sends have no sandbox.
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
PartialSMS fallback can route through your Twilio, GoHighLevel or a custom webhook.
Not listed
Event replay
Supported30-day webhook delivery log with replay from the dashboard or API, plus one automatic retry.
Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedGoHighLevel, n8n, Zapier and Make.com.
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
SupportedHubSpot, Salesforce, Close and Pipedrive. One CRM per workspace.
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
SupportedHosted goal bots and Knowledge Base replies with tools, in copilot or autopilot mode.
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
Not listed
PartialVercel Chat SDK adapter (iMessage not listed) and an OpenClaw skill.
Streaming replies
Not listed
PartialChat SDK adapter streams by editing on Telegram only.
Agent group chats
Not supportedNo group chat support
Not listed
Human handoff
SupportedCopilot drafts need approval, and conversation.handover fires when the AI stops for a person.
PartialDashboard inbox and workflow handoff nodes; no iMessage-specific handoff documented.
Audit logs
SupportedActivity log of workspace changes, including MCP tool calls.
SupportedAppend-only log of team-management actions; Enterprise adds broader audit logs.
Message history API
SupportedMessage history, conversations and replies endpoints.
Supported
Plans and compliance
Free plan
Not supportedDocs say there are no free trials, paid pilots or refunds.
SupportedFirst 2 connected accounts free; free iMessage sandbox (5 contacts, 50 messages a day).
Public pricing
SupportedStarter $149/month, Growth $299/month, plus $335 setup per line.
Supported$200 per iMessage sender per month, plus the connected-account fee.
No per-message fees
SupportedNo per-message fees. AI credits and extra call minutes are billed separately.
PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA
Not listedGrowth lists a 4-hour support SLA. No uptime SLA found.
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
SupportedEach line runs on its own iPhone and Apple ID on dedicated Mac hardware, with no VMs.
Not listed
SOC 2 Type II
Not supportedSecurity page says Tuco does not hold SOC 2.
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
SupportedGDPR page with data rights and Standard Contractual Clauses. DPA availability listed.
SupportedGDPR documentation in the trust portal; public DPA.

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

Pricing

Tuco AI

Starter is $149 a month for 1 line and Growth $299 a month for 2 lines, each with a one-time $335 setup fee per line and no per-message fees.

Pricing model: flat per line, plus AI credits and call minute packs

Source

Zernio

An iMessage sender costs $200 a month plus Zernio's per-account fee, with a free sandbox; SMS, calls and outbound messages past 10,000 a month are metered.

Pricing model: flat per sender, plus per connected account and usage meters

Source

Which should you choose?

Choose Tuco AI if you need FaceTime calls, iMessage availability check, line pooling and email.

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

Frequently asked questions