Skip to main content
Integration · Intercom

Augment Intercom with AI knowledge answers

You already pay for Intercom. The inbox is sharp, your team likes the macros, the conversation view is the best in the business. NebulaHex sits on top of Intercom rather than in place of it — your AI agent answers from your full knowledge base on five channels and reaches into your Intercom workspace when it needs to.

OAuth 2.0 · 10 toggleable Intercom actions · Flat-fee, multi-channel

Intercom/Inboxapp.intercom.com / convo

Jordan Chen

Agile Helix · via Website Widget

JC
How do I export my conversation data to CSV?

You can export from Settings → Data → Export. CSV format includes all conversation fields.

📄 From your Help Center: “Exporting conversation data”

JC
Got it. But I need older data — can someone from your team help?
Of course. I’ve flagged this for our team — you’ll hear back within our SLA window.
Sara is typing…

Assignee

SK
Sara K.

Tags

bot-escalateddata-exportwebsite-widget

Contact

jordan.chen@agilehelix.com

Agile Helix

Source

NebulaHex bot

Auto-tagged on handoff

Conversation in your inboxBot answered 2 of 3 messages
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 makes every conversation that lands in it cheaper, faster, and better-informed — and it covers the channels Intercom doesn’t.

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, your bot can do ten Intercom actions during a conversation. They split into reads, writes, and tag-management. Each has its own toggle in the Configure Tools panel.

READ4 tools

The bot queries your Intercom workspace during a chat to ground answers in your real Help Center and contact data.

intercom_search_articles

Search your Help Center articles by query

intercom_lookup_contact

Find a Contact by email, phone, or external ID

intercom_search_conversations

Find a contact’s past conversations

intercom_lookup_ticket

Pull a Ticket by ID and read its state

WRITE4 tools

When the conversation produces something your team should see, the bot writes it into Intercom directly.

intercom_create_conversation

Open a new Conversation in your inbox

intercom_create_ticket

Open a Ticket with the transcript attached

intercom_create_contact

Create a Contact on lead.captured

intercom_reply_conversation

Post a reply into an existing Conversation

MANAGE2 tools

The bot tags conversations and lists existing tags so your team’s segmentation rules stay clean.

intercom_list_tags

Pull the workspace tag library

intercom_tag_conversation

Apply tags to route through your team rules

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. There’s no second copy of your knowledge to maintain. You update an article in Intercom; your NebulaHex bot starts answering with the new content the next time it’s searched.

03

How the bot writes to Intercom

Intercom integration follows the same two patterns as our other CRM-and-helpdesk connectors. They’re deliberately separate so you decide what fires automatically and what stays under the model’s judgment during a chat.

Pattern 1 · Event-driven write

When the bot captures a name and email mid-chat, lead.captured fires and an Intercom Contact is created or updated. Your team sees the conversation history in the same contact view they already use.

Pattern 2 · Tool-driven write

When the conversation needs a new Conversation, Ticket, reply, or tag in Intercom, the bot decides during the chat and calls the right tool. Tickets aren’t auto-created on every escalation — the model uses its judgment based on whether the conversation actually needs ticketing or whether a Conversation is the right shape.

The reply tool is unusual. Once a Conversation exists in Intercom, the bot can post replies into it from a chat in a different channel. A customer who started on WhatsApp can have the next exchange threaded back into the same Intercom Conversation your team is already watching.

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 Intercom remains the inbox where everything lands.

One bot, five channels, one Intercom inbox

Website Widget
WhatsApp
Instagram
Messenger
Telegram

NebulaHex bot

One knowledge base. One brain.

Escalations land in your existing inbox

Intercom Inbox

The home your team already uses

You don’t need a separate bot per channel, you don’t need to maintain separate knowledge bases, and you don’t need to teach your team a new inbox. The same Intercom Conversations they already watch start receiving handoffs from every channel your customers use.

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.

1

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.

2

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.

3

Configure the 10 actions

Toggle which Intercom actions the bot can call. Help Center search and contact lookup usually go on first. Ticket creation and conversation tagging next. Conversation reply only when you’re confident the bot should write into existing threads.

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. Anything the bot already created in your workspace — Contacts, Conversations, Tickets — stays in Intercom 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 Intercom with conversation already in your inbox and the transcript attached. Your monthly AI bill is flat — not a per-resolution meter.

Flat-fee AI, same Intercom inbox
🌍

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 and inbox handoff. One bot answers in 80+ languages on 5 channels; escalations come back to your Intercom inbox with channel-of-origin tagged.

Intercom inbox = command center; channels expand
🔓

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.

AI cost decoupled from support seats
🌱

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. When the bot escalates, the conversation goes into Intercom because that’s where the founder already lives.

AI layer for $0, clean upgrade path

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 plug into your Intercom inbox so the conversations that need humans land where humans already work.”

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. The 10 Intercom actions in NebulaHex are scoped narrowly enough that 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; editors can manage knowledge and tune bot behavior; 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 just give it a five-channel front door and a flat-fee AI brain. Sign up for free, build the bot, connect Intercom when you’re ready.