A1 Media × Blooio — iMessage infrastructure for a HighLevel lead-gen agency.
Blue Bubbles Inside Every Client's GHL Account
A1 Media is a lead-generation agency for the insurance and financial services space — life insurance producers, annuity specialists, and independent financial advisors. Their model is hands-on: they run the ads, they nurture the leads, and they deliver appointment-ready prospects straight into the client's own GoHighLevel sub-account.
Because every agent runs on their own GHL instance, A1 isn't one account with 50 lines — they're seven separate Blooio organizations: one line A1 runs for their own agency outreach, plus six more, one per producer client, all operated by the same A1 team. Every new producer they onboard gets their own dedicated number, fully integrated with their GHL workflows, with A1 managing the messaging on the client's behalf.
Before Blooio, A1 was stitching this together with MyCRMSim — a cheaper iMessage option that was "too technical" to scale across clients. They knew iMessage mattered because the response they got from blue bubbles was dramatically better than GHL's native Twilio SMS. So they went looking for a real iMessage provider for business — and found Blooio through YouTube.
Seven lines, one operator
A1 runs one iMessage line for their own agency outreach and six more on behalf of producer clients — each a separate Blooio organization so the number, the GHL integration, and the billing sit inside the producer's own business. A1 manages every line from a single pane of glass.
A1's own line
Agency outreach
Producer #1
Life insurance
Producer #2
Life insurance
Producer #3
Life insurance
Producer #4
Life insurance
Producer #5
Financial services
Producer #6
Financial services
The Challenge
Insurance and financial services leads are skeptical by default. When a follow-up text lands as a green SMS with an unfamiliar area code, it gets flagged as spam before the agent ever gets a chance to help. A1 needed every outbound to look like a real producer texting a real prospect — not an agency blasting a list.
The scaling problem was harder. Every new agent A1 onboards is a new GHL sub-account, a new set of workflows, a new line that needs to be iMessage-capable from day one. Whatever infrastructure A1 used had to plug into HighLevel on a per-client basis, survive credit and insurance follow-up sequences without getting numbers banned, and give A1 real visibility into whether leads actually received the messages.
MyCRMSim couldn't keep up. The setup was too technical, the GHL integration was fragile, and A1's delivery was regressing right as they needed to push harder on follow-up. (For the full feature comparison, see Blooio vs MyCRMSim.)
Why Blooio
Blooio gave A1 one purpose-built primitive: a dedicated iMessage line, native GHL integration, and a simple per-client billing model that scales one producer at a time. Every line is provisioned with iMessage, RCS, and SMS enabled, plugs directly into the client's GoHighLevel sub-account, and routes every outbound automatically based on which protocol the recipient can receive.
The result: across 5,177 outbound messages sent from A1's own line and their six client organizations in the first two and a half months on Blooio, 99% were successfully delivered — with 68% landing as native iMessage, 22% as RCS on Android, and the remainder falling back to SMS. Reply rate across unique contacts held at 36.3%. And the feature that changed A1's funnel math — inbound text links — opened a new lead channel that didn't exist before.
99% delivery success
Only 51 of 5,177 outbound messages failed across every line — even on multi-touch insurance follow-up sequences
Sub-two-minute reply
Median reply time of 1.9 minutes — because blue bubbles feel like a personal producer, not a mass-text platform
Inbound text links
463 tracked inbound clicks that bypass lead forms and start real iMessage conversations — closing at 1-in-6 vs 1-in-10 from standard funnels
Per-client scaling
Each new agent is a new org, a new GHL integration, and a new line — onboarded in hours, not days
Protocol distribution across A1's seven lines
More than two-thirds of A1's outbound volume lands as real iMessage — the exact thing MyCRMSim and Twilio-native GHL couldn't deliver reliably. RCS and SMS fall back automatically for recipients who can't receive iMessage.
Based on 5,177 outbound messages across A1's own line and six A1-managed client organizations, Jan 20 – Mar 31, 2026.
The inbound text link: A1's funnel hack
Instead of sending every ad click through a lead form, A1 routes a portion of traffic through a Blooio inbound link — a tappable link that opens the prospect's Messages app with a pre-filled text to the agent's iMessage line. There's no form to fill out. The prospect just hits send, and the agent gets a real iMessage conversation from a real phone number they can keep texting without being filtered as spam.
463
tracked inbound link clicks
1 in 6
close rate via inbound link
1 in 10
close rate via standard form
Close-rate comparison reported by A1 Media across their insurance & financial services funnels.
The inbound feature has been massive. It's turned into free leads for us — people who never would've filled out a form just tap the link, hit send, and they're in a real iMessage thread with the agent. Those leads close one out of six. Our standard form leads close one out of ten. That difference is worth tens of thousands of dollars a quarter.
The Results
In their first two and a half months on Blooio, A1 Media sent more than 5,100 outbound iMessages across their own line and six producer clients, reached nearly 1,000 unique prospects, and generated over 1,600 inbound replies. 36% of every contact A1 reached out to wrote back — a reply rate well above what most outbound insurance funnels see on green SMS.
Speed is where blue bubbles compound. Half of all prospect replies arrive within 1.9 minutes of A1 sending an outbound. When the first response lands that fast, agents can pick up the phone with context while the lead is still warm — instead of chasing them three days later through a filtered spam folder.
Month over month, A1's volume climbed as they onboarded new producers. February was the first full month on Blooio with 2,700+ messages; March nearly hit 4,000 (+58%) — all while delivery success held at 99%. That growth happened without A1 touching messaging infrastructure. They onboard the producer; Blooio handles the line.
Month-over-month growth across all seven lines
Infrastructure Blooio handles so A1 can focus on lead gen
- Per-client organizations— each producer gets their own Blooio org, their own dedicated number, and their own GHL integration, so the line and billing live inside the client's business.
- Native GoHighLevel integration — inbound and outbound messages flow through the client's existing GHL workflows, so A1's nurture sequences run on iMessage instead of Twilio SMS without rebuilding anything.
- Inbound text links — A1 places a Blooio link in ads and funnels; prospects tap to send a pre-filled iMessage, and the agent gets a real conversation instead of a form fill.
- Protocol fallback — iMessage by default, RCS for Android, SMS as a safety net — with no configuration from A1 or their clients.
- Volume-discount pricing — A1 bundles their Blooio cost into the client's service fee, and their per-line rate drops as they add producers.
Looking Forward
A1 is projecting twenty to thirty client producers on Blooio by end of year. To support that, they're consolidating their billing model — baking Blooio into their own service fee so clients see one price — and exploring annual commitments for pre-provisioned lines as they onboard new agents in bulk.
The niche stays tight: insurance and financial services, with a focus on producers who need both the lead-gen engine and the infrastructure underneath it to actually deliver. Blooio continues to handle the messaging — iMessage lines, GHL plumbing, inbound links, protocol fallback — while A1 focuses on what they do best: turning paid traffic into appointments that close.
Further reading
Want to build what A1 built? These guides and comparisons go deeper on the iMessage, HighLevel, and infrastructure pieces that power their stack.
Blooio × GoHighLevel
The native GHL integration A1 uses to run iMessage through their clients' existing workflows.
iMessage for GoHighLevel: Setup Guide
Step-by-step walkthrough for replacing Twilio SMS in GHL with blue-bubble iMessage.
Blooio vs MyCRMSim
Side-by-side comparison of the two iMessage providers A1 evaluated before switching.
MyCRMSim (external)
A1's previous iMessage setup — included for context on where they came from.
iMessage for Business
Why blue bubbles convert — the full playbook behind A1's outbound strategy.
iMessage + CRM
How iMessage plugs into modern CRMs like GoHighLevel, HubSpot, and Salesforce.
iMessage vs RCS
How A1's 68/22/9 iMessage-RCS-SMS split gets generated automatically behind the API.
Blooio Enterprise
Annual commitments and pre-provisioned lines — the path A1 is exploring as they scale to 20–30 producers.
Tailored case study
Another iMessage-on-the-back-end customer: 45K+ messages, 23K+ contacts, 97.5% delivery success.
Aneu case study
How an AI consumer app scaled to 139K messages in 60 days on Blooio infrastructure.
Running a HighLevel agency? Replace green SMS with Blooio.
Blooio plugs directly into every GHL sub-account with dedicated iMessage lines, inbound text links, and automatic protocol fallback — the same stack A1 Media uses to deliver leads to six producers with a 1-in-6 close rate. For teams scaling past 10 lines, our enterprise plans unlock annual commitments and pre-provisioned inventory.
