Know what landed, was read and got a reply
Every message reports six states with a timestamp and the channel it traveled on. Your CRM acts on them the moment they change.
Included on every line. No A2P registration required.
Tom Becker
iMessage
iMessage · Today
Proposal's over to you. Happy to walk it through.
Reading it now.
Take your time. I'm free after 3 if questions come up.
Read 2:14 PM
Delivered, read and replied, each reported back to the record.
The numbers that predict revenue
Delivered tells you the list was clean. Replies and conversions tell you the offer worked. Every state is recorded, so you see both.
Six states, in order
Queued, sent, delivered, read, replied or undelivered, each with a timestamp, so you see how fast people answered as well as whether they did.
Read is a signal, not a denominator
Many people keep read receipts off, so visible reads sit below real readership. Use read to prioritize contacts and delivered as the base for every rate.
Split by channel
Every message carries the channel it used, so reports show what iMessage produced on its own and what RCS and SMS added.
Reporting by step
Most sequences have one step carrying the replies and two carrying nothing. Step-level reporting shows which is which.
Automations fire on the event
Delivered with no reply after ten minutes can create a call task, read with no reply can raise its priority, and undelivered can route to email and phone. States arrive by webhook, so nothing has to poll.
Trigger
New lead in CRM
Under 9 seconds
Send iMessage
Your data, where you want it
Webhooks post each state as it happens and the REST API returns the same data on demand. Most teams write states to the CRM and mirror raw events into a warehouse.
POST /v1/messages
{ "to": "+15125550142", "content": "..." }
webhook message.received
{ "service_type": "iMessage", "content": "Yes, Thursday" }
What are delivery states?
Delivery states are per-message labels that follow a text from send to reply. Blue Reacher reports six: queued, waiting for its send slot; sent, left your line; delivered, on the device; read, the thread was opened; replied, the conversation is live; and undelivered, rejected. Each carries a timestamp and the channel it used, which is enough to drive automation.
Questions about read receipts and delivery
The questions buyers ask before they start. Anything not here is answered in the answers library.
Can I see whether someone read my message?+
Yes, when the recipient has read receipts turned on. Many people keep them off, so your visible read count sits below real readership. Use read to prioritize, and delivered as the base for campaign rates.
How is reply rate calculated?+
Unique contacts who replied, divided by unique contacts delivered, across the campaign's window. Counting contacts rather than replies stops one chatty lead from inflating the number.
What does undelivered mean?+
The message was rejected, usually because the number isn't a live mobile line. Fallback tries RCS, then SMS, so a reachable contact still gets it.
How fast do states update?+
In real time. Each change posts to your webhook endpoint as it happens, so automations fire without polling or anyone watching a dashboard.
Which metric predicts revenue?+
Reply rate and conversion rate. Delivered and read barely move between a great campaign and a poor one; replies tell you whether the offer landed, and conversions decide where the budget goes.
See these numbers on your own list
Book your Blue Funnel Map and ask us to open it by text. You watch your own message go from sent to delivered to read while we talk.
Most teams are live within a week.