"Can we text customers over iMessage?" usually means one of two things. Some teams want a chat button on their website or Apple Maps listing that opens a conversation in Messages. Others want their outbound texts to show up blue on iPhones, with the business name and photo instead of a bare 10-digit number. Apple built a product for the first. The second is a different kind of service, and it has its own price, limits and rules.
This guide covers both. It explains what each one requires, what blue-line texting costs with worked math, what happens with Android users, and where the approach doesn't fit. We make Ready, which sells the second kind (we call it a blue line). The comparison tries to be fair, because many businesses only need one of these, and some need neither.
The two things people mean by "iMessage for business"
Apple Messages for Business
Apple Messages for Business is Apple's own service. The defining trait is that the customer starts the conversation. They tap a Messages button in Safari, Maps, Search or your app, and a chat opens. You can't send the first message cold. You register your brand with Apple and connect through one of Apple's approved messaging service providers, which supplies the agent console.
It works well for inbound support: order questions, booking changes, "is this in stock." It is a poor fit for appointment reminders, shipping notices or follow-ups, because those are messages you need to send first. We cover setup and the provider landscape in Apple Messages for Business: setup, requirements, pricing and providers.
Blue-line texting (business-initiated iMessage)
The second kind sends your texts as iMessage from a dedicated line, so they render blue on an iPhone and show your business name and photo. The difference that matters most is that you can text first. That makes it usable for the same jobs people use SMS for, such as follow-ups, reminders and replies to a form fill, with a different delivery channel to iPhones.
Ready's blue line is this second kind. It is not Apple Messages for Business, and we don't describe it as such.
Quick comparison
| Apple Messages for Business | Ready blue line | |
|---|---|---|
| Who starts the chat | Customer only | Business can text first |
| Entry points | Buttons in Safari, Maps, Search, your app | Any phone number you have consent to text |
| Setup | Apple brand registration plus an approved provider | Set up a line; no 10DLC registration needed |
| Android users | Not reachable through it | Fall back to SMS from your regular number |
| Shows business name/photo | Yes | Yes |
| Best for | Inbound support chat | Two-way conversations you start or continue |
Requirements: what you need before the first blue text
Apple Messages for Business requirements
You need a verified brand with Apple, a messaging service provider, and entry points placed where customers will find them. Because the customer starts every thread, consent questions are simpler. Your volume, however, depends on how many people tap the button.
Blue line requirements
A blue line needs no 10DLC registration, so a business can start texting as soon as the line is set up. That is the main speed advantage over SMS. On SMS, most approvals take 2 to 7 days, and unregistered traffic gets carrier-filtered.
Two caveats are worth stating plainly:
- Android fallback still runs on SMS. Texts to Android phones go from the account's regular number. If the account already had a number they bill at the regular text price; if the blue line came with its green number, they bill at 6 cents a segment once the account registers. That regular number follows normal SMS rules. An account can send up to 500 texts a month before it registers. After that, it has to register for 10DLC: $25/mo for registration and $2/mo per number, with the first month ($25) charged at submit. If a meaningful share of your contacts use Android, plan on registering anyway. Our 10DLC cost breakdown itemizes every fee.
- Consent still applies. iMessage delivery doesn't change who you're allowed to text. Text people who opted in or who already talk to you. Consent records are your responsibility; keep the opt-in time, wording and source on your side.
What blue-line texting costs
Ready blue-line pricing:
- $99 a month per line
- 6 cents a segment for each text sent
- 6 cents a segment for each reply received on the blue line
- Reactions are free
- Texts to Android go from your regular number: $0.0075/segment plus a $0.0045 carrier fee if you already had a number, 6 cents a segment once you register if the blue line came with its green number
A segment is 160 GSM-7 characters, or 153 per part when a message runs longer. An emoji drops the limit to 70 characters (67 per part). Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so those never change the count.
Worked example: a service business texting existing customers
Assumptions, stated up front:
- 1,000 customers texted in a month, all of whom opted in
- Each conversation averages 2 outbound segments and 1 reply segment
- An assumed 60/40 iPhone-to-Android split (check your own contact data; it varies by audience and region)
iPhone side (blue line):
- 600 contacts × 3 segments = 1,800 segments
- 1,800 × $0.06 = $108
- Plus one line at $99
- Blue-line subtotal: $207
Android side (SMS from your regular number):
- 400 contacts × 3 segments = 1,200 segments
- 1,200 × $0.0075 = $9, plus 1,200 × $0.0045 in carrier fees
- Plus 10DLC registration if you're past 500 texts a month
Same month, all SMS instead:
- 3,000 segments × $0.0075 = $23, plus 3,000 × $0.0045
The blue line costs noticeably more. In this example, the blue-line month comes to about $221 with carrier fees against about $36 all SMS, so it adds roughly $185, and both setups need 10DLC registration for their SMS. You're paying for the blue bubble, the business name and photo, and texting without waiting on registration. Whether that's worth it depends on what a reply is worth to you.
For a business where one booked job covers the monthly difference, the math often works. For a high-volume, low-margin notification stream, plain registered SMS is usually the better call. These figures exclude the optional compliance surcharge: scrubbing and landline validation are $0.003 extra per segment each when switched on, and both are off by default. For a longer cost discussion, see Blue bubble texting for business: cost, limits and when it beats green SMS.
The limits that shape how you use it
Blue lines are built for conversations, not bulk sends. The limits reflect that.
- Unlimited texting with people you already talk to. Existing threads aren't capped.
- Up to 50 new conversations a day per line. In the example above, if all 600 iPhone contacts were new to the line, one line would take 12 days to reach them all.
- Up to 2 texts to someone until they reply. No third nudge into silence.
- Photos only after they reply. Your first message is text.
- Campaigns and drip campaigns send from regular numbers, not the blue line. Bulk outreach stays on SMS.
If you need more new people a day, add another line. The "Add lines automatically" setting can add one when the day's new-conversation allowance runs out. Each added line is another $99 a month, so size this deliberately. For a practical sizing exercise, see 50 new conversations a day per line: sizing blue lines for an ecommerce support inbox.
These limits favor certain workflows:
- Replying to inbound leads and form fills
- Ongoing customer conversations, such as service updates, scheduling and support
- Follow-ups to people who already know you
They work against cold outreach, which you shouldn't be doing by text anyway, and against high-volume promotional sends.
Android fallback: how one thread handles both colors
iMessage only exists on Apple devices. When a contact is on Android, the text goes from the account's regular number as SMS. If the account already had a number, those texts bill at the regular price. If it had none, the blue line comes with a green number, and once the account registers its texts bill at 6 cents a segment.
Replies, reactions, typing indicators and group chats from the blue side land in the same inbox thread as SMS. Your team works one conversation per contact regardless of device. The contact sees blue on iPhone and green on Android. Our post on whether iMessage works on Android goes deeper on device behavior and where RCS fits in.
How Ready delivers it for platforms and teams
The blue line is part of the same platform as Ready's SMS. That matters if you run a CRM or vertical SaaS product that texts on behalf of your customers. Each customer gets a sub-account with its own numbers and registration. Blue lines sit alongside those numbers and share one inbox and one REST API.
What you get around the blue line:
- One API for blue and green. The blue line guide and the blue line API reference cover setup and sending. SMS sends use
POST /v1/messages, documented at docs.tryready.com/api/messages. - Opt-out handling on the SMS side. Inbound STOP is honored and propagates across campaigns. Opted-out numbers are refused up front and not charged.
- Quiet-hours enforcement. A campaign or drip SMS in the recipient's quiet hours is held and sent later; a one-to-one or API SMS is held only if sending reopens within 6 hours, otherwise it is refused and you send it again. Texts are charged only when they send.
- GoHighLevel install. For agencies on GHL, Ready installs natively with two-way sync mapped per GHL location.
- Prepaid billing via Stripe, with carrier fees itemized separately.
Be honest with yourself about fit. If you only need inbound chat from your website and Maps listing, Apple Messages for Business through an Apple provider is the purpose-built tool. If your volume is mostly bulk notifications, registered SMS is cheaper per message. Raw carrier APIs like Twilio charge less per segment than our Standard rate, and that's worth knowing before you choose. The blue line earns its price in conversations where you send first and the reply matters.
The practical takeaway
- Customer-starts-the-chat support: Apple Messages for Business.
- Business-starts-the-chat, two-way conversations to iPhones: a blue line at $99/mo per line plus 6 cents a segment, with no 10DLC wait.
- Android contacts and bulk campaigns: registered SMS at $0.0075/segment plus $0.0045.
- Plan for the limits: 50 new conversations per line per day, 2 texts before a reply, and photos only after a reply.
A sensible first step is to pull your contact list and estimate the iPhone share. Then rerun the worked example with your own volume. If the numbers make sense, the blue line docs walk through setup, and you can create an account to try it. Pricing for the SMS side is on the pricing page.