Most of this site explains how to use this channel well. That is a bias, and the honest correction is a page that says when not to bother. Every item below is a real reason to walk away, not a soft objection with a workaround attached.
1. Nobody can answer replies
This is the disqualifier. The entire advantage of iMessage is that it feels like a conversation, and a conversation nobody answers is worse than an email nobody expected a reply to. If you cannot commit a named person to responding within business hours, use email. Who answers.
2. Your list is not consented
A purchased list, scraped numbers, or contacts who gave you a number for a receipt are not consent. In the US, TCPA carries statutory damages per message and does not exempt business-to-business. This is not a risk to manage — it is a reason not to start. The legal position.
3. Your customers are mostly on Android
If your customer base skews heavily Android, you are paying for a line to reach a minority and falling back to SMS for the rest — at which point you are running an SMS programme with extra steps. Check before you buy: your booking system or CRM may already know, and if it does not, a lookup endpoint will tell you.
4. The content is long, or needs keeping
Quotes, contracts, invoices, warranty documents, anything with a table in it. These belong in an inbox where they can be found in six months. Sending them by message is a worse experience for everyone.
5. You want a marketing channel
This is the most common mismatch
Businesses buy an iMessage line hoping for an email-marketing replacement with better open rates. The channel does not tolerate that frequency: promotional volume produces opt-outs and blocks far faster than in email, a block is permanent, and it counts against your line's health. If the plan is a weekly send to a list, this is the wrong purchase.
6. You need it to be officially sanctioned
If your security review, your regulator or your own risk appetite requires that a vendor operates with the platform's permission, no provider in this category qualifies. Apple publishes no iMessage API. Apple Messages for Business is the sanctioned option, and it can only answer conversations the customer starts — if that does not fit, the honest answer is not to use iMessage at all.
7. You cannot measure it
Not "you do not have analytics" — you can build that. This means you genuinely cannot tell whether an outcome happened: no booking system, no CRM, no record of who came back. Without a baseline you will not know whether the line is worth its fee, and unmeasured line fees get cancelled at the first cost review regardless of whether they were working. Build the baseline first.
What to do instead
| If your blocker is | Do this |
|---|---|
| Nobody answers replies | Email with a clear "do not reply", or fix the staffing first |
| Consent | Build a consented list properly, then revisit |
| Android-heavy base | RCS through a CPaaS, with SMS fallback |
| Long content | Email, always |
| Wanting a marketing channel | Email. It is better at this and always was |
| Needing official sanction | Messages for Business, or nothing |
| No way to measure | Fix the measurement, then reconsider |
If none of the seven apply, the channel is probably worth trying — and the free sandboxes mean finding out costs nothing. Where to start.