How to Send a Mass iMessage to Customers (Without Group Threads)
TL;DR
A mass iMessage that works is thousands of individual one-to-one threads sent from a dedicated iMessage line, personalized per contact and paced by the platform, with availability checks before the send and STOP handling after it. The two DIY routes both fail: a group thread caps at 32 people and turns into reply-all chaos, and a bulk blast from a personal number gets deliveries quietly failing and the number reported as junk. The channel rewards looking like a person, so the setup has to send like one, at scale.
On this page
How do you send a mass iMessage?
Individual one-to-one messages from a dedicated iMessage line, through a platform built for it. Each contact gets their own thread with their own name in it, the platform paces sends, checks iMessage availability before sending, and routes replies back to your team.
Both obvious shortcuts fail: a group thread hard-caps at 32 people, and a blast from a personal number gets deliveries silently killed. Apple built iMessage for people texting people, so the DIY routes each collide with that design. Worth understanding before you burn a list on either.
Why a group thread is the wrong tool
Apple caps a group iMessage thread at 32 participants (Apple Support), so a 500-contact send would need 16 separate group threads before you even hit the real problems. And the real problems are worse than the cap.
Everyone in a group thread sees everyone else. That means you just disclosed your customer list to your customers, phone numbers included, which is a privacy failure your prospects will notice even if regulators never do. Then the replies start. One person answers "who is this?" and 31 people get the notification, then the next reply, then the mute-and-leave exodus. Your brand's first impression is a notification storm the recipient did not ask to join.
Group threads have a real job in business messaging: a deal thread with three stakeholders, an onboarding thread with a client's team. Deliberate, small, and personal. As a broadcast tool they are disqualified before you start.
What a group thread does to a 500-contact send
32
Participants in one group iMessage thread
Apple's published hard cap.
16
Separate threads a 500-contact send would need
Before you reach any of the real problems.
31
People notified by every single reply
One person answers "who is this?" and everyone else gets the notification, then the next reply, then the mute-and-leave exodus.
What happens when you blast from a personal number
Deliveries quietly stop. It is the same silent drop that kills filtered SMS, wearing a different uniform: Apple does not publish sending limits for ordinary numbers, but the pattern is documented across years of Apple community threads. Send enough near-identical messages in a short window and messages start showing Not Delivered, often with no obvious trigger and no way to appeal. The account keeps working for normal texting, so people rarely realize the bulk sends died until they notice nobody ever replies.
Recipients finish the job. Messages from unknown senders carry a Report Junk link on iPhone, and a blast that reads like a blast collects those reports fast. Enough of them and deliverability degrades for everything the number sends. You have one personal number, and this is how it stops being useful for outreach permanently.
There is also no opt-out machinery. A contact who replies STOP to your personal number is opting out to a human who has to remember it, forever, across every future campaign. Miss one and the TCPA's statutory damages run $500 to $1,500 per message, with your personal number on the complaint. The legality of the channel is covered in our iMessage marketing legality guide; the short version is that consent and opt-out obligations apply in full, and a personal phone has no tooling for either.
What a dedicated iMessage line does differently
A dedicated line is a separate business number for outbound volume. Every send is an individual thread, personalized from your contact fields, paced automatically with quiet hours and throttling. Availability checks before sending, automatic RCS then SMS fallback for non-iMessage contacts, STOP detection and suppression across every future send, and per-message delivery states so you know what landed.
The full flow from audience building through scheduling to reporting is on the iMessage campaigns page.
What the platform does around each send
- 1Availability checkBefore the send
Tells you which contacts can receive iMessage before anything goes out, so the list is a routing decision rather than a guess.
- 2Individual threads, personalizedThe send itself
Every message is its own thread with the contact's own name in it, so 2,000 messages read as 2,000 texts rather than one broadcast.
- 3Paced automaticallyThroughout
Quiet hours and throttling, which is what keeps deliveries landing at volume.
- 4RCS then SMS fallbackFor the rest of the list
Contacts outside iMessage still get covered in the same send.
- 5STOP detected and suppressedAfter a reply
Suppression applies across every future send rather than living in someone's memory.
- 6Delivery states returnedPer message
You know what landed instead of guessing.
Compliant list practices before your first send
The channel being effective is exactly why the list discipline has to be real. The rules below are the baseline, and none of them are optional at bulk volume.
- Have a consent basis you can point a lawyer at, stored per contact. The TCPA applies to iMessage the same way it applies to SMS.
- Scrub prior opt-outs before every campaign, across every channel you run. Revocation must be honored within 10 business days under the FCC's revocation rules, in effect since April 11, 2025.
- Identify yourself in the first message. A named sender with a real reason to reach out collects replies; an anonymous blast collects junk reports.
- Run an availability check first and write separate copy for the fallback path, so Android contacts get a message written for the format it arrives in.
- Segment and personalize. A thousand identical messages is the exact pattern that gets a channel degraded, on every platform, on every rail.
- Cap the first campaign small, read the reply and opt-out rates, then scale. Opt-out rate is the earliest warning you get that the list or the copy is wrong.
Where Blue Reacher fits
Blue Reacher is a B2B iMessage platform: unlimited iMessages (50 opted-in / 30 cold new contacts a day) per line, availability checking, campaigns and sequences, STOP auto-detection, RCS then SMS fallback, no A2P registration required. Pricing is public: $249 per line per month, or $1,949 per line per year (about $162/mo), on the pricing page.
You already paid for the lead. The channel is why they never replied. Book your Blue Funnel Map, a 15-minute call, and we'll text you a demo from a live line so you see exactly what your list would see.
Frequently asked questions
Can I send a mass text from my iPhone without a group chat?
Not at real volume. Sending individually by hand does not scale past a few dozen messages, shortcuts that automate it produce identical messages in a burst, which is the pattern that gets deliveries failing, and your personal number has no opt-out handling. Past roughly 50 contacts, the working setup is a dedicated iMessage line on a sending platform, with each contact in their own thread.
How many people can be in one iMessage group thread?
32, per Apple's published limit. But the cap is the smaller problem: a group thread exposes every recipient's number to every other recipient and turns every reply into a notification for the whole group. For any customer-facing send, individual one-to-one threads are the only format that respects the recipient.
Is sending mass iMessages legal?
Yes, under the same rules as any business texting: appropriate consent under the TCPA, honest sender identification, and opt-outs honored within 10 business days under the FCC revocation rules in effect since April 11, 2025. Statutory damages run $500 to $1,500 per message, so the consent and suppression machinery is not optional. Our guide to iMessage marketing legality covers the details.
What happens to contacts who don't have iMessage?
On a proper platform they still get the message. Blue Reacher checks iMessage availability before the send, routes eligible contacts to the blue bubble, and falls back to RCS then SMS for everyone else. That check is also worth running for its own sake: it tells you what share of your list gets the full iMessage experience before you commit to copy.
How much does it cost to send bulk iMessages?
Blue Reacher prices per line rather than per message: $249 a month or $1,949 a year per line, with unlimited iMessages, so the cost of a 5,000-contact campaign and a 500-contact campaign is the same flat fee. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered. Per-segment SMS pricing catches up fast at volume; the crossover math is in our iMessage vs SMS comparison.
Keep reading
More on imessage outreach
iOS 27 Changes What Counts as a Reply
Apple is shipping a Messages update this fall that rewrites three things a sales team measures without touching a single thing a sales team does. Reactions stop being text. Suggested replies start sounding like the person sending them. Failed sends retry without telling anyone. None of that is a feature announcement for outbound, and all of it lands in your numbers.
Blue Bubble vs Green Bubble: What the Color Does to Reply Rates
The bubble color is a compressed trust signal, and it changes how a sales message gets treated before a word is read. Here is the mechanics of what each color means, how iOS filters unknown senders, and what that does to response behavior when the sender is a business.
iMessage Team Inbox: How Sales Teams Share One Line
Consumer iMessage was built for one person, so teams that want shared visibility need a different architecture: dedicated business lines whose threads sync into the CRM. What that looks like in practice, what to require from any setup, and where standalone inbox apps fit.
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