How do I sign up for Intercom and set up our first inbox, channels (email/chat), and roles/permissions?

Getting Intercom live for the first time is mostly about four things: creating your workspace, setting up an inbox your team can actually work from, connecting your main channels (email and chat), and locking down who can do what with roles and permissions. Do those well, and you get a single, AI-powered system instead of a patchwork of tools and logins.

Quick Answer: You sign up for Intercom by creating a workspace, then configure your first Helpdesk inbox, connect your email and Messenger channels, and assign roles/permissions so Fin AI Agent and your human team can work safely from the same shared view of every customer.

The Quick Overview

What It Is: An Intercom workspace with a Helpdesk inbox, integrated Messenger (chat) and email channels, and a permission model that controls who can configure, respond, and administer the system.
Who It Is For: Support, success, and operations teams that want one connected system for customer service—where Fin AI Agent and human agents share the same inbox, context, and workflows.
Core Problem Solved: Fragmented support across tools and channels—so you can respond faster, resolve more with AI, and keep governance tight as you scale.

How It Works

At a high level, you:

Create an Intercom workspace and complete the basic profile details.
Set up your first inbox in the Helpdesk and connect your core channels (email and chat via Messenger).
Assign roles and permissions so admins, agents, and specialists have exactly the access they need.

Under the hood, this is what turns Intercom into one connected system: channels (web, email, etc.) feed conversations into your inbox; Fin AI Agent and Copilot live directly in that workflow; and roles/permissions ensure only the right people can change critical settings like security, Workflows, and Data connectors.

1. Sign up and create your Intercom workspace

Go to https://intercom.com and start a free trial or sign-up flow.
Enter your work email and basic company details (company name, size, URL).
Confirm your email if prompted and log in to your new workspace.
During onboarding, you’ll be asked about:
- Your main use case (support, sales, or both)
- Approximate team size
- Preferred channels

These inputs help Intercom preconfigure parts of your Helpdesk, but you can adjust everything later.

Important: Decide who will be your initial admins. They’ll set security baselines (2FA, SAML SSO, identity verification) and own the first configuration of inboxes, channels, and Workflows.

2. Set up your first inbox in the Helpdesk

Your inbox is where agents and Fin AI Agent work together. Start with a simple, clear structure: one primary support inbox, then add specialized inboxes as you grow.

In Intercom, go to:
Settings > Workspaces (for workspace basics) and then
Settings > Helpdesk or Settings > Inbox (exact label may vary by UI version).
Create a new inbox, for example:
- Name: “Customer Support”
- Purpose: All inbound support from email, chat, and Messenger.
Configure:
- Team assignment: Add your first support team or individuals.
- Default rules: Choose how new conversations get routed (round-robin, based on workload, etc.).
- Views/filters: Create views like “New,” “Waiting on customer,” and “Urgent” so agents don’t live in one giant list.
Set expected reply times (SLAs) and any internal tags you plan to use for reporting (e.g., “Billing,” “Bug,” “Onboarding”).

Once this is in place, you have a home for every conversation your channels will start sending into Intercom.

3. Connect your chat channel with Intercom Messenger

Intercom Messenger is the chat experience customers see on your website or inside your product. It’s tightly integrated with the Inbox and Fin AI Agent.

There are two main surfaces:

Messenger inside your product (web app): For logged‑in users.
Messenger on your website: For logged‑out visitors on marketing pages.

3.1 Enable the Messenger

In your workspace, go to:
Settings > Channels > Messenger.
Turn on the Messenger for your workspace.
This turns on the Messenger APIs and ensures your workspace starts accepting traffic.

Note: We recommend securing Messenger with identity verification using JWTs for logged‑in users—especially if you’ll expose account-specific data or actions.

3.2 Install Messenger on your website or app

Intercom gives you multiple install paths (code snippet, WordPress, tag managers, etc.). The exact UI steps depend on the option you choose during onboarding.

Common web install pattern:

From the Messenger settings page, choose your install method. For example, for WordPress, you’ll see dedicated instructions.
Follow the instructions for your method:
- For direct web install, copy the JavaScript snippet from Intercom.
- Paste it into your site/app’s HTML template (usually before </body>).
Deploy your site/app.

Once installed, logged‑in users on your web app can get in touch via Messenger. With Intercom Inbox, you can respond to and manage users’ conversations from the team inbox. If your workspace doesn’t have full Inbox access, you’ll use the conversations list to read and reply.

Advanced pattern I use in production:
If you need Messenger to respect cookie consent, boot it disabled until consent is given:

window.intercomSettings = { app_id: 'YOUR_APP_ID', disabled: true };
Intercom('boot', window.intercomSettings);

// After consent:
Intercom('boot', { app_id: 'YOUR_APP_ID', disabled: false });

This ensures Messenger only loads once you have consent, but still ties conversations back to users via identity verification.

4. Connect your email channel

Email is usually the backbone of support volume. Intercom can either host an email address for you or connect to an existing one like support@yourcompany.com.

4.1 Add your support email

Go to:
Settings > Channels > Email.
Add your primary support email address (e.g., support@yourcompany.com).
Choose whether Intercom will:
- Provide a mailbox you forward to, or
- Directly connect via DNS and act as the primary handler.
Configure:
- The inbox that incoming emails should route to (e.g., your “Customer Support” inbox).
- Any basic routing rules (by subject, address, or email predicates like “Email To” vs “Email Cc” if you later use Workflows to decide when Fin responds).

Once connected, inbound emails appear as conversations in your inbox, alongside chat and Messenger conversations, with the same customer context and AI tools.

5. Create roles and assign permissions

This is where you control who can configure security, channels, and AI—and who should only work conversations. For a clean rollout, I recommend three starting profiles:

Workspace Admins: Own security, channels, and core configuration.
Support Agents: Work in the inbox, resolve conversations, use Copilot.
Contributors/Light users: Occasional access (e.g., engineers or product managers who help on tricky tickets).

5.1 Configure roles

Go to:
Settings > Security or Settings > Teammates & Permissions (label may vary) and then open Roles.
For each role, define capabilities such as:
- Can manage general and security settings: Turn on/off 2FA enforcement, SAML SSO, Google Sign‑In, and security-sensitive options.
- Can manage channels: Edit settings under Settings > Channels > Messenger / Email / WhatsApp / SMS, etc.
- Can manage Workflows and Fin AI Agent: Configure automation, Fin Tasks/Procedures, and Data connectors.
- Can manage Helpdesk settings: Create/modify inboxes, rules, SLAs, views.
- Can view and respond to conversations: Work in the inbox, use macros, insert Help Center articles.
Save each role configuration.

Important: Only give “Can manage general and security settings” to a small group who understand your identity and compliance requirements.

5.2 Invite teammates and assign roles

Go to:
Settings > Teammates (or Your teammates in some UIs).
Click Add teammate and enter their work email.
Assign the appropriate role:
- Admin role for system owners who’ll connect channels and define escalation paths.
- Support agent role for people working conversations day‑to‑day.
- Limited/Custom role for specialists (engineering, billing) who only need partial access.
Send the invite.

Once accepted, teammates can log in and work from the shared inbox with the correct level of control.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Helpdesk Inbox	Centralizes all conversations from email, Messenger, and other channels.	One connected system for support—no more channel silos or context-switching.
Messenger (Chat)	Adds in‑app and on‑site chat for logged‑in users and visitors.	Faster, conversational support that feeds directly into your inbox with full context.
Roles & Permissions	Controls who can configure settings, manage AI, and respond to customers.	Strong governance and security—so you can scale AI and human support without losing control.

Ideal Use Cases

Best for teams launching Intercom for the first time: Because it walks you from workspace creation through inbox, channels, and permissions—so you get value in days, not weeks.
Best for teams layering Fin onto an existing helpdesk: Because you can start by configuring Messenger and email with correct roles/permissions, then later deepen automation with Workflows, Data connectors, and Fin Tasks.

Limitations & Considerations

You need admin-level access to set up channels and roles: Only teammates with permissions like “Can manage general and security settings” and channel management can complete these steps. If you’re not seeing the right options, check your role.
Messenger and email setup differ by tech stack: The core flow is consistent, but the exact install steps vary (e.g., WordPress vs custom web app, domain provider for DNS). Plan a short implementation window with your web/dev team to avoid surprises.

Pricing & Plans

Pricing depends on your team size, feature set, and channel volume, but the pattern is:

You create a workspace and choose a plan based on your support needs (Helpdesk + Fin + channels).
You add teammates and AI capabilities (Fin AI Agent, Copilot, Workflows) as you scale.

Common plan fit:

Core/Starter-type plan: Best for smaller teams needing a unified inbox, Messenger, and email with basic roles and permissions.
Pro/Enterprise-type plan: Best for larger teams needing advanced governance (SAML SSO, workspace-level 2FA enforcement), more granular roles/permissions, and deeper automation with Fin, Workflows, Data connectors, and Fin Tasks/Procedures.

For current details, go to https://intercom.com/pricing from your region.

Frequently Asked Questions

How long does it take to get Intercom live with inbox, email, and chat?

Short Answer: Usually a few hours to a day, assuming you have access to your website and DNS/domain settings.

Details:
Creating the workspace and first inbox takes minutes. Enabling the Messenger and installing it on your site is also fast—Intercom’s Messenger install is designed to take “a few minutes” once you’ve chosen your method. Email can be connected just as quickly if you already control your DNS and support address. The longest part is often coordinating with whoever manages your website or domain.

Do I have to set up roles and permissions before inviting my team?

Short Answer: You can invite your team first, but you should define roles and permissions early to avoid over‑permissioning.

Details:
Intercom will let you invite teammates right after signup. However, if everyone defaults to a high‑privilege role, you risk accidental changes to security, channels, or Workflows. A better pattern is:

Create your workspace.
Define at least an Admin role and an Agent role with clear capabilities.
Invite teammates and assign the correct role from day one.

This keeps your environment governed as you introduce Fin AI Agent, set up Messenger, and connect more channels like WhatsApp, Instagram, or SMS.

Summary

To sign up for Intercom and set up your first inbox, channels, and permissions, you: create a workspace, configure a Helpdesk inbox, connect Messenger and email under Settings > Channels, and establish roles so only the right people can manage security, channels, and AI. Once those pieces are in place, you have a single, self‑improving system where Fin AI Agent and your human team share one inbox, one customer view, and clear operational guardrails.

Next Step

Get Started