Dial vs iBlueText

Compare Dial and iBlueText 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

iBlueText

Hosted or self-hosted iMessage lines with iPhone lookup
Starting price
$29/month (self-hosted, 1 line); $99/month per hosted line
Free plan
No-card trial: 100 lookups, 10 verifications and 10 iMessages; self-hosted 3-day trial

Dial supports 44 of the 77 features compared here, and iBlueText supports 43.

Feature comparison

FeatureDialiBlueText
iMessage messaging
iMessage
SupportedNeeds an iMessage number, provisioned through the API. Pay-as-you-go accounts only.
SupportedHosted lines on iBlueText's Macs and iPhones, or self-hosted on your own Macs
Group chats
SupportedSend to and read iMessage groups the number was added to. Polls work in groups; replies and reactions do not.
Not listedNot mentioned in the API docs
Group management
Not supportedDocs say Dial cannot create a group, join one or accept an invite link.
Not listed
Group name and photo
Not listedGroup names are read live from the line; no way to set a name or photo is documented.
Not listed
Mentions
Not listed
Not listed
Tapbacks
SupportedSix tapback names or any single emoji. Sent only on inbound messages; received on message.received.
SupportedSend six tapbacks to inbound messages and receive reaction.received. Not on SIP-on rented Macs.
Threaded replies
SupportedNative threaded replies to inbound iMessage or RCS messages, one-to-one only.
Supportedreply_to quotes an inbound message; falls back to a normal message if Apple refuses
Typing indicators
PartialSend only, one-to-one and in groups. No inbound typing events are documented.
PartialSend only, in existing iMessage threads; no inbound typing events documented
Read receipts
PartialReports when recipients read your iMessages. No way to mark inbound messages read.
PartialReceive only: message.read and read_at when the recipient has read receipts on
Edit and unsend
Not listed
Not listed
Message effects
Not listed
Supported8 screen and 4 bubble effects on /send
Animated text effects
Not listed
Not listed
Stickers
Not listed
Not listed
Formatted text
Not listed
Not listed
Attachments
SupportedOne attachment per iMessage, 5 MB. Images, audio, video, PDF, vCard and iCalendar. No HEIC.
SupportedPhotos, video, voice memos, vCards and PDFs, up to 5 files of 5 MB each
Live Photos
Not listed
Not listed
Rich link previews
Not listed
SupportedGoHighLevel page cites real link previews; no API option documented
Voice messages
SupportedA single audio file on an iMessage number is sent as a native voice message.
SupportedVoice memos sent and received as attachments
Contact cards
SupportedSend .vcf files as media. Inbound cards arrive as text/vcard media (since October 2026).
Supported.vcf files sent as attachments
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
Not listed
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.
PartialHosted lines can get a business sender name at setup; no API or photo option documented
FaceTime calls
Not listed
PartialFaceTime audio placed from the self-hosted Bridge app, with call webhooks; no call API
Delivery status
PartialiMessage sends report no delivery receipts; delivery is inferred once a read arrives.
Supportedqueued, sent, delivered, read and failed; plain SMS has no delivery receipt
iMessage availability check
SupportedLookup endpoint checks whether any number can receive iMessage or WhatsApp.
SupportedLookup API at $0.005 a number, 400 free per line a day; also detects FaceTime
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.
SupportedHosted plan: iBlueText runs the Mac, iPhone, Apple Account and US number
Dedicated numbers
SupportedEach number belongs to your account. Docs say only US numbers can be provisioned now.
SupportedEach hosted line is its own US number on a dedicated, warmed Apple ID
Shared numbers
Not listed
PartialOnly the 10 free trial messages, which are sent from iBlueText's fleet
Bring your own number
Not listed
SupportedSelf-hosted uses your own iPhones and numbers; hosted lines can use your own Apple Account
Line pooling
Not listedDocs suggest splitting recipients across several iMessage numbers by hand; no automatic pooling found.
SupportedCampaigns spread new contacts across your lines and keep existing contacts on their line
SMS fallback
SupportediMessage numbers fall back to RCS or SMS automatically, at no message charge.
Supported
RCS fallback
Supported
PartialFalls back to green; the carrier decides RCS or SMS and iBlueText reports which
Outbound-first messaging
SupportedCold outbound allowed. Each iMessage number can start up to 50 new conversations a day.
SupportedCapped at 50 new iMessage and 50 new SMS contacts a day per line, 15 in the first 5 days
Calls on the iMessage number
SupportediMessage numbers also place and receive AI voice calls, or forward inbound calls.
PartialFaceTime audio from the line's Apple ID via the self-hosted Bridge app; no phone calls
Other channels
SMS
SupportedTwo-way SMS; MMS to US and Canada. Subscription accounts can text US numbers only.
SupportedSMS and MMS from the line's number; self-hosted can add Android phones or your own Twilio
RCS
PartialOnly as automatic fallback from iMessage numbers; not a channel you can pick.
PartialGreen messages go as RCS or SMS as the carrier decides; RCS cannot be selected
WhatsApp
BetaBeta, enabled per account. Runs on an iMessage number, one attachment per message.
SupportedYour own number paired by QR code ($19/mo add-on) or a hosted number from $49/mo
Telegram
Not supportedNot offered
Not supportedNot offered
Slack
Not supportedNot offered as a channel. A Zapier app can forward messages to Slack.
Not supported
Email
Not supportedNot offered
Not supported
Phone calls
SupportedInbound and outbound AI voice calls with transcripts.
Not supportedNot offered; calls are FaceTime audio only
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.
PartialiMessage and SMS share /send; WhatsApp has its own endpoint; inbound shares one webhook
Developer tools
REST API
Supported
SupportedOpenAPI 3.1 spec published
TypeScript SDK
Supported@getdial/sdk
Not listedNone found; docs say no SDK is needed
Python SDK
Supporteddial-sdk
Not listed
Other SDKs
Not supportedSDK overview lists only Node and Python clients, plus agent framework packages.
Not listed
CLI
Supporteddial CLI, installed with a shell script or npx. Needs Node 22 or later.
Not listed
Webhooks
Supported
SupportedReplies, opt-outs and opt-in status events, per account or per line
Signed webhooks
SupportedHMAC-SHA256 over timestamp and body, X-Dial-Signature header.
SupportedX-IBT-Signature: HMAC-SHA256 of the raw body
MCP server
SupportedRemote server with OAuth at getdial.ai/mcp, or local stdio through the CLI.
Supportedibluetext-mcp on npm, 30 tools
Open source
PartialThe Chat SDK adapter is MIT on GitHub. The platform is closed.
Not supportedBridge is licensed per line and cannot be resold; only the npm MCP package is MIT
Self-hosting
Not listedSelf-Hosted mode only means calls are driven by your own agent server; the platform itself is hosted.
SupportediBlueText Bridge runs on your own Macs from $29/mo; messages stay on your hardware
Local testing
Not listed
Not listed
Custom channel providers
Not listed
PartialSelf-hosted Bridge can route SMS through your own Twilio account
Event replay
PartialWebhooks retry up to 6 attempts. The live stream replays only about 2 minutes of missed events.
PartialWebhooks retried 3 times over about 12 minutes; conversations API has a since filter
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedZapier app with message and call triggers, and send, call and provision actions.
SupportedNative GoHighLevel and Wix apps; Zapier, Make and n8n through webhooks
CRM integrations
Not listed
SupportedNative GoHighLevel only; HubSpot and Salesforce through the API and webhooks
Built for AI agents
Agent framework
PartialHosted AI voice agent runs calls from a prompt. Messaging is send and receive only.
Not listed
Agent framework integrations
SupportedLangChain, Vercel AI SDK, CrewAI, AutoGen, Microsoft Agent Framework and a Vercel Chat SDK adapter.
Not listed
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listed
Human handoff
PartialThe voice agent can transfer a call to a person. No handoff for messaging.
SupportedPause or resume the built-in AI per conversation; it steps back 24 hours after a manual reply
Audit logs
Not listed
PartialPortal API log lists every API call for 30 days
Message history API
SupportedList and search messages, up to the 100 most recent per request.
SupportedConversations API returns two-way transcripts
Plans and compliance
Free plan
Supported$5 of free credit, no card. Free accounts are capped at 5-minute calls and 2 concurrent calls.
PartialOne-time allowance: 100 lookups, 10 verifications and 10 iMessages, no card
Public pricing
Supported
Supported
No per-message fees
PartialMessages from a $250/month iMessage number are free. SMS on standard numbers is billed per message.
SupportedFlat per line; lookups and verifications cost $0.005 each
Uptime SLA
PartialUptime SLA listed for Enterprise only.
Not supportedTerms provide the service as is, with no guarantee of availability
Isolated infrastructure
Not listed
PartialSelf-hosted runs on your own Macs; hosted runs many lines per Mac
SOC 2 Type II
PartialSite says SOC 2 certified. Report type and a report are not published.
Not listed
GDPR
SupportedDPA covers GDPR and UK GDPR, with Standard Contractual Clauses.
Not listedPrivacy policy mentions GDPR rights where applicable; no DPA found

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

iBlueText

Hosted lines cost $99 a month each plus a one-time setup fee from $249, self-hosted Bridge plans run from $29 a month for 1 line to $999 for 100 lines, and lookups cost $0.005 each.

Pricing model: flat per line, plus prepaid credits for lookups and verifications

Source

Which should you choose?

Choose Dial if you need group chats, polls, phone calls and TypeScript SDK.

Choose iBlueText if you need message effects, rich link previews, FaceTime calls and shared numbers.

Frequently asked questions