FAQ
Direct answers to the questions evaluators ask before building on Blue Reacher: devices, A2P, Android recipients, volume, compliance, and CRM fit.
Do I need my own phone?
No. Lines are dedicated iMessage lines that Blue Reacher provisions and manages. You send through the API, and nothing runs on your hardware.
Do I need A2P or 10DLC registration?
No. A2P registration is a carrier requirement for SMS traffic. iMessage traffic doesn't pass through carrier SMS filtering, so there's no registration process before you can start sending. Messages that fall back to SMS are still delivered through the platform without a registration step on your side.
What happens when a recipient can't receive iMessage?
The message falls back to SMS automatically when your workspace's message routing allows it, and every message record carries the channel that actually carried it. To check a number before you send, call POST /v1/contacts/check-imessage. It needs a line with Advanced Mode on.
How much can I send?
Sending capacity is set per line. Scaling volume means adding lines, not pushing one line harder. The deliverability page explains how to keep each line healthy as volume grows.
Is this TCPA compliant?
The platform can start an automation on a stop keyword and refuses sends to a contact with Do Not Disturb on. Keeping an opt-out list and consent for who you contact are yours, and the compliance guide covers what that requires, including the April 2025 FCC revocation rules, quiet hours, and record-keeping.
Which CRMs work?
Any CRM that can call an HTTP API and receive a webhook can connect. Register it as a custom integration, create and update contacts through the contacts endpoints, store your CRM record id in custom_fields, and receive replies on the workspace's inbound webhook.
Can I send media, voice notes, and group messages?
Yes to all three. Attach one file per message by passing a public https:// URL in attachments. An audio file in attachments is sent as a voice note on iMessage. Send a tapback with POST /v1/messages/{id}/reactions, and send to a group chat with POST /v1/groups/{channel}/{id}/messages. Format details are in message formatting.
How do opt-outs work?
Automations can start on a stop keyword, and you add the step that turns on Do Not Disturb. You can also set it from your own system with PATCH /v1/contacts/{id}/dnd. Keep your own opt-out list as well. Details in opt-out handling.
What does "delivered" actually mean?
That the message reached the recipient's thread. It doesn't mean read, and it doesn't mean the line is healthy. The metric that reports both is reply rate, and deliverability explains how to read it.
Where do I start?
The quickstart: install your app with OAuth, probe the token, send one message, check its status.