Blue Reacher vs Inkbox

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

Inkbox

Email, phone, iMessage and A2A identity for AI agents
Starting price
$25/month (Developer); $167/month for a dedicated iMessage number (Startup)
Free plan
Free: 3 identities, shared iMessage up to 2,000 messages a month and 3 recipients at a time

Blue Reacher supports 50 of the 77 features compared here, and Inkbox supports 45.

Feature comparison

FeatureBlue ReacherInkbox
iMessage messaging
iMessage
SupportedOne-to-one iMessage sends and replies over REST and webhooks.
SupportedShared router service on every plan, or a dedicated line from the Startup plan.
Group chats
PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.
SupportedDedicated lines only, 2 to 8 remote participants. Shared service is 1:1.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
PartialCreate a group by sending to 2 to 8 numbers. No add or remove member API in V1.
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
Not listed
Mentions
Not listed
Not listed
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
SupportedSend, replace and remove 7 tapbacks including eyes; inbound tapbacks arrive by webhook.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
Supportedreply_to_message_id in 1:1 and group chats, with thread reads. Falls back to a plain reply.
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
PartialSend only, in 1:1 chats. Groups and inbound typing events are not supported.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
PartialSend read receipts in 1:1 chats. No read status for your own sent messages is documented.
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.
Supported4 bubble and 9 full-screen send styles, in 1:1 and dedicated-line groups.
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 media item per message, uploads up to 10 MiB. No media before the recipient's first reply.
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.
Not listed
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
PartialThe router sends the agent's contact card on connect. Sending other vCards is not documented.
Polls
Not listed
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
Not listedDocs say recipients see only the number until they save your contact card.
SupportedDedicated lines share the identity's display name and avatar automatically.
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
Not listedCalls run over iMessage lines, but the docs do not say whether they are FaceTime.
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
Supportedimessage.sent, imessage.delivered and imessage.delivery_failed webhooks, per recipient in groups.
iMessage availability check
PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedReturns iMessage, SMS or RCS for any E.164 number.
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.
SupportedShared router lines and dedicated lines run by Inkbox. No Mac needed.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
SupportedStartup plan includes one dedicated iMessage number. VoIP numbers for calls and SMS from Developer.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
SupportedFree and paid plans include shared iMessage. The human must text the router first.
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.
BetaOrganization-owned shared iMessage pools, beta and by request only.
SMS fallback
Supported
SupportedInkbox tries iMessage first and can fall back to SMS; was_downgraded marks it.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
PartialDocs describe SMS fallback, and the service field can report rcs. The transport cannot be chosen.
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
PartialDedicated lines can start chats, up to 40 new recipients a day. Shared service needs the human to text first.
Calls on the iMessage number
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
SupportedAgents place and receive voice calls over shared and dedicated iMessage lines.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
SupportedSMS and MMS on dedicated VoIP numbers, US and Canada included. Group MMS is beta.
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
PartialOnly as a transport reported on iMessage lines; not a channel you can pick.
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.
BetaSlack is in beta: read, reply, files and retained history search.
Email
Not supportedNot offered. Docs say there is no email-address sender option.
SupportedEach identity gets a mailbox, with custom domains and IMAP/SMTP access.
Phone calls
PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.
SupportedInbound and outbound calls with your own WebSocket agent or Inkbox Voice AI (beta).
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.
PartialOne identity and one webhook subscription across channels, but separate APIs per channel.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Supported@inkbox/sdk
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
Supportedinkbox on PyPI
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
SupportedRust SDK (inkbox crate).
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
Supported@inkbox/cli
Webhooks
Supported
Supported
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
SupportedHMAC-SHA256 with a per-identity signing key.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
SupportedRemote Streamable HTTP endpoint at inkbox.ai/mcp, with a separate ChatGPT endpoint.
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.
PartialSDK, CLI, skills and examples are MIT on GitHub. The service is closed.
Self-hosting
Not listed
Not listed
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.
SupportedDelivery log with replay. Incoming-call and Slack deliveries cannot be replayed.
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).
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.
PartialIdentity layer with contact memories across email, texts and calls. No conversation framework.
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
SupportedPlugins for Hermes Agent, OpenClaw, OpenCode, Codex, Claude Code and DeepSeek Harness.
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listedAgents can reach each other over A2A tasks, but not in group chats.
Human handoff
SupportedPause or snooze the AI assistant per contact while a person replies.
PartialPeople can reply from the Console, and Voice AI can transfer a call. No handoff controls for agents.
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 read conversations and threads, with search on texts and email.
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
SupportedFree: 3 identities, shared iMessage up to 2,000 messages a month and 3 recipients at a time.
Public pricing
Supported
Supported
No per-message fees
Supported
PartialiMessage is capped per plan with no per-message fee. Extra SMS/MMS and call minutes cost $0.03 each.
Uptime SLA
Not listed
Not listed
Isolated infrastructure
SupportedDedicated lines per customer, never shared; workspaces logically isolated.
PartialDedicated iMessage infrastructure is listed for Enterprise only.
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.
Not listedThe DPA names the CCPA only; GDPR is not mentioned.

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

Inkbox

Free covers 3 identities with shared iMessage; Developer is $25 a month with a VoIP number; Startup is $167 a month with one dedicated iMessage number; Enterprise is custom. SMS/MMS and call minutes over allowance cost $0.03 each.

Pricing model: monthly plans with allowances, plus per-unit SMS/MMS and call-minute overage

Source

Which should you choose?

Choose Blue Reacher if you need group name and photo, rich link previews, voice messages and FaceTime calls.

Choose Inkbox if you need sender name and photo, shared numbers, Slack and email.

Frequently asked questions