Dial vs Zernio

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

Dial

Phone numbers with calls, SMS and iMessage for AI agents
Starting price
$3/month per standard number; $250/month per iMessage number
Free plan
$5 free credit, no credit card required

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

Dial supports 44 of the 77 features compared here, and Zernio supports 57.

Feature comparison

FeatureDialZernio
iMessage messaging
iMessage
SupportedNeeds an iMessage number, provisioned through the API. Pay-as-you-go accounts only.
Supported
Group chats
SupportedSend to and read iMessage groups the number was added to. Polls work in groups; replies and reactions do not.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
Not supportedDocs say Dial cannot create a group, join one or accept an invite link.
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
Not listedGroup names are read live from the line; no way to set a name or photo is documented.
SupportedRename a group or change its photo, one change per call.
Mentions
Not listed
Not listed
Tapbacks
SupportedSix tapback names or any single emoji. Sent only on inbound messages; received on message.received.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
SupportedNative threaded replies to inbound iMessage or RCS messages, one-to-one only.
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
PartialSend only, one-to-one and in groups. No inbound typing events are documented.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
PartialReports when recipients read your iMessages. No way to mark inbound messages read.
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
SupportedOne attachment per iMessage, 5 MB. Images, audio, video, PDF, vCard and iCalendar. No HEIC.
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
SupportedA single audio file on an iMessage number is sent as a native voice message.
SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards
SupportedSend .vcf files as media. Inbound cards arrive as text/vcard media (since October 2026).
PartialcontactCard shares the sender's own card only.
Polls
Supported2 to 10 options, one-to-one or in iMessage groups. Votes arrive as events with a live tally.
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
SupportedSet the first name, last name and photo shown beside the number's iMessages.
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
Not listed
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
PartialiMessage sends report no delivery receipts; delivery is inferred once a read arrives.
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
SupportedLookup endpoint checks whether any number can receive iMessage or WhatsApp.
Not listed
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportediMessage numbers are provisioned through the API, with asynchronous setup. No Mac or device needed.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
SupportedEach number belongs to your account. Docs say only US numbers can be provisioned now.
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
Not listed
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
Not listedDocs suggest splitting recipients across several iMessage numbers by hand; no automatic pooling found.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
SupportediMessage numbers fall back to RCS or SMS automatically, at no message charge.
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
Supported
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedCold outbound allowed. Each iMessage number can start up to 50 new conversations a day.
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
SupportediMessage numbers also place and receive AI voice calls, or forward inbound calls.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
Other channels
SMS
SupportedTwo-way SMS; MMS to US and Canada. Subscription accounts can text US numbers only.
Supported
RCS
PartialOnly as automatic fallback from iMessage numbers; not a channel you can pick.
Supported
WhatsApp
BetaBeta, enabled per account. Runs on an iMessage number, one attachment per message.
Supported
Telegram
Not supportedNot offered
Supported
Slack
Not supportedNot offered as a channel. A Zapier app can forward messages to Slack.
Supported
Email
Not supportedNot offered
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
SupportedInbound and outbound AI voice calls with transcripts.
SupportedInbound and outbound PSTN calls, SIP trunks, browser softphone, recording and transcription.
Apple Messages for Business
Not listedDocs say iMessage numbers send over Apple Messages for Business, but no business chat product is documented.
Not supportedNot offered
Unified channel API
SupportedOne messages endpoint and event format for SMS, iMessage and WhatsApp, plus calls.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supported@getdial/sdk
Supported@zernio/node
Python SDK
Supporteddial-sdk
Supportedzernio-sdk
Other SDKs
Not supportedSDK overview lists only Node and Python clients, plus agent framework packages.
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
Supporteddial CLI, installed with a shell script or npx. Needs Node 22 or later.
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
Supported
Supported
Signed webhooks
SupportedHMAC-SHA256 over timestamp and body, X-Dial-Signature header.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
SupportedRemote server with OAuth at getdial.ai/mcp, or local stdio through the CLI.
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
PartialThe Chat SDK adapter is 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 listedSelf-Hosted mode only means calls are driven by your own agent server; the platform itself is hosted.
Not supportedHosted cloud service only
Local testing
Not listed
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
Not listed
Not listed
Event replay
PartialWebhooks retry up to 6 attempts. The live stream replays only about 2 minutes of 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
SupportedZapier app with message and call triggers, and send, call and provision actions.
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
Not listed
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
PartialHosted AI voice agent runs calls from a prompt. Messaging is send and receive only.
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
SupportedLangChain, Vercel AI SDK, CrewAI, AutoGen, Microsoft Agent Framework and a Vercel Chat SDK adapter.
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
PartialThe voice agent can transfer a call to a person. No handoff for messaging.
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
SupportedList and search messages, up to the 100 most recent per request.
Supported
Plans and compliance
Free plan
Supported$5 of free credit, no card. Free accounts are capped at 5-minute calls and 2 concurrent calls.
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
PartialMessages from a $250/month iMessage number are free. SMS on standard numbers is billed per message.
PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA
PartialUptime SLA listed for Enterprise only.
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
Not listed
Not listed
SOC 2 Type II
PartialSite says SOC 2 certified. Report type and a report are not published.
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
SupportedDPA covers GDPR and UK GDPR, 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

Dial

Pay-as-you-go starts with $5 of free credit. A standard number is $3 a month plus metered SMS and calls, an iMessage number is $250 a month with free messages, and Enterprise is custom.

Pricing model: per number plus metered usage; iMessage messages free on an iMessage number

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 Dial if you need polls, iMessage availability check and uptime SLA.

Choose Zernio if you need group management, group name and photo, edit and unsend and message effects.

Frequently asked questions