iMessage Deliverability: How to Keep Your Lines Healthy
TL;DR
iMessage deliverability is three things stacked: delivered, visible, answered. Delivery receipts only prove the first, which is how a line pays the unknown-sender tax: every message lands, iOS 26 files it where the recipient has notifications switched off, and the dashboard reports a healthy campaign nobody has read. Lines stay healthy when your sending pattern looks like a person working a list, your list is clean, and enough recipients reply to pull you into their main inbox. Reply rate is the health signal to watch, because a reply is what buys known-sender status back.
On this page
- 01What does iMessage deliverability actually mean?
- 02Why sending patterns matter more than what you write
- 03Who decides how much a line sends in a day?
- 04Why reply rate is a health metric, not just a performance metric
- 05List hygiene: what to strip before the first send
- 06What actually damages sender reputation
- 07How do you catch a line degrading before it costs you meetings?
- 08The recovery playbook for an underperforming campaign
- 09What your team controls, what a managed platform handles
- 10Where Blue Reacher fits
- 11Frequently asked questions
What does iMessage deliverability actually mean?
Deliverability is whether your message reaches someone who can act on it. iOS 16's Screen Unknown Senders routes unread-from numbers to a separate list with notifications off.
Measure three layers: Delivered (reached the device), Visible (landed where recipient sees it), Answered (a human replied, the only layer that drives revenue).
- Delivered: the message reached the device. Your delivery states confirm this. It's table stakes and says nothing about outcomes.
- Visible: the message landed somewhere the recipient will actually look, with a notification attached. Known-sender status decides this one.
- Answered: a human replied. This is the only layer that produces booked appointments, and it feeds back into the other two.
Why sending patterns matter more than what you write
Pattern is judged at scale; copy is judged by one person. Filters key off sending shape: how many new threads at once, similarity, speed, reply rate. A great opener in a bad pattern still gets buried.
Copy controls whether you get a reply once you're seen. But don't rewrite openers to fix a volume problem; fix the list. Two separate failure modes; teams burn weeks on copy when the real issue was the list.
Who decides how much a line sends in a day?
On a managed platform, the platform handles pacing. Blue Reacher paces every line like a person working a list, respects local business hours, and adjusts when numbers say to.
What you control is list order. Open with segments most likely to answer. Replies early compound; every replied conversation the recipient cannot flag.
Lines pace at 50 opted-in / 30 cold new contacts/day to stay deliverable; replies are never metered.
Why reply rate is a health metric, not just a performance metric
A reply changes what the recipient's carrier and handset can do to your line. Apple's Report Junk doesn't appear on a thread you've already replied to.
Reply rate is the share of daily sending immune to negative signal and counted toward known-sender status. Below 3:1 reply-to-flag ratio, treat the line as degraded.
- Above 10:1: healthy, nothing to change
- 5:1 to 10:1: hold volume flat and fix your weakest segment
- 3:1 to 5:1: cut volume in half and pause cold sends entirely
- Below 3:1: treat the line as degraded and run the recovery playbook
What a reply actually buys you
12 of 100
Threads protected at a 12% reply rate
One reply closes the complaint window on that thread permanently.
97 of 100
Threads still exposed at a 3% reply rate
And they stay exposed for as long as the thread exists.
10:1
The reply-to-flag ratio worth defending
Replies divided by Report Junk, STOP and hard blocks over the same window. Below 3:1, treat the line as degraded.
List hygiene: what to strip before the first send
Strip anything that can't reply, then send in order of warmth. Those two moves do more for line health than every other hygiene step combined.
Then order the send. Warmest segment first on a new line and after every recovery.
Warm contacts reply, replies buy known-sender status, which is what your cold segment will need three weeks later.
- Non-mobile numbers. Landlines, switchboards, and main office VoIP lines are dead weight that drags every ratio you track.
- Numbers with no blue-bubble availability. Check before you send, not after. A pre-send availability check turns a guess into a routing decision.
- Data older than roughly 18 months with no refresh. B2B mobile numbers churn with job changes faster than most teams assume.
- Duplicates across lines and across reps. Nobody should get the same opener from two of your numbers in the same month.
- Anyone who opted out anywhere in your organization. Suppression is org-wide and permanent, not per campaign.
- Role numbers and generic contacts scraped off websites. They inflate list size and answer nothing.
What actually damages sender reputation
Reputation damage is almost always a pattern the recipient can feel. Ranked by how often I see each one cause real trouble:
- The same text in hundreds of threads. Vary sentence structure, not just merge fields.
- A link in the first message. It's the strongest single tell of automation and hands a hesitant recipient a reason to flag instead of read.
- Sending to a list that was never going to answer. A bad list kills a line faster than bad copy ever will.
- Slow or partial opt-out handling. Every missed STOP is a complaint sitting in a queue.
- Volume jumps after a pause. Coming back from a holiday week at full speed reads as a fresh burst, not a resumed relationship, which is why pacing after a pause is handled for you.
- Unstaffed replies. A prospect who answers in 30 seconds and hears nothing for two days is worse for you than a prospect you never messaged.
- Sending at 6:40am in the recipient's timezone. Scheduled sends against local business hours fix this at zero cost.
- Moving a list that already failed onto a different line. The list is the problem, and it produces the same result wherever it goes. If a list killed the numbers once, retire the list.
How do you catch a line degrading before it costs you meetings?
Watch the leading indicators, because meetings move last. Things break in order: reply time stretches, then reply rate drops, then conversations route to green-bubble, then opt-outs climb, then meetings fall.
The trick is a control segment. Every week, send the same opener to a fixed 50-contact slice from the same source with the same criteria.
When headline reply rate moves, the control tells you whether the line changed or your list changed.
- Control-segment reply rate down 25% week over week: investigate the list and the copy today
- Down 40%: pause the campaign and talk to us before the next send
- Median time to first reply doubles with no seasonal explanation: investigate before the next send
- Opt-outs clustering in one segment: retire that segment, not the opener
The order things break in
- 1Median time to first reply stretchesFirst signal
Investigate before the next send if it doubles with no seasonal explanation.
- 2Reply rate on a stable segment dropsSecond
Down 25% week over week on the control segment: investigate the list and the copy today. Down 40%: pause the campaign.
- 3More conversations route to green-bubble fallbackThird
The list is aging, or it was never checked for availability.
- 4Opt-outs and total silence climb togetherFourth
Opt-outs clustering in one segment means retire that segment, not the opener.
- 5Meeting count fallsTwo to three weeks late
The only signal most teams watch, and the last one to arrive.
The recovery playbook for an underperforming campaign
Recovery splits the same way: the sending side is handled for you, and the list side is yours. What only you can do is find which segment or opener is carrying the damage.
Pull your last 500 conversations and break reply rate out by segment and opener. In most cases one segment is responsible for nearly all of it.
Restart on your warmest segment with the opener you have the most history on, no links. If two full attempts fail on the same list, retire the list and rebuild. A new line does not clean a list.
What your team controls, what a managed platform handles
Split the work by where the knowledge lives. Your team owns judgment about people: who to message, what to say, how fast to answer. A managed platform owns the mechanics and the monitoring.
Teams that try to hand-manage pacing end up doing all of it at 70%. List quality and reply speed go unwatched. Blue Reacher customers send texts from their CRM and see 2-3x more appointments.
| Your team owns | A managed platform handles |
|---|---|
| Segment quality, source, and send order | Pacing, scheduling, and sends against local business hours |
| Opener copy and variants | Delivery states, webhooks, and reporting you can read |
| Reply staffing and response speed | STOP auto-detection and opt-out enforcement |
| Which segments a campaign works, and in what order | Availability checking before a send goes out |
| The control segment and the weekly read | RCS then SMS fallback when a recipient isn't on iMessage |
| Consent records and honoring opt-outs in your CRM | Setup with no A2P registration required and nothing for you to install |
| Which lists to retire | Implementation consultation, message intent configuration, and optimization check-ins |
Where Blue Reacher fits
Blue Reacher is the right half of that table. Every line is paced against the recipient's local business hours, availability is checked before sends go out, and STOP is auto-detected and suppressed.
iMessage falls back to RCS then SMS. Pricing is $249 per line per month or $1,949 per year at about $162 a month on the pricing page.
Unlimited iMessages (50 opted-in / 30 cold new contacts a day) makes advice affordable. Follow-ups inside a live thread are cheapest replies you earn. Book your Blue Funnel Map, a 15-minute call, and we'll text you a demo.
Frequently asked questions
Does a delivery receipt mean my message was seen?
No. Delivery confirms the message reached the device and nothing more. Under iOS 26, a delivered message can sit in the Unknown Senders list with notifications off unless it's flagged time-sensitive (Apple Support, 2025). Treat delivery as the floor and reply rate as the real read on whether people are seeing you.
How many new conversations a day is safe on a fresh line?
On Blue Reacher that is not a number you set: pacing is managed per line so sending reads like a person working a list. What you control is the order segments get worked in. Open with people most likely to answer. Lines pace at 50 opted-in / 30 cold new contacts a day; replies are never metered.
Does getting a reply really stop someone from reporting me as spam?
On that thread, yes. Apple's Report Junk option doesn't appear on a conversation you've already replied to, and it doesn't appear for a sender saved in the recipient's contacts (Apple Support). That's why reply rate belongs on your health dashboard, not only your performance dashboard.
Do I need A2P 10DLC registration for iMessage outreach?
A2P 10DLC is the US carrier framework for application-to-person SMS and MMS sent from 10-digit numbers (Twilio compliance documentation). Blue Reacher runs with no A2P registration required. Consent law is a separate matter: TCPA, state statutes, and your own opt-out records still apply to every message you send.
What's the fastest way to tell whether the line or the list is the problem?
Run a control segment. Send the same opener each week to a fixed 50-contact slice drawn the same way from the same source. If the control holds steady while your headline reply rate falls, the new list or new copy caused it. If the control falls too, the line is degrading and it's time to cut volume.
Should I move to a new number when a line goes bad?
Only after you've fixed the cause. A list that failed on one line produces the same result wherever it goes, because the list is what recipients are reacting to. Retire the list, let the existing campaign recover on segments that answer, and save the new line for genuine capacity growth.
Keep reading
More on deliverability
Why Your Business Texts Aren't Delivering (and What Actually Fixes It)
The dashboard says sent, replies stopped, and nobody told you why. A field guide to silent SMS failure: how to tell unregistered blocking from content filtering from velocity flags, the fixes in order of effort, and when the honest answer is that the rails are the problem.
Why Leads Ghost Your Emails but Answer Texts
The lead who ignored four emails is not gone, they are triaging. A look at what inbox saturation actually does to reply behavior, why the same buyer answers a text in minutes, and the polite mechanics of moving a conversation from email to iMessage.
Put this on your pipeline
Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.
Book a demo