State of iMessage Automation 2026

Table of contents

1. Why we published this
2. Headline benchmarks at a glance
3. Reply rate: 2.7% unique-lead on cold outreach
4. Delivery: 93% of messages reach the recipient
5. iMessage native vs SMS fallback split
6. Opt-out rate: 4% of inbound replies
7. Comparison to industry baselines
8. What the data does not tell us
9. Methodology
10. Use this data

---

Editor's note: Bharadwaj founded Tuco AI, the platform whose aggregate data backs this report. We've kept the underlying numbers honest: ratios where the absolute volume could mislead, explicit sample-size disclosure, no cherry-picking of top performers. Source aggregations are reproducible from the methodology section.

Last updated: May 19, 2026

Why we published this

Most iMessage automation pricing pages cite "98% open rates" and "30%+ reply rates" without citation. Those numbers are usually from Apple Business Chat marketing decks for enterprise rich-card flows — not what an actual sales team running cold outbound through a third-party iMessage platform sees in production.

We pulled the aggregate from Tuco AI's production database for the five-month window ending May 19, 2026, and published the ratios as-observed. Where the data is too thin to draw conclusions, we say so. Where it's skewed by a small number of high-volume customers, we say so. The intent is to give operators a baseline they can actually plan against.

Headline benchmarks at a glance

Across 13 active customer accounts, December 16, 2025 → May 19, 2026:

Caveat: absolute volume is dominated by a handful of high-volume customers. Ratios are more meaningful than raw counts in this dataset; we report ratios throughout.

Reply rate: 2.7% unique-lead on cold outreach

We measure reply rate two ways:

• Unique-lead reply rate: of the 8,403 unique recipients contacted at least once, 230 replied at least once. 2.7%. This is the cold-outreach industry-standard measurement.
• Message-level reply rate: 1,423 inbound replies against 16,141 outbound messages. 8.8%. Higher because warm threads generate multiple inbound messages per lead.

The cold email industry sits at roughly 1% reply rate for purchased-list outbound per Mailchimp's 2024 SMB email benchmarks. Cold SMS sits at 1-2% per Twilio's published messaging engagement reports. LinkedIn InMail reportedly clears 3-5% per LinkedIn's own marketing solutions data.

iMessage cold outreach landed at 2.7% unique-lead reply rate in our dataset — meaningfully ahead of cold email and cold SMS, broadly in line with InMail, without LinkedIn's daily send caps or visibility to recipients that the message is "an automated platform message."

What we can't claim from this dataset:

• We can't compare against high-end "warm" benchmarks (5-15%) because our outbound mix is a heavy weight toward cold sequences. Warm-thread reply rates within our 8.8% message-level number suggest warm replies are materially higher, but the sample is too thin to publish a separate warm number with confidence.
• We can't break the reply rate down by industry. Our customer mix spans home services, SaaS sales, youth sports recruiting, van conversions, and e-commerce — too few accounts per vertical to publish industry-specific reply benchmarks without misleading readers. We'll publish per-industry breakdowns once we have 30+ accounts per vertical.

For more on what drives reply rate on iMessage specifically, see our complete guide to iMessage brand marketing and the vertical-specific use case pages.

Delivery: 93% of messages reach the recipient

We classify every message into one of seven status codes at terminal state. Across all final-state messages (excluding queued and scheduled — that's in-flight inventory, not outcomes):

Effective successful delivery: 93%.

For comparison, SMS through US carriers under A2P 10DLC sees delivery rates around 85% post-carrier-filter per published industry benchmarks, with the spam-filter tail being the dominant failure mode for promotional content. iMessage routes through Apple's network rather than US carriers, which is why the iMessage native delivery rate is higher than carrier SMS even when both reach iPhones.

The full data on why this matters compared to A2P 10DLC carrier filtering is in our A2P 10DLC alternative deep-dive.

iMessage native vs SMS fallback split

The 57/23 split (native iMessage vs SMS fallback) is one of the most operationally useful numbers in this report.

In aggregate:

• 57% of messages arrived as native iMessage with blue-bubble formatting.
• 23% fell back to SMS because the recipient endpoint didn't accept iMessage (Android, iPhone with iMessage disabled, throttled endpoint, etc.).
• 13% were submitted as iMessage with sent confirmation but no delivery receipt (recipient offline).
• 7% failed outright.

The 23% fallback rate roughly tracks the US mobile market composition: roughly 55% iPhone share, 45% Android per Statista's 2026 US mobile OS market share data. For a US-focused B2B audience with iPhone-skewing demographics (founders, sales leaders), expected native iMessage share is higher; for B2C with broad demographic spread, fallback rate moves toward the 40-50% range.

Operational implication: if your messaging vendor doesn't handle SMS fallback transparently, 23% of your messages disappear for the Android-recipient half of your audience. Tuco AI's fallback is automatic — see the pricing matrix for which competitors offer it natively vs as an add-on.

Opt-out rate: 4% of inbound replies

Of 727 unique inbound reply threads, 31 (4%) contained an opt-out keyword (STOP, UNSUBSCRIBE, REMOVE, CANCEL, QUIT, END, OPT-OUT, and informal variants like "stop please," "don't text me").

For comparison, CTIA Best Practices guidance places industry SMS opt-out rates at 3-7% on opt-in lists, climbing meaningfully on cold or purchased lists. Our 4% figure sits at the favorable end of that range — likely because iMessage's higher trust signal (blue bubble, real sender name) suppresses the "who is this and why are they texting me" reaction that drives a chunk of cold-SMS opt-outs.

What this means operationally: every 25 replies your team handles, expect one opt-out. Build the workflow with that in mind — opt-out parsing should be automatic and CRM write-back should be near-real-time so the next campaign doesn't re-send to an opted-out lead. Both are default behavior on Tuco AI; see the HubSpot integration and Salesforce integration pages for how opt-out propagation works in production.

The TCPA-side rule on opt-out handling is also worth knowing: businesses must honor opt-outs through any reasonable method within 10 business days. Most teams aim for near-real-time. We cover the full TCPA framework in the iMessage for life insurance agents post — the framework applies to every B2C-adjacent vertical, not just insurance.

Comparison to industry baselines

Putting the numbers together with public benchmarks:

The win for iMessage isn't a single dominant metric. It's the combination: higher reply rate than email + SMS, higher delivery rate than SMS post-filter, and the ability to operate inside the same speed-to-lead window that drives the MIT lead-response study's 21x qualification improvement when contact happens within 5 minutes.

What the data does not tell us

Being honest about the limits:

1. We don't have enough per-vertical volume to publish industry-specific reply rates. Home services, SaaS, youth sports recruiting, and high-ticket coaching are all represented in the dataset, but with too few accounts per vertical to support published benchmarks. We'll revisit this once we have 30+ accounts per vertical.
2. We don't have causal data on what drives reply rate. Lead source, sequence design, sender personalization, and offer all matter and we can't isolate which moved the needle in any specific account.
3. Time-to-first-reply distributions require joining inbound messages to their initiating outbound message, which our schema makes brittle — the unmatched count was high enough that we don't publish that distribution here. Future schema work will fix this.
4. Day-of-week and hour-of-day patterns are dominated by a small number of bulk-send events. We won't publish a "best time to send" table from this dataset because it would be misleading. If we publish one in the future it'll be after explicit normalization across accounts.
5. Five months is a short window. Seasonal patterns (Q4 retail surge, summer slowdown for B2B) are not fully visible. The 2027 update will have a 12-month window for comparison.

Methodology

Data source: Tuco AI production MongoDB cluster, tuco-ai database, messages collection. Time window: First message at 2025-12-16T00:33:38Z, last message at 2026-05-19T01:54:05Z. Five months and three days. Account count: 13 customer organizations with active subscription status. Aggregation: every message in the time window, with no top-performer filtering and no exclusions for low-volume accounts. We chose ratio-based reporting over absolute volume reporting because volume is heavily skewed toward a small number of bulk-send customers.

Reply rate calculation:

• Unique-lead: count distinct leadId values in messages where direction='received', divide by count distinct leadId values where direction='sent'.
• Message-level: count messages where direction='received', divide by count messages where direction='sent'.

Delivery rate calculation:

• Final-state denominator: count messages where status ∈ — explicitly excludes queued and scheduled (in-flight inventory, not outcomes).
• Successful numerator: count messages where status ∈ .

Opt-out rate calculation:

• Numerator: count messages where direction='received' and message body matches regex /^(stop|unsubscribe|remove|cancel|quit|end|opt.?out)/i.
• Denominator: count distinct conversation threads with at least one inbound message.

Where this report differs from vendor marketing-page benchmarks:

• We measure aggregate, not best-case. Vendor pages typically cite top-decile performers.
• We exclude in-flight messages from delivery denominators. Some vendor reports include them, which inflates apparent delivery rates by ~30% during high-volume periods.
• We measure opt-outs against reply count, not against total sends — operationally more useful but produces a higher headline number than total-send-based reporting.

Use this data

If you're a B2B operator planning iMessage outreach for the first time, this gives you a real production baseline to plan against:

• Reply rate: assume 2-3% on cold lists, 8-10% on warm follow-up cadences.
• Delivery: assume ~93% successful delivery if your vendor handles SMS fallback; ~70% if they're iMessage-only.
• Opt-outs: budget for 3-5% of inbound replies being opt-out requests. Build automated CRM write-back.

For platform comparison and pricing methodology, see the Sendblue / Blooio / Linq Blue pricing transparency post. For the regulatory side (TCPA + A2P 10DLC), the A2P 10DLC alternative reference is the most-cited page on our site.

If you want to discuss running benchmarks against your own outbound, book a 15-minute call. We share more detailed per-vertical aggregates with prospects who can reciprocate with anonymized data on their own outreach.