What iBlueText does, what it costs, what the limits are, and where the honest edges of the product are. If something here is not covered, email russ@ibluetext.com.
iBlueText is an iMessage platform for business. Three things: iPhone Lookup tells you which numbers on a list are on iMessage before you send; Campaigns send real blue-bubble iMessage from warmed Apple IDs on real hardware, falling back to green SMS or RCS automatically; and SMS Verify sends one-time codes for signups and logins. There is also an Inbox with two-way replies, AI auto-replies, a REST API, webhooks, a GoHighLevel integration and an SMPP interface.
Real iMessage. Messages are sent from dedicated, warmed Apple IDs signed in on real devices, so they arrive as blue bubbles with delivery and read receipts. If a recipient is not on iMessage the message falls back to green — RCS or SMS depending on the handset and carrier — so nothing is silently dropped.
It checks whether a phone number is registered for iMessage before you send. Blue-bubble messages get materially better engagement than SMS, so knowing which half of a list is on iMessage lets you target properly, avoid wasted sends and clean the list. Lookups are free up to 400 per line per day, then $0.005 each.
No card to start. Every new account gets 100 iPhone lookups, 10 SMS verifications and 10 real campaign messages — a free allowance for each service so you can test all three end to end. The campaign messages are genuine iMessage from our fleet; put your own number on the list and watch one arrive.
Lookups and verifications are a flat $0.005 each from prepaid credits. Ongoing sending needs a line at $99/month plus a $249 one-time setup, and each active line includes 400 free lookups per day. There are no per-message fees on top of the line.
No. We host the entire fleet — the hardware, the Apple IDs and the SIMs. You upload a list in your browser, or call the API, and we handle delivery.
Each line is capped at 50 new first-contact recipients per channel per day (15/day during a line's first five days while it warms up), plus 150 per channel per day to numbers that have not replied. Once someone replies, two-way conversation is unlimited. Over-cap sends hold and resume the next day rather than failing. More lines raise the ceiling proportionally.
Because the limits are what keep the numbers alive. iMessage is not a bulk SMS channel — Apple bans accounts that behave like spam infrastructure, and a banned Apple ID takes its whole message history with it. The caps are set to the level that keeps lines healthy long-term. If you need higher throughput, the answer is more lines, not a higher per-line rate.
Yes. If you already run a messaging platform, connect over SMPP v3.4 — the same protocol you use with SMS carriers — and send iMessage without writing to our REST API. Credentials are self-serve from your dashboard and go live in about a minute. Host smpp.ibluetext.com, port 3550, TLS only.
Yes. Each bind is a trunk and you choose the route by which bind you submit on. Most customers run two: an auto trunk (iMessage when available, green otherwise, with automatic fallback) and a green trunk that always sends RCS or SMS. On receipts: iMessage and RCS both confirm delivery so you get a real DELIVRD; plain SMS has no delivery receipt at all, so those return ACCEPTD.
No, and neither can anyone else. You choose green; the recipient's handset and the two carriers then negotiate RCS or plain SMS per message. What we do is report which one actually happened, so your delivery reporting reflects reality instead of an assumption.
Yes — a REST API for sending, lookups, verification, conversations and contacts, plus webhooks for inbound replies and delivery events. Authentication is a bearer API key you generate in the dashboard. See the API documentation.
There is a native GoHighLevel integration that puts iMessage into GHL conversations and workflows. Everything else connects through the REST API and webhooks, which covers Zapier, Make and n8n.
Opt-out handling is automatic and not optional. Any reply containing STOP, UNSUBSCRIBE, CANCEL, QUIT or END adds that number to your suppression list permanently, and the API then refuses to send to it. Consent capture and TCPA-oriented controls are built in.
You must have consent for the people you message. Cold, unconsented blasting is the fastest way to get a sending line suspended — by Apple, by the carrier, or by us. The platform is built for warm lists: customers, opt-ins, existing contacts and replies. If you do not have permission to message someone, this is the wrong tool.
iMessage works anywhere the recipient is on iMessage. For green messages, international delivery depends on the sending line's carrier plan, so international SMS/RCS is routed through a line that covers it.
We run many lines per machine rather than one Mac per line, and pass the saving on — $99 per line against their $149 to $1,000.
Create a free account, verify your phone, and you immediately have 100 lookups, 10 verifications and 10 real campaign messages with no card. Upload a list, run a lookup to see the blue/green split, and send a campaign to your own number first to see exactly what a recipient sees.
Still deciding? Start free — 100 lookups, 10 verifications and 10 real campaign messages, no card. Or read the API documentation and the SMPP guide.