Send iMessages from Intercom
The short answer
Yes. Intercom events and workflows fire webhooks that send blue-bubble iMessages through Blue Reacher, so the trial going cold or the churn-risk signal gets a text instead of another email. The conversation lives in Blue Reacher or your CRM, with replies and delivery states posted back over webhooks. No A2P registration required, $249 per line per month.
Key takeaways
- Intercom's blind spot is the user who stopped showing up.
- Through the API and webhooks, not a first-party app; Blue Reacher is native on GoHighLevel, HubSpot, Close, Salesforce, Pipedrive and Follow Up Boss, and the white-glove team wires Intercom for you during onboarding.
- iMessage doesn't appear as a channel inside the Intercom inbox.
- White-glove onboarding is included: one call where the team picks the two or three lifecycle moments worth texting, wires the webhooks or Zaps against your Intercom events, and writes the first message set with you.
How a message falls back
Why add iMessage next to Intercom at all?
Intercom's blind spot is the user who stopped showing up. The trial that went quiet on day 9, the champion who hasn't logged in, the expansion conversation nobody opened. Every tool you'd normally reach them with lands in the same ignored inbox.
- iMessage is the one channel those people still read. A blue-bubble text from the CSM or founder they talked to gets treated like a message from a person. Blue Reacher customers see 2-3x the reply rate of cold email on lifecycle moments. Fin and Messenger keep handling in-product volume; iMessage handles the humans who left. No A2P registration required, so it's an onboarding call, not a compliance project.
How does the connection actually work?
Through the API and webhooks, not a first-party app; Blue Reacher is native on GoHighLevel, HubSpot, Close, Salesforce, Pipedrive and Follow Up Boss, and the white-glove team wires Intercom for you during onboarding. On the send side, whatever surfaces your signal, an Intercom workflow reaching a webhook step, an event landing in your warehouse, or a Zapier trigger watching Intercom, calls the Blue Reacher API with the user's number and a message built from their attributes: plan, trial day, last-seen, the feature they stalled on.
- On the return side, replies, per-message delivery states, and opt-outs post to your webhooks. Most teams write them into the CRM or back onto the Intercom contact as events and attributes via the Intercom API, so segments and workflows can react: a reply pauses the win-back series, a delivered-but-silent state escalates to a call task. STOP is detected and the contact suppressed automatically, and non-iMessage users get RCS then SMS fallback.
- Trial day 9, no activation event: a text from the AE who ran the kickoff, not onboarding email #6
- Health score drops or usage falls off: the CSM's line opens a real thread before the renewal call
- Fin resolves a billing question that smells like churn: route the account to a human over iMessage
- Closed-lost 90 days ago: a two-line revival text with a voice memo outperforms the re-nurture sequence
What stays honest about this setup?
iMessage doesn't appear as a channel inside the Intercom inbox. Your team replies from Blue Reacher or your CRM. This is a B2B lifecycle channel, not a broadcast tool. Dedicated lines, personal messages, opt-outs honored automatically. That's what keeps reply rates at 2-3x, and it's the only way Blue Reacher builds this.
Setup and pricing
White-glove onboarding is included: one call where the team picks the two or three lifecycle moments worth texting, wires the webhooks or Zaps against your Intercom events, and writes the first message set with you. Most teams send within a week. $249 per line per month with unlimited iMessages ($199 at 4+ lines), or $1,949 per line per year, about $162.50 a month, with the $449 activation waived on annual. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.
Frequently asked questions
Does Intercom support iMessage as a channel?
No. Intercom's channels are Messenger, email, and the other surfaces it manages natively; iMessage isn't one of them. Blue Reacher adds iMessage alongside Intercom: Intercom's events and workflows trigger the sends over webhooks, and the conversation itself lives in Blue Reacher or your CRM.
Can Fin hand a conversation off to iMessage?
Not directly, but the pattern works through your routing: when Fin or an inbox rule tags an account as needing a human (churn risk, pricing question, escalation), that event can fire a webhook that opens an iMessage thread from the account owner's line. The handoff is an automation you own, wired during onboarding.
Do replies show up in Intercom?
Replies post to your webhooks, and from there you can write them onto the Intercom contact as events or attributes via the API, or into your CRM, which is where most teams want them. The full thread always lives in Blue Reacher. Delivery states and opt-outs flow the same way.
Do we need A2P registration to text users?
No A2P registration required. Sends go out over iMessage from your dedicated line, falling back to RCS then SMS for users who can't receive iMessage. STOP replies are auto-detected and suppressed.
What does it cost next to an Intercom subscription?
$249 per line per month, unlimited iMessages, no per-message or per-seat fees. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered. $199 per line at 6+, or $1,949 per line per year (about $162.50 a month) with the $449 white-glove activation waived. Most SaaS teams start with one line per CSM plus one for lifecycle automation.
See it live on your lifecycle moments
Book a demo and bring the segment that ignores your emails: stalled trials, quiet accounts, closed-lost. We'll trigger a real blue-bubble send from one of your signals on the call and watch the reply come back.