Blue Reacher vs Zernio

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

Blue Reacher

Managed iMessage lines for B2B sales, with API and MCP
Starting price
$199/month per line at 4+ lines; $249/month for 1 to 3 lines
Free plan
Free public sandbox key; simulator only, no real sends

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

Blue Reacher supports 50 of the 77 features compared here, and Zernio supports 57.

Feature comparison

FeatureBlue ReacherZernio
iMessage messaging
iMessage
SupportedOne-to-one iMessage sends and replies over REST and webhooks.
Supported
Group chats
PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedRename a group or change its photo, one change per call.
Mentions
Not listed
Not listed
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
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
Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.
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 supportedDocs say there is no Markdown rendering on any channel.
SupportedInline *bold*, _italic_, __underline__ and ~strikethrough~ markup renders as rich text.
Attachments
SupportedOne file per message for now. Images and video up to 100 MB, audio and PDF up to 25 MB.
SupportedUp to 10 per message, each a public https URL of at most 256 characters.
Live Photos
Not listed
Not listed
Rich link previews
SupportedA bare URL renders as a preview card on iMessage, built on the recipient's device.
SupportedOn by default; linkPreview: false sends links as plain text.
Voice messages
PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
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
Not listedDocs say recipients see only the number until they save your contact card.
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.
Not listed
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedEach line is an Apple ID on Apple hardware run by Blue Reacher.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number
SupportedPricing lists port-in support for an existing number.
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
SupportedOmit the line on a send and load balancing picks one; the site calls it smart routing.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
Supported
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
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
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
Supported
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
Supported
WhatsApp
Not supportedNot offered
Supported
Telegram
Not supported
Supported
Slack
Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.
Supported
Email
Not supportedNot offered. Docs say there is no email-address sender option.
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.
SupportedInbound and outbound PSTN calls, SIP trunks, browser softphone, recording and transcription.
Apple Messages for Business
Not supportedNot offered; the site describes it as a separate Apple product.
Not supportedNot offered
Unified channel API
SupportediMessage and SMS fallback share one send endpoint and message model.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Supported@zernio/node
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
Supportedzernio-sdk
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
Supported
Supported
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. 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 listed
Not supportedHosted cloud service only
Local testing
SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
Not listed
Not listed
Event replay
PartialRetries for about a day; undelivered events are kept and support replays them on request.
Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
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 listed
Not listed
Human handoff
SupportedPause or snooze the AI assistant per contact while a person replies.
PartialDashboard inbox and workflow handoff nodes; no iMessage-specific handoff documented.
Audit logs
PartialDocs mention an exportable opt-out audit trail; no general activity log is documented.
SupportedAppend-only log of team-management actions; Enterprise adds broader audit logs.
Message history API
SupportedConversation history per contact, cursor-paginated.
Supported
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
SupportedFirst 2 connected accounts free; free iMessage sandbox (5 contacts, 50 messages a day).
Public pricing
Supported
Supported$200 per iMessage sender per month, plus the connected-account fee.
No per-message fees
Supported
PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA
Not listed
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
SupportedDedicated lines per customer, never shared; workspaces logically isolated.
Not listed
SOC 2 Type II
Not supportedTrust page says controls map to SOC 2 but the independent attestation is not complete.
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
SupportedGDPR page and a published DPA with Standard Contractual Clauses.
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

Blue Reacher

Lines are $249 a month each plus a $449 activation fee, $199 a month each at 4 or more lines, or $1,949 per line per year with activation waived.

Pricing model: flat per line, no per-message fees

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 Blue Reacher if you need FaceTime calls, iMessage availability check, line pooling and local testing.

Choose Zernio if you need edit and unsend, stickers, formatted text and location sharing.

Frequently asked questions