Send iMessages from Outreach
The short answer
Yes. Outreach triggers and its API fire a webhook when a prospect hits the moment you choose: a sequence step, stage change, opened-but-silent signal. That webhook sends a blue-bubble iMessage through Blue Reacher from the rep's dedicated line. Replies and delivery states post back over webhooks to update the prospect. No A2P registration required; white-glove onboarding wires it.
Key takeaways
- Because the sequence math has stopped working on email alone.
- Through the API and webhooks, not a marketplace tile.
- One dedicated line per rep, matching how Outreach already assigns prospect ownership, so the thread belongs to the person whose name is on the sequence.
- One onboarding call: the Blue Reacher team maps which sequence moments should text, wires the trigger-to-webhook path and the reply write-back, and drafts the first templates with your enablement lead.
How a message falls back
Why add iMessage to sequences that already run email and calls?
Because the sequence math has stopped working on email alone. Reply rates on cold email keep sliding, dials connect less every year, and the LinkedIn step drowns in everyone else's. The channel where B2B buyers answer strangers writing like humans is the text thread, and iMessage is that thread at its most personal: blue bubble, read receipts, it's the rep's line.
- Slot it in without changing the playbook: same sequences, same prospects, one added touch at 2-3x cold email reply rate. Booking teams carry that lift through. No A2P registration means adding the channel doesn't send RevOps into a 10DLC queue.
How does Blue Reacher plug into an Outreach motion?
Through the API and webhooks, not a marketplace tile. Blue Reacher is native on GoHighLevel, HubSpot, Close, Salesforce, Pipedrive, Follow Up Boss. The pattern uses Outreach triggers and API events (directly, Zapier, or middleware) to fire sends at moments you define. Reaching the "text now" step, stage advancing after a demo no-show, email opened twice silent: each becomes a webhook call sending a personalized iMessage from the owning rep's line.
- Return traffic keeps Outreach truthful. Replies, delivery states, and opt-outs post to your webhooks, and middleware writes them back through the Outreach API: log the reply on the prospect, mark them replied so the sequence pauses instead of emailing someone mid-conversation, or push a task to the rep. STOP replies are detected and suppressed by Blue Reacher automatically, and non-iMessage contacts fall back to RCS, then SMS, so the touch never just vanishes.
Touch 3-4 reply rate
- Email-and-phone sequence
- Cold email baseline
- With an iMessage step
- 2-3x cold email on the iMessage touch
No-show follow-up
- Email-and-phone sequence
- Another email into the pile
- With an iMessage step
- A text from the rep's line within minutes
Compliance lift
- Email-and-phone sequence
- A2P 10DLC registration for any SMS step
- With an iMessage step
- No A2P registration required
Reply handling
- Email-and-phone sequence
- Native for email, absent for texting
- With an iMessage step
- Webhooks pause the sequence and log the reply
Cost per touch
- Email-and-phone sequence
- Per-message SMS fees at volume
- With an iMessage step
- Unlimited iMessages (50 opted-in / 30 cold new contacts a day), $249 per line per month
How do reps actually work the channel?
One dedicated line per rep, matching how Outreach already assigns prospect ownership, so the thread belongs to the person whose name is on the sequence. Reps answer replies in Blue Reacher (or your CRM, where threads also sync), and the reply event lands in Outreach so reporting still tells the truth about what's working.
- Sequencing discipline carries over: Blue Reacher supports scheduled sends and its own multi-touch sequences, so you can either fire one-off texts from Outreach moments or enroll a prospect into an iMessage cadence and let Outreach handle everything else. White-glove onboarding tunes message intent so texts read like the rep, not like step 4 of 12.
Setup and pricing
One onboarding call: the Blue Reacher team maps which sequence moments should text, wires the trigger-to-webhook path and the reply write-back, and drafts the first templates with your enablement lead. Most teams have the step live within a week. $249 per line per month with unlimited iMessages (50 opted-in / 30 cold new contacts a day), $199 per line at 6+ (a full SDR pod qualifies), or $1,949 per line per year, about $162.50 a month, with the $449 activation waived on annual billing.
Frequently asked questions
Is Blue Reacher in the Outreach marketplace?
No. The connection runs through the Blue Reacher API and webhooks, driven by Outreach triggers and API events, directly or via Zapier or middleware. The white-glove team wires it during onboarding; what you give up versus a marketplace app is a logo on a listings page, not functionality.
Can a reply pause the Outreach sequence?
Yes, and it should. Replies post to webhooks the moment they arrive, and the write-back marks the prospect replied through the Outreach API so the sequence stops. Nothing torches a warm thread faster than step 5's email landing mid-conversation.
Does each rep need their own line?
One line per rep is the recommended shape, mirroring prospect ownership in Outreach, at $249 per line per month ($199 at 4+ lines, which most pods hit). Threads then genuinely belong to the rep whose name signs them, which is a real driver of the reply rate.
What about prospects without iMessage?
Blue Reacher checks availability per contact before sending. Non-iMessage prospects get the same message over RCS, then SMS, automatically, and the delivery state posts back so your reporting knows which channel carried each touch.
Do we need A2P 10DLC registration for the texting step?
No A2P registration required with Blue Reacher, which is normally the slowest part of adding any texting step to a sales stack. STOP opt-outs are detected and suppressed automatically, keeping the motion compliant without RevOps maintaining lists.
See it live inside your sequence
Book a demo and bring one underperforming sequence. We'll wire its key moment to a real send on the call, show the reply pausing the sequence, and price the pod.