Limited offer

Build with our iMessage API/MCP. Get our sandbox for free.

Integrations

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.

$249 per line per month, published No A2P registration required 50 opted-in / 30 cold new contacts a day, unlimited replies
Industry and support platforms

7 tools in this group

Trigger

Intercom

Under 9 seconds

Send iMessage

Result

Reply back in Intercom

iMessage

Hi Alex, following up on your demo request. Worth a quick chat this week?

Sent from your Intercom workflow

Yeah, tomorrow works.

Key takeaways

  • Intercom's blind spot is the user who stopped showing up.
  • Through the API and webhooks, not a first-party app; the white-glove team wires Intercom at onboarding.
  • iMessage doesn't appear as a channel inside Intercom.
  • White-glove onboarding is included: one call to pick lifecycle moments worth texting, wire the webhooks or Zaps against Intercom events, and write the first message set.

How a message falls back

How a message falls backEvery message is attempted as iMessage first, falls back to RCS if the number cannot receive iMessage, and falls back to SMS if it cannot receive RCS, so the message arrives either way.iMessageBlue bubble, read in minutesRCSIf the number is Android and RCS-...SMSIf neither, so it still arrives
Every message is attempted as iMessage first, falls back to RCS if the number cannot receive iMessage, and falls back to SMS if it cannot receive RCS, so the message arrives either way.

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 reach tool lands in the same ignored inbox.

  • iMessage is the one channel those people read. Blue-bubble text from CSM or founder reads like a person. Customers see 2-3x reply rates versus cold email.
  • Fin and Messenger handle in-product volume; iMessage handles users who left. No A2P registration required, just an onboarding call.

How does the connection actually work?

Through the API and webhooks, not a first-party app; the white-glove team wires Intercom at onboarding. An Intercom workflow, warehouse event, or Zapier trigger calls the API with the user's number and attributes.

  • Replies, delivery states, and opt-outs post to webhooks. Write to CRM or Intercom contact as events so segments react: replies pause win-back, silent escalates to calls.
  • STOP detected and contact suppressed automatically. 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 Intercom. Your team replies from Blue Reacher or your CRM.

  • This is a B2B lifecycle channel, not broadcast. Dedicated lines, personal messages, opt-outs honored automatically.
  • Reply rates hit 2-3x because of how it's built.

Setup and pricing

White-glove onboarding is included: one call to pick lifecycle moments worth texting, wire the webhooks or Zaps against Intercom events, and write the first message set. 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, $449 activation waived. Lines pace at 50 opted-in / 30 cold new contacts daily; replies unmetered.

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/line/mo, $199 at 4+, or $1,949/year (~$162.50/mo). Unlimited iMessages, pace 50 opted-in / 30 cold new daily, replies never metered. Waive $449 on annual.

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.