Blue Reacher vs Chert

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

Chert

iMessage and FaceTime numbers for AI agents
Starting price
$25/month (Shared)
Free plan
24-hour trial: 10 messages and 10 FaceTime minutes on a shared line

Blue Reacher supports 50 of the 77 features compared here, and Chert supports 47.

Feature comparison

FeatureBlue ReacherChert
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.
Supported2 to 31 recipients; first group message must be text only.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedCreate, add or remove participants, and leave a group.
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedSet a group's display name and icon.
Mentions
Not listed
Not listed
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
SupportedSix standard tapbacks; inbound tapbacks show in message history.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
Not listedHomepage mentions reply context; no reply-to field in the API docs.
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedBest effort; group typing is not supported on every line.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
SupportedMark chats read; messages carry read_at when known.
Edit and unsend
Not listed
PartialEdit within 15 minutes; no unsend endpoint documented.
Message effects
Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedApple send effects, validated against an allowed list.
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.
SupportedUpload then send; several images can go out as one grouped message.
Live Photos
Not listed
Supportedlive_photo pairs an uploaded HEIC with its MOV.
Rich link previews
SupportedA bare URL renders as a preview card on iMessage, built on the recipient's device.
Supportedrich_link parts render as preview bubbles; falls back to a plain URL.
Voice messages
PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedNative voice notes on enabled lines; inbound memos arrive as attachments, no transcript.
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
SupportedBuilds a vCard bubble in DMs and groups.
Polls
Not listed
SupportedEnabled lines only; read votes by polling, no vote webhooks yet.
Chat backgrounds
Not listed
Not listed
Location sharing
Not listed
PartialOne-time location pin on enabled lines; not Live Location or Find My.
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.
SupportedNative name-and-photo sharing on enabled lines (share_native).
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
SupportedInbound audio and video, outbound audio only, bridged to your LiveKit agent.
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
SupportedPer-message status with delivered_at, and the channel used (iMessage or SMS).
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.
SupportedChert-managed sender lines assigned to your tenant.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
Supported$250/mo per line, arranged on a call; no self-serve checkout yet.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
SupportedFree 24-hour trial and $25/mo Shared plan on a shared line.
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.
SupportedPicks and pins a sender line per recipient from your assigned lines.
SMS fallback
Supported
PartialLines enabled for SMS retry only; plain-text 1:1 messages, not groups or media.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
Not listedHomepage says SMS or RCS fallback; API docs only describe SMS retry.
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
SupportedFirst send to a new recipient creates a lead and pins a line.
Calls on the iMessage number
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
PartialHomepage offers one number for iMessage and FaceTime; docs say identities are not unified yet.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
PartialOnly as an automatic retry after a failed iMessage, on enabled lines.
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
Not listedMentioned only as a fallback on the homepage.
WhatsApp
Not supportedNot offered
Not supportedNot offered
Telegram
Not supported
Not supported
Slack
Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.
Not listed
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.
Not supportedNot offered; calls are FaceTime only.
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.
PartialiMessage and SMS retry share one API; FaceTime uses a separate API.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Beta@trychert/sdk 0.2.0 on npm (MIT); the homepage still says SDK packages are not published.
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
BetaSource preview on GitHub; not released on PyPI.
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
BetaRust, C#/.NET, C++ and Go clients are source previews on GitHub.
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
BetaFaceTime CLI on npm's beta tag; the SDK adds a chert-sdk CLI for sends.
Webhooks
Supported
SupportedMultiple subscriptions with event filters; message.received for inbound.
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
SupportedHMAC-SHA256 per-subscription secret over timestamp and raw body.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
Not listed
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.
PartialSDKs are MIT and a FaceTime link connector is Apache-2.0; the service is closed.
Self-hosting
Not listed
Not listedOnly the open-source FaceTime link connector runs on your own machine.
Local testing
SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.
Not listedSSE stream and dev inbox avoid a public webhook, but a real phone is still needed.
Custom channel providers
Not listed
Not listed
Event replay
PartialRetries for about a day; undelivered events are kept and support replays them on request.
SupportedDurable event log with replay by event ID, polling and SSE.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.
Not listed
CRM integrations
SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).
SupportedSalesforce managed package and HubSpot app.
Built for AI agents
Agent framework
PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.
PartialChert-managed FaceTime assistants and a LiveKit voice-agent starter; messaging is send and receive.
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
PartialFaceTime calls connect to LiveKit agents; no messaging framework integrations.
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.
SupportedSlack reply triage with approve-to-send drafts, plus a console reply pane.
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.
PartialLast 200 messages per chat; no pagination yet.
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
Partial24-hour trial with 10 messages and 10 FaceTime minutes on a shared line.
Public pricing
Supported
Supported
No per-message fees
Supported
SupportedFlat monthly prices; paid plans have usage limits that are not spelled out.
Uptime SLA
Not listed
Not listed
Isolated infrastructure
SupportedDedicated lines per customer, never shared; workspaces logically isolated.
SupportedDedicated $250/mo line for your project; lower plans use shared lines
SOC 2 Type II
Not supportedTrust page says controls map to SOC 2 but the independent attestation is not complete.
Not listed
GDPR
SupportedGDPR page and a published DPA with Standard Contractual Clauses.
SupportedPrivacy policy sets out GDPR legal bases and rights.

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

Chert

A free 24-hour trial includes 10 messages and 10 FaceTime minutes on a shared line; Shared is $25 a month and a dedicated line is $250 a month, but paid checkout is paused.

Pricing model: flat monthly per line, with usage limits

Source

Which should you choose?

Choose Blue Reacher if you need threaded replies, iMessage availability check, bring your own number and RCS fallback.

Choose Chert if you need edit and unsend, Live Photos, polls and location sharing.

Frequently asked questions