Miss Blue vs Zernio

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

Miss Blue

Dedicated iMessage line with API, team inbox and calling
Starting price
$99/month per number (launch price)
Free plan
Free sandbox; 30-minute live demo line

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

Miss Blue supports 47 of the 77 features compared here, and Zernio supports 57.

Feature comparison

FeatureMiss BlueZernio
iMessage messaging
iMessage
Supported
Supported
Group chats
SupportedSend into an existing group by its chat_id and read group threads.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
SupportedCreate groups of 2 to 32 and add or remove members; leaving a group is not supported yet.
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
SupportedRename a group and set or remove its photo.
SupportedRename a group or change its photo, one change per call.
Mentions
Not listed
Not listed
Tapbacks
SupportedAdd or remove the six tapbacks; tapbacks from customers appear on the message.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
SupportedQuoted replies with reply_to_message_id.
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
SupportedSend typing, optional auto-typing on inbound iMessage, and contact typing via webhook.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
SupportedExplicit read receipts by API; outbound messages report read.
PartialMark a chat read inside an active two-way chat. Webhook docs list message.read for other platforms only.
Edit and unsend
PartialUnsend within Apple's 2-minute window. An edit endpoint is documented, but the FAQ says editing is not supported yet.
SupportedEdit text within 15 minutes; unsend within 2 minutes removes the bubble for the recipient.
Message effects
Not supportedThe errors page says effects are not a supported API operation yet.
Supported13 screen and bubble effects, such as slam, invisibleInk, confetti and fireworks.
Animated text effects
Not supportedThe errors page says expressive text styles and effects are not supported yet.
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
SupportedImages, video, PDFs, Office files and more up to 100 MiB, one per send, or carousels of 2 to 20 images.
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
SupportedAudio-only sends use the native voice-note bubble by default.
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
SupportedSend Find My requests, read the sharing state and watch live fixes over Server-Sent Events.
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
SupportedSet and verify the number's Name and Photo Sharing profile by API.
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
PartialFaceTime Audio only, as a $250/month add-on per line.
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
Supportedpending, sent, delivered, read and failed with a reason, by webhook or per-message callback.
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
SupportedLive iMessage and FaceTime registration lookup; a separate lookup reads your own past traffic.
Not listed
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedEach number runs on a Mac that Miss Blue operates; staff provision numbers within about 48 to 72 hours.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
Supported$99/month per number at the launch price (normally $198).
SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers
SupportedShared-pool numbers are offered as a separate, labelled option.
SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number
SupportedTransfer an existing number in; staff complete it in about 1 to 2 weeks.
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
SupportedAuto round robin spreads new contacts across a project's dedicated numbers, then keeps each on one.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
SupportedFalls back to RCS, or to SMS where RCS is unavailable, from the same number.
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
SupportedFalls back to RCS where the carrier and recipient support it.
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedNew contacts are paced: 50 per number per day by default and 150 messages a day in total.
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
SupportedFaceTime Audio and phone calls from the number customers already message.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
Other channels
SMS
SupportedAs fallback from the iMessage number; the docs also describe Twilio SMS lines.
Supported
RCS
SupportedAs fallback when the carrier and recipient support it.
Supported
WhatsApp
Not supportedNot offered
Supported
Telegram
Not supported
Supported
Slack
Not supportedNot offered as a channel; the Slack page is an integration guide.
Supported
Email
Not supportedNot offered as a channel; iMessage can be sent to Apple ID email addresses.
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
PartialBrowser phone calls as a $75/month add-on; API keys cannot place regular phone calls.
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
SupportediMessage with RCS and SMS fallback, groups and calls share one API and webhook stream.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API
Supported113 endpoints across 13 resources, with an OpenAPI file.
Supported
TypeScript SDK
Not listedThe API is plain HTTP; no SDK package was found.
Supported@zernio/node
Python SDK
Not listed
Supportedzernio-sdk
Other SDKs
Not listed
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
Supportedmb, with installers for macOS, Linux and Windows.
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
Supported
Supported
Signed webhooks
SupportedHex HMAC-SHA256 over timestamp and raw body; per-message callbacks are unsigned.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
Supportedmb mcp serves the CLI commands as MCP tools for Claude Code, Codex, Cursor and others.
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
Not supportedThe CLI repo holds builds and installers without a license; the service 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
Supportedmb_sandbox_ keys simulate outcomes and signed webhooks on a virtual number, with no phone.
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
Not listed
Not listed
Event replay
PartialPer-endpoint delivery log and history sync; docs say to poll GET /v1/messages to repair missed events.
Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry
Not listed
Not listed
No-code integrations
BetaGoHighLevel connector is in beta; the Zapier, Make and n8n pages are setup guides.
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
BetaGoHighLevel connector in beta; HubSpot and Salesforce pages describe API builds set up in onboarding.
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
PartialNo agent SDK; offers a managed conversational AI add-on and multi-step automations.
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
PartialGuide pages for Vercel AI SDK, Chat SDK, LangChain and Claude Agent SDK; no adapter package found.
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
SupportedShared Message Center for human takeover, with internal notes and resolving.
PartialDashboard inbox and workflow handoff nodes; no iMessage-specific handoff documented.
Audit logs
Not listed
SupportedAppend-only log of team-management actions; Enterprise adds broader audit logs.
Message history API
SupportedThread history by API and a conversation sync from the line's Mac.
Supported
Plans and compliance
Free plan
SupportedFree sandbox with simulated sends, plus a 30-minute live demo line by texting DEMO.
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
PartialEnterprise only: contracted service terms; no uptime figure published.
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
SupportedDedicated numbers run on hardware assigned to you; Enterprise adds dedicated equipment.
Not listed
SOC 2 Type II
Not listed
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
Not 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

Miss Blue

A free sandbox for testing, then $99 per dedicated number per month at the launch price (normally $198), with the usual $479 setup fee waived until October 31; FaceTime Audio ($250), phone calls ($75) or both ($300) are optional add-ons per line, and Enterprise is custom.

Pricing model: flat per line

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

Choose Zernio if you need message effects, stickers, formatted text and rich link previews.

Frequently asked questions