9 features, one page each
Features
Messaging and the FaceTime dialer are the product. These are the features that ride on every line, one page each.
What can Blue Reacher actually do?
Blue Reacher sends blue-bubble iMessages from your CRM on a dedicated line, with a FaceTime dialer on the same number. Every line carries the same nine features: RCS and SMS fallback, group messaging, rich messaging, sequences, scheduled messages, availability checking, read receipts, opt-out handling, and the webhooks and API that wire it all into your stack.
Two design choices run through all of them: automation stops the moment a human replies, and every message reports the channel it actually used and where it is in its lifecycle.
There is no feature tier. Every line carries the full set at the flat per-line price, with unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day, and white-glove setup configures it for you.
Frequently asked questions
What features come with every Blue Reacher line?
All of them: RCS and SMS fallback, group messaging, rich messaging, sequences, scheduled messages, availability checking, read receipts, opt-out handling, webhooks and API. There is no feature tier; the flat per-line price is the whole price, with unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day.
Can I automate follow-up over iMessage?
Yes. Sequences run message steps with waits and stop on reply, so a follow-up never talks over a contact who answered. Scheduled messages land each send at the contact's local morning, and every step reports sent, delivered, read and replied.
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, sequences, 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.
Ready to see your funnel on blue bubbles?
15 minutes on your funnel. We mark every stage a green bubble is costing you a reply, and you keep the map either way.