Jump to section
01
Sits on top of Intercom, not in place of
Intercom is one of the best-built support inboxes on the market. The conversation view, the macro tooling, the way agent assignment and team inboxes are organized, the speed of the messenger itself — those are not things to throw away. If your team lives inside Intercom every day, ripping it out to chase a cheaper alternative is rarely the right move.
The gap shows up in two places. First: the cost structure of layering AI on top, which scales with conversation volume rather than seat count. Second: reach. AI deployed inside Intercom answers on the channels Intercom natively supports. If your customers also message you on WhatsApp, Instagram DMs, Messenger, or Telegram and you want one AI agent answering them all the same way, you’re stitching a multi-channel story together with extra tools.
NebulaHex doesn’t try to replace the Intercom inbox. It answers from your Intercom Help Center on every channel it covers, including the ones Intercom doesn’t. When a website visitor taps Talk to a human, on a bot with live chat handoff switched on (it is off by default), the conversation comes to your team in the NebulaHex inbox; today nothing is handed into Intercom.
Flat fee
Subscription pricing, not per-resolution. Bring your own AI key on higher tiers to remove the message ceiling entirely.
Multi-channel
Same bot answers on website widget, WhatsApp, Instagram, Messenger, and Telegram. One knowledge base, one inbox.
Model choice
Claude or GPT. You’re not locked to a single vendor for both the inbox and the AI brain.
02
What the integration does
Once Intercom is connected, the Configure Tools panel lists ten Intercom tools, which this page groups into reads, writes, and tag management. Two run during a conversation today: Help Center search and contact lookup. The others are locked off, or, for the writes and tagging, refused even when switched on. Like every integration tool, the two run only when your agent answers with a Claude model.
Your Help Center stays the source of truth. The bot searches the same articles your team writes for the same Help Center your customers already use. Each search is live and returns an article’s title, the first 300 characters of its text and its link, so after you update an article in Intercom the next search sees the new version, and the bot answers from that opening text and can link the full article.
03
What the bot writes to Intercom
The Intercom integration has the same two write patterns as our other CRM-and-helpdesk connectors. Today neither one runs for Intercom, so the bot writes nothing into your workspace.
Pattern 1 · Event-driven write · not running today
When the bot captures a name and email mid-chat, lead.captured fires, but the Intercom connection subscribes to no events, so no Intercom contact is created or updated. The lead stays on your NebulaHex Leads page.
Pattern 2 · Tool-driven write · not running today
The tools that would open a Conversation or a Ticket, post a reply, or add a tag in Intercom are refused today, on every surface, even when switched on. Escalations do not open anything in Intercom either: they go to your team in the NebulaHex inbox.
04
Multi-channel reach
The Intercom Messenger is great for your website. Your customers also reach out elsewhere. NebulaHex covers five channels with one bot, and on every one of them it can answer from your Intercom Help Center. The conversations themselves stay in NebulaHex, not in Intercom.
One bot, five channels, one Intercom Help Center
NebulaHex bot
One knowledge base. One brain.
Every answer can draw on your Help Center
Intercom Help Center
The articles your team already writes
You don’t need a separate bot per channel. The conversations stay in NebulaHex, and none of them arrive as Intercom Conversations today.
05
How to connect
Three steps. The shortest setup of any of our CRM-or-helpdesk integrations — no region picker, no API key to paste, no department to choose.
Click Connect on the Intercom card
In your bot’s Integrations tab. The card opens Intercom’s standard OAuth screen. You sign in to the workspace you want to connect and approve the scopes NebulaHex needs.
Workspace recognized, card flips connected
You return to NebulaHex; the card shows your Intercom workspace name and a green status pill. No region picker, no PAT to paste. The whole exchange is OAuth 2.0.
Check the lookups
Help Center search and contact lookup are on from the start, and they are the two tools that run today. Ticket creation, tagging and replies can be switched on but do not run yet.
Because the connection is OAuth-based, you can revoke NebulaHex’s access from inside Intercom at any time, the same way you can revoke any installed app. Your bot in NebulaHex shows the connection as broken so you know to repair or remove it. The bot creates nothing in your workspace today. Coming soon: Contacts, Conversations and Tickets the bot creates for a visitor who proves their email address, which will stay in Intercom when you disconnect, exactly where your team expects to find it.
06
Real use cases
A SaaS team already paying for Intercom seats
Forty-person SaaS, support team of six lives in Intercom. You evaluated AI add-ons, liked the resolution quality, but the projected per-resolution bill at your conversation volume was higher than your headcount budget. You parked it. NebulaHex gives you a different option: connect your Intercom workspace, point the bot at your existing Help Center, turn on the website widget. The bot answers routine questions without paging anyone. Escalations land in your NebulaHex inbox with the whole conversation; they are not handed into Intercom today. Your monthly AI bill is flat — not a per-resolution meter.
E-commerce expanding to WhatsApp and Instagram
You sell direct-to-consumer. Intercom has been your support hub for years and your team is fast inside it. But customers in Latin America message you on WhatsApp, your Instagram store gets DMs, and lately you’ve seen Telegram traffic from a community that grew around your brand. Right now those threads are answered by a part-timer copying replies between apps. Connect NebulaHex, plug in WhatsApp and Instagram, connect Intercom for Help Center search. One bot answers on 5 channels from the knowledge you give it; when a website visitor taps Talk to a human, on a bot with live chat handoff switched on (it is off by default), the conversation comes to your team in the NebulaHex inbox.
A mid-market team replacing the AI add-on, not the inbox
You didn’t love the lock-in of buying AI from the same vendor that owned your inbox. You wanted to choose your model — Claude or GPT. You wanted leverage on pricing. NebulaHex’s Bring Your Own Key option lets you connect your own AI provider account. The bot uses your model, you pay the model provider directly, and your message volume stops mattering for the AI cost line. Intercom keeps doing what it’s good at — inbox, macros, team management. NebulaHex provides the AI brain and the multi-channel reach.
A startup on Intercom’s lower tier
You’re early. You’re on Intercom’s lower tier because the inbox is the right product for your three-person team. Layering enterprise AI on top is out of budget, but your founder is fielding every “how do I do X” question and that’s not scalable past your first hundred users. Sign up for NebulaHex’s Free plan, point a bot at your docs and landing page, embed the widget. Your founder stops being the answer key for password resets. Live chat handoff starts on the Pro plan: there, when a visitor taps Talk to a human in your website widget, on a bot with live chat handoff switched on (it is off by default), the conversation goes to the NebulaHex inbox; it is not handed into Intercom today.
07
What Intercom is, and where it sits
Intercom started as a customer-messaging tool and grew into a full support platform with a helpdesk, an in-product messenger, a help center, automation rules, and Fin — its own AI agent. The brand sits firmly in the support-tool category. Companies use it because the inbox feels modern, the conversation view collapses email, chat, and SMS into one place, and the customer-facing messenger is one of the most polished in the industry.
Fin is Intercom’s AI agent. It connects to external APIs through Intercom’s data connectors and is priced on a per-resolution model — fair as a pricing structure, and a meaningful line item at higher conversation volumes. For teams that resolve a lot of conversations, the math scales linearly with success.
NebulaHex’s positioning relative to Intercom isn’t “we replace it.” It’s “we add an AI brain on a flat subscription, on every channel your customers actually use, and we search your Intercom Help Center so the answers point to what your team already wrote.” Today, when a website visitor taps Talk to a human, on a bot with live chat handoff switched on (it is off by default), the conversation lands in the NebulaHex inbox rather than in Intercom.
08
NebulaHex vs Fin, honestly
Fin is a strong product. We’re not going to pretend otherwise. For teams already deeply invested in a customized Fin deployment with a year of Custom Answers tuning behind it, our AI layer is a step sideways, not forward. The teams who get the most out of NebulaHex on top of Intercom are the ones who:
- →Want flat-fee AI economics rather than per-resolution metering as they scale
- →Need a single AI brain answering on WhatsApp, Instagram, Messenger, or Telegram in addition to Intercom
- →Want model choice (Claude or GPT, or your own AI provider key) instead of being locked to one vendor for inbox and AI
- →Are on Intercom’s lower tiers where adding a per-resolution AI layer is out of budget
You can coexist with Fin. During a chat, NebulaHex only reads from Intercom — Help Center search and contact lookup — so you can run Fin for what Fin is best at and use NebulaHex for the channels and economics Fin doesn’t cover. The two don’t fight each other over writes.
09
Trust & security
Your Intercom connection credentials are encrypted at rest and in transit. The connection uses OAuth 2.0 — you never paste an access token into NebulaHex, and you can revoke our access at any time from inside your Intercom workspace’s app settings. Tokens we hold on our side are encrypted before they’re stored.
Access to your bots, channels, and integrations is gated by role-based permissions. Owners and admins can connect or disconnect Intercom; members work the shared inbox; viewers have read-only access. Sensitive actions require confirmation. Outbound connections to Intercom’s API are pinned at the network layer to defeat redirect-based attacks.
We don’t use your conversation data — or anything we read from your Intercom workspace — to train AI models. If you want full control of where prompts and responses go, the Bring Your Own Key option routes everything through the AI provider account you choose, on your terms with that provider. See our privacy policy and terms.
10
Keep your Intercom inbox. Add the AI layer.
You don’t need to commit to a plan to try this. Sign up for the Free plan, build a bot on your knowledge, embed the widget, and see how the AI handles your real questions. When you’re ready to add Intercom, click Connect on the Intercom card.
Your Intercom inbox stays the inbox.
We add a five-channel front door and a flat-fee AI brain that answers from your Help Center. Sign up for free, build the bot, connect Intercom when you’re ready.