16 capabilities, one page each
Features
One page per capability: what it does, how teams use it, how to set it up. This is the complete list.
What can Blue Reacher actually do?
Send blue-bubble iMessages from your CRM at campaign scale with media, voice, group threads, typing indicators, read receipts, reactions. Five jobs organize the capabilities: Send (campaigns, sequences, group threads, media); Convert (speed to lead, reminders, reactivation); Deliver (fallback, availability, opt-outs, states); Channels (where iMessage, RCS, SMS fit); Build (API and webhooks).
Two design choices run through every capability: automation pauses when a human replies, and everything reports honestly per message with the channel it actually used. Sequences pause, campaigns skip suppressed contacts, manual sends block opted-out recipients.
No add-on tier. Every line carries the full feature set at the flat per-line price with unlimited iMessages, and white-glove setup configures it, so the distance between reading a feature page and running it is one call. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.
Each page covers one capability: what it does, funnel moments it serves, how to set up, honest limits.
Features by industry
Same three capabilities, per vertical: trigger events, existing systems, industry funnel math.
Frequently asked questions
What features come with every Blue Reacher line?
All of them: campaigns, sequences, group messaging, media, availability checking, RCS then SMS fallback, opt-outs, delivery states, API, webhooks. No feature tier; flat rate with unlimited iMessages is the whole price. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.
Can I automate sequences and campaigns over iMessage?
Yes. Sequences run with message steps, waits, and stop-on-reply, so follow-ups never talk over replied contacts. Campaigns pace themselves, skip suppressed contacts, and report sent/delivered/read/replied/opted out per step.
How does Blue Reacher handle opt-outs?
Automatically and account-wide. STOP keywords and "take me off this list" are caught on every reply, queued sends canceled, and the contact suppressed across all lines, campaigns, and manual sends. Each event logs in an exportable audit trail.
What happens when a contact can't receive iMessage?
Message steps down to RCS, then SMS if needed, in the same thread and campaign. You can check availability before sending to know what share lands as blue bubbles.
Do delivery states really report per message?
Yes: queued, sending, sent, delivered, read, failed, per message, plus the channel that carried it. States stream to your CRM via webhooks, so operators gate steps on delivery and trigger nudges on read-with-no-reply.
Is there an API behind these features?
Every feature reaches the REST API with bearer-token auth, documented at docs.bluereacher.com and openapi.json. AI agents use the same surface through the MCP server.