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

Getting Intercom live with a clean first inbox, connected channels, and sane permissions doesn’t need a long implementation. If you treat it like a production system from day one—clear routing rules, scoped roles, and secure Messenger—you’ll avoid painful rework later when volume grows.

Quick Answer: Sign up for Intercom, create your primary support inbox, connect email and Messenger as channels, then lock in roles and permissions so agents, admins, and owners each have the right level of control.

The Quick Overview

What It Is: A step‑by‑step setup of your first Intercom Helpdesk environment—sign‑up, inbox creation, email and chat channel configuration, and role/permission assignment.
Who It Is For: Support leaders, admins, and ops owners rolling out Intercom for the first time or migrating from another helpdesk.
Core Problem Solved: It’s easy to end up with a messy inbox, unowned channels, and over‑permissioned users—this guide shows how to launch Intercom as a single, connected system that’s secure and scalable from day one.

How It Works

You’ll move through four key phases in order:

Create and secure your Intercom workspace.
Set up your first inbox and routing rules.
Connect your core channels (email and Messenger chat).
Assign roles and permissions so the right people control settings, data, and workflows.

Think of this as building the backbone of your support system: once these pieces are in place, you can safely layer on Fin AI Agent, Workflows, Copilot, and more without revisiting fundamentals.

Workspace sign‑up & baseline security:
Sign up for Intercom, verify your account, and enforce basic security (SAML SSO/Google Sign‑In/2FA) so you’re not rebuilding access control when the team grows.
Inbox & routing foundations:
Create your first inbox (usually “Support”), decide what conversations it should own, and configure assignment and SLAs. This gives you one shared view of every customer you support via email, Messenger, and other channels.
Channel configuration (email + chat):
Connect your support email address and install the Intercom Messenger on your website/app. This is where conversations actually enter the system, so you want them wired into the right inbox from the start.
Roles, permissions & governance:
Assign workspace roles (Owner, Admin, Support Agent, Light user) and fine‑tune permissions—especially who can manage security, channels, Workflows, and billing—so changes are deliberate, not accidental.

Phase 1: Sign up for Intercom and secure your workspace

1. Create your Intercom account

Go to https://intercom.com and click Get started or Free trial.
Sign up with your work email (or Google Sign‑In if your org prefers it).
Enter the basic details Intercom asks for:
- Company name and website
- Role and team size
- Primary use case (usually “Customer support” / “Helpdesk”)

Your workspace is created in a few seconds—this is the environment where you’ll configure inboxes, channels, AI, and reporting.

2. Add your first teammates

Add colleagues who will help configure and run support:

Go to Settings (gear icon) > General > Teammates.
Click Add teammate and invite them via email.
For now, set them as:
- Admin if they’ll configure inboxes, channels, Workflows, and Fin.
- Support Agent if they’ll primarily answer conversations.

You’ll refine roles and permissions in Phase 4; this gives them access to start collaborating.

3. Set baseline security controls

Launches go smoother when access control is in place from the start, especially for larger teams.

Go to Settings > Security (your exact path may differ slightly depending on plan).
From here, an Owner/Admin with Can manage general and security settings should:
- Enable 2‑factor authentication (2FA), ideally enforced at the workspace level.
- Configure Google Sign‑In or SAML SSO if your identity provider supports it.
- Review session timeouts and allowed authentication methods.

Important: Lock down “general & security settings” to a small set of admins. This keeps channel changes, domain verification, and identity verification (JWT) keys in the right hands.

Phase 2: Create your first inbox and routing rules

Your inbox is where conversations from all channels land. Done right, you get one connected system where email, Messenger, and AI handoffs all converge with full customer context.

1. Create (or confirm) your primary inbox

Go to Settings > Workspaces / Inbox (name can vary by plan—look for “Inboxes”).
Intercom usually creates a default inbox. You can:
- Rename it to Support or Customer Support, or
- Create a new inbox (e.g., Support – Global).

Define what this inbox owns:

General support across all regions
All email+Messenger conversations to start
Handoffs from Fin AI Agent

2. Configure assignment and SLA behavior

Inside your primary inbox:

Set default assignment rules:
- Auto‑assign to a round‑robin of support agents, or
- Assign to an “Unassigned” queue that a team lead manages.
Configure office hours if you want expected reply times to adjust by schedule.
Decide whether to use Workflows for first‑line routing (recommended once you’re live).

This is where you ensure customers don’t land in “no man’s land.” Every conversation should have a clear owner and a clear path if not answered quickly.

3. Connect inbox to channels conceptually

You’ll wire channels in Phase 3, but align the model now:

Email: All emails sent to support@yourcompany.com should route into the Support inbox.
Messenger (chat): All website/app Messenger conversations should land in the Support inbox (you can segment later by page, tag, or topic).
AI handoffs: Fin AI Agent should assign or mention the right inbox/team whenever it escalates.

Phase 3: Connect your channels (email + chat)

With your inbox ready, you can turn on the actual entry points for customers: email and Messenger.

A. Connect your support email channel

You want a single support address (e.g., support@yourcompany.com) that customers already know, and you want replies and history to live in Intercom.

Go to Settings > Channels > Email.
Choose how to connect:
- Forwarding from an existing support address (e.g., from Google Workspace or Microsoft 365), or
- Using an Intercom‑provided email address and aliasing it.
Follow the on‑screen steps:
- Verify your domain (DNS changes like SPF/DKIM are usually required so emails send reliably).
- Set From name and Reply‑to address so customers see a branded sender.
Route email into your primary inbox:
- Under your email configuration, set Destination inbox to Support.

Note: Keep this simple at first—one support address, one inbox. You can introduce multiple addresses and inboxes later (e.g., billing, sales, region‑specific).

B. Install and enable the Intercom Messenger (web/app chat)

The Intercom Messenger is your real‑time chat channel on your website or product. It’s fully integrated with Inbox, so your team sees the same conversation alongside email, AI context, and customer history.

According to Intercom’s install docs, a full and secure Messenger setup has two steps:

Initial Messenger install for users on web.
(Then) secure it with JWTs for identity verification.

1. Turn on the Messenger for your workspace

Go to Settings > Channels > Messenger.
Make sure the Messenger is enabled—this turns on Messenger APIs for your workspace and lets it start accepting traffic.

If this isn’t enabled, no user or visitor traffic will ever hit your Inbox from chat.

2. Install Messenger on your website or app

From Settings > Channels > Messenger > Install, choose your install method:

JavaScript snippet (most web apps/sites)
WordPress plugin
Other platform‑specific methods

Example (web snippet):

Copy the JavaScript code snippet Intercom provides.
Add it to your website/app template just before the closing </body> tag.
Deploy your changes.

For WordPress, Intercom’s panel will show you specific plugin steps—install the plugin, paste your app ID, and activate.

Note: It typically takes only a few minutes to install Messenger on your site. Once installed, you can welcome, onboard, and support customers on your website or in‑product.

3. Secure Messenger with identity verification (JWT)

If you have logged‑in users in your product, secure Messenger so conversations are tied to real user identities and can’t be spoofed:

In your backend, generate JWTs that Intercom can verify for each logged‑in user.
Include those tokens in your Intercom('boot', { ... }) call.

For privacy/cookie consent use cases, you can initially boot Messenger with disabled: true, and then re‑enable after consent:

window.intercomSettings = {
  app_id: 'your_app_id',
  disabled: true,
  // other settings and identity verification fields here
};

// After user accepts cookies/consent:
Intercom('boot', {
  app_id: 'your_app_id',
  disabled: false,
});

This gives you tight control over when Messenger appears and ensures only authenticated users see their own conversation history.

4. Confirm conversations land in the right inbox

Once Messenger is live:

Open your website/app in a browser.
Start a test conversation as a visitor or logged‑in user.
In Intercom, open Inbox and confirm:
- The new conversation appears in your Support inbox.
- Assignment rules work as expected (auto‑assign/queue).

If you don’t have access to Inbox, you’ll see conversations in the conversations list instead, but the routing principle is the same.

Phase 4: Set up roles and permissions

Intercom works best when roles and permissions mirror how your team actually operates—owners govern, admins configure, agents resolve, and specialists contribute knowledge.

1. Understand core roles

Typical roles you’ll see or configure:

Owner: Full control of billing, security, and workspace‑level settings. Usually 1–2 people (e.g., Head of Support, VP CX).
Admin: Can manage inboxes, channels, Workflows, Fin, and day‑to‑day configuration.
Support Agent (or Team Member): Works in Inbox, responds to conversations, uses Copilot, inserts Help Center articles.
Light / Limited User: May access some reporting or view conversations, but can’t change core settings.

2. Assign roles during rollout

Go to Settings > General > Teammates.
For each teammate:
- Set role (Owner, Admin, Support Agent, etc.).
- Place them into the Support team or other relevant teams so routing rules can target them.

Operationally sound setup:

1–2 Owners (Support leader + maybe an exec sponsor).
A small group of Admins (support ops, system admin).
All frontline staff as Support Agents.
Occasional Light users for cross‑functional visibility (e.g., product, sales).

3. Control sensitive permissions

Within roles or advanced permissions, pay special attention to capabilities like:

Can manage general and security settings: Limit to Owners/Admins you trust with security, domain verification, JWT keys.
Can manage channels (Email, Messenger, WhatsApp, etc.): Keep this tight to prevent accidental re‑routing or downtime.
Can manage Workflows, Fin AI Agent, and Fin Tasks/Procedures: These control how automation behaves—treat them like production code.
Can view/export customer data and reports: Align with your data governance and privacy requirements.

Note: As you add more channels (WhatsApp, Instagram, SMS) and more automation, revisit permissions so every new capability has a clear owner.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Unified Inbox	Centralizes conversations from email, Messenger, and other channels.	One connected system—no more switching tools or losing context.
Messenger + Helpdesk	Embeds Intercom Messenger in your site/app, linked to the Support inbox.	Real‑time support with a shared view of every customer interaction.
Roles & Permissions	Defines who can configure, respond, and govern Intercom.	Strong governance—so changes are safe, auditable, and intentional.

Ideal Use Cases

Best for new Intercom customers: Because it walks you from sign‑up to a fully working Support inbox, with email and chat wired correctly from day one.
Best for teams migrating from another helpdesk: Because it shows how to keep a single support address and route everything into Intercom without breaking existing workflows.

Limitations & Considerations

DNS and IT dependencies: Email setup and domain verification may require help from your IT team or domain admin—plan for that lead time.
Security ownership: Identity verification (JWT), SAML, and channel security should be owned by someone with access to your codebase and identity provider; don’t delegate this to someone without technical access.

Pricing & Plans

Intercom offers several plans that bundle the Helpdesk, Fin AI Agent, and channels differently. The exact pricing depends on your volume and needs, but structurally:

All plans give you access to the core Inbox, Messenger, and Help Center, with varying limits on teammates, contacts, and channels.
Higher‑tier plans add advanced capabilities: Workflows, Fin AI Agent, Data connectors, Fin Tasks/Procedures, and richer governance.

When choosing a plan for this setup:

Starter / Core Helpdesk: Best for small teams needing one primary inbox and standard email + chat support.
Growth / Advanced Suite: Best for teams that want to roll out Fin, use multiple channels (WhatsApp, Instagram, SMS), and enforce governance (SSO, workspace‑level security controls).

For current plan details and pricing, check https://intercom.com or speak with Intercom sales.

Frequently Asked Questions

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

Short Answer: In most cases, you can go from sign‑up to a working inbox with email and Messenger in under a day—often within an hour.

Details:
The time‑consuming parts are usually outside Intercom:

Email: DNS updates (SPF/DKIM/DMARC) can take time to propagate, depending on your domain host.
Messenger: Installation is quick—a few minutes to add the script or plugin and deploy.
Roles/permissions: If you’ve already decided who should be Owner/Admin/Agent, assigning these takes minutes.

If you treat security and identity verification (JWT, SSO) as part of day‑one setup, you may need engineering time—but even then, most teams can complete a secure rollout in days, not weeks.

Do we have to switch off our existing helpdesk immediately?

Short Answer: No. You can run Intercom alongside your existing helpdesk while you validate the new inbox, channels, and workflows.

Details:
Many teams layer Intercom in gradually:

Start by installing Messenger and routing those conversations to the Intercom Support inbox.
Forward your existing support@ email into Intercom while keeping your old tool active during a transition window.
Once you’re confident inbox routing, roles, and channels are stable, you can cut over fully and decommission the old system.

This lets you test Intercom’s Helpdesk, Fin AI Agent, and routing in production conditions without risking lost conversations.

Summary

A clean Intercom rollout follows a predictable sequence: sign up and secure your workspace, create a primary Support inbox, connect email and Messenger into that inbox, then lock in roles and permissions so the system scales safely. When you treat this as the foundation—a single, connected Helpdesk where AI and humans share the same view of every customer—you avoid the usual early‑stage chaos of scattered channels, unowned conversations, and over‑permissioned users.

Once these fundamentals are in place, you’re ready to layer on Fin AI Agent, Copilot, Workflows, and more advanced channels—knowing every interaction flows through a reliable, governed system.

Next Step

Get Started