Blue Reacher vs Dial

Compare Blue Reacher and Dial 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

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

Blue Reacher supports 50 of the 77 features compared here, and Dial supports 44.

Feature comparison

FeatureBlue ReacherDial
iMessage messaging
iMessage
SupportedOne-to-one iMessage sends and replies over REST and webhooks.
SupportedNeeds an iMessage number, provisioned through the API. Pay-as-you-go accounts only.
Group chats
PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.
SupportedSend to and read iMessage groups the number was added to. Polls work in groups; replies and reactions do not.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
Not supportedDocs say Dial cannot create a group, join one or accept an invite link.
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
Not listedGroup names are read live from the line; no way to set a name or photo is documented.
Mentions
Not listed
Not listed
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
SupportedSix tapback names or any single emoji. Sent only on inbound messages; received on message.received.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
SupportedNative threaded replies to inbound iMessage or RCS messages, one-to-one only.
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
PartialSend only, one-to-one and in groups. No inbound typing events are documented.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
PartialReports when recipients read your iMessages. No way to mark inbound messages read.
Edit and unsend
Not listed
Not listed
Message effects
Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.
Not listed
Animated text effects
Not listed
Not listed
Stickers
Not listed
Not listed
Formatted text
Not supportedDocs say there is no Markdown rendering on any channel.
Not listed
Attachments
SupportedOne file per message for now. Images and video up to 100 MB, audio and PDF up to 25 MB.
SupportedOne attachment per iMessage, 5 MB. Images, audio, video, PDF, vCard and iCalendar. No HEIC.
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.
Not listed
Voice messages
PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedA single audio file on an iMessage number is sent as a native voice message.
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
SupportedSend .vcf files as media. Inbound cards arrive as text/vcard media (since October 2026).
Polls
Not listed
Supported2 to 10 options, one-to-one or in iMessage groups. Votes arrive as events with a live tally.
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
Not listedDocs say recipients see only the number until they save your contact card.
SupportedSet the first name, last name and photo shown beside the number's iMessages.
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
Not listed
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
PartialiMessage sends report no delivery receipts; delivery is inferred once a read arrives.
iMessage availability check
PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedLookup endpoint checks whether any number can receive iMessage or WhatsApp.
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.
SupportediMessage numbers are provisioned through the API, with asynchronous setup. No Mac or device needed.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
SupportedEach number belongs to your account. Docs say only US numbers can be provisioned now.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
Not listed
Bring your own number
SupportedPricing lists port-in support for an existing number.
Not listed
Line pooling
SupportedOmit the line on a send and load balancing picks one; the site calls it smart routing.
Not listedDocs suggest splitting recipients across several iMessage numbers by hand; no automatic pooling found.
SMS fallback
Supported
SupportediMessage numbers fall back to RCS or SMS automatically, at no message charge.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
Supported
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
SupportedCold outbound allowed. Each iMessage number can start up to 50 new conversations a day.
Calls on the iMessage number
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
SupportediMessage numbers also place and receive AI voice calls, or forward inbound calls.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
SupportedTwo-way SMS; MMS to US and Canada. Subscription accounts can text US numbers only.
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
PartialOnly as automatic fallback from iMessage numbers; not a channel you can pick.
WhatsApp
Not supportedNot offered
BetaBeta, enabled per account. Runs on an iMessage number, one attachment per message.
Telegram
Not supported
Not supportedNot offered
Slack
Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.
Not supportedNot offered as a channel. A Zapier app can forward messages to Slack.
Email
Not supportedNot offered. Docs say there is no email-address sender option.
Not supportedNot offered
Phone calls
PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.
SupportedInbound and outbound AI voice calls with transcripts.
Apple Messages for Business
Not supportedNot offered; the site describes it as a separate Apple product.
Not listedDocs say iMessage numbers send over Apple Messages for Business, but no business chat product is documented.
Unified channel API
SupportediMessage and SMS fallback share one send endpoint and message model.
SupportedOne messages endpoint and event format for SMS, iMessage and WhatsApp, plus calls.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Supported@getdial/sdk
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
Supporteddial-sdk
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
Not supportedSDK overview lists only Node and Python clients, plus agent framework packages.
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
Supporteddial CLI, installed with a shell script or npx. Needs Node 22 or later.
Webhooks
Supported
Supported
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
SupportedHMAC-SHA256 over timestamp and body, X-Dial-Signature header.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
SupportedRemote server with OAuth at getdial.ai/mcp, or local stdio through the CLI.
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.
PartialThe Chat SDK adapter is MIT on GitHub. The platform is closed.
Self-hosting
Not listed
Not listedSelf-Hosted mode only means calls are driven by your own agent server; the platform itself is hosted.
Local testing
SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.
Not listed
Custom channel providers
Not listed
Not listed
Event replay
PartialRetries for about a day; undelivered events are kept and support replays them on request.
PartialWebhooks retry up to 6 attempts. The live stream replays only about 2 minutes of missed events.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.
SupportedZapier app with message and call triggers, and send, call and provision actions.
CRM integrations
SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).
Not listed
Built for AI agents
Agent framework
PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.
PartialHosted AI voice agent runs calls from a prompt. Messaging is send and receive only.
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
SupportedLangChain, Vercel AI SDK, CrewAI, AutoGen, Microsoft Agent Framework and a Vercel Chat SDK adapter.
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listed
Human handoff
SupportedPause or snooze the AI assistant per contact while a person replies.
PartialThe voice agent can transfer a call to a person. No handoff for messaging.
Audit logs
PartialDocs mention an exportable opt-out audit trail; no general activity log is documented.
Not listed
Message history API
SupportedConversation history per contact, cursor-paginated.
SupportedList and search messages, up to the 100 most recent per request.
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
Supported$5 of free credit, no card. Free accounts are capped at 5-minute calls and 2 concurrent calls.
Public pricing
Supported
Supported
No per-message fees
Supported
PartialMessages from a $250/month iMessage number are free. SMS on standard numbers is billed per message.
Uptime SLA
Not listed
PartialUptime SLA listed for Enterprise only.
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.
PartialSite says SOC 2 certified. Report type and a report are not published.
GDPR
SupportedGDPR page and a published DPA with Standard Contractual Clauses.
SupportedDPA covers GDPR and UK GDPR, with Standard Contractual Clauses.

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

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

Which should you choose?

Choose Blue Reacher if you need group management, group name and photo, message effects and rich link previews.

Choose Dial if you need polls, sender name and photo, WhatsApp and uptime SLA.

Frequently asked questions