Intercom Shared Inbox & Team Inbox Explained (2026)

This guide explains how the Intercom Inbox works as a shared and team inbox: how conversations arrive, the difference between team and personal inboxes, the four ways conversations get assigned, how views organize the queue, how teammates collaborate, and where SLAs, macros, and the Fin AI agent fit in — with a setup outline, best practices, and honest limits. For the wider platform picture, start with what Intercom is; for the support-team angle, see Intercom for customer support. Everything below is verified against Intercom's own help documentation as of June 2026.

Update (June 2026): Salesforce has agreed to acquire Fin (formerly Intercom) for ~$3.6 billion and plans to fold it into Salesforce's Agentforce — the deal was announced June 15, 2026 and is expected to close around Q4 of Salesforce's FY2027, worth weighing in any long-term Intercom/Fin decision.

A quick terminology note. "Shared inbox" and "team inbox" are how people describe Intercom, not separate products you switch on. Intercom's official name for the workspace is the Inbox. Within it, team inboxes are real, named objects you create, while "shared inbox" is just the general idea of a queue several people work together.

How conversations flow into the Inbox

The Inbox is the destination for every customer message, regardless of where it started. Intercom pulls conversations in from several sources:

• The Messenger — the chat widget on your website or inside your app, Intercom's signature channel and where most real-time conversations begin.
• Email — customers emailing your support address land as conversations, not a separate mailbox.
• Other channels — WhatsApp, SMS, phone, social, and Slack-connected conversations route into the same Inbox so agents work one queue instead of many tabs.
• Fin handoffs — when the Fin AI agent answers first and then escalates, the conversation arrives with its full history attached (more below).

The point of a shared inbox is that all of this converges: an agent does not need to know whether a question came in by chat or email — it is a conversation in a queue, with the customer's record and context attached.

Team inboxes vs. personal inboxes

Intercom gives the Inbox two scopes, and understanding the split is the key to using it well.

Personal (individual) assignment is your own work. When a conversation is assigned to you, it appears in your "Mine" view. It is still visible to the wider team — Intercom is a shared workspace, not a set of private mailboxes — but you own the reply.

Team inboxes are the shared queues. A team inbox belongs to a group rather than a person: you assign a conversation to the "Billing" team or "VIP support" team instead of to one teammate. Every team you create gets its own inbox, so members can manage everything assigned to that group, and conversations do not sit unowned when the one person who handles them is out.

In practice most teams run a hierarchy: conversations land in a team inbox first (by channel, topic, region, or customer tier), then get assigned to an individual — automatically or when an agent claims one. This keeps unowned work visible at the team level while giving each conversation a clear human owner.

How conversations get assigned

Assignment is where a shared inbox either runs smoothly or descends into chaos. Intercom supports four approaches, and you can mix them across different team inboxes.

A few details that matter in real operations:

• Round robin assigns to active teammates in sequence and skips anyone set to "Away," picking back up where it left off. Note that, per Intercom's docs, round robin does not respect a teammate's assignment limit — it keeps distributing in order regardless of how loaded someone is. If even load matters more than strict rotation, Balanced is the safer pick.
• Assignment rules (run as assignment Workflows) are how you route by meaning: send billing keywords to the finance team, Spanish speakers to a Spanish inbox, or high-MRR accounts to a VIP team. Criteria can include user attributes, the page a customer is on, keywords in the first message, or custom data like account value.
• Assignment limits and workload management cap how many conversations a teammate can hold at once, so a single agent is not handed fifty open chats. This is the guardrail that makes auto-assignment safe to leave on.

Views and folders: organizing the queue

A busy shared inbox needs more than one big list. Intercom's views let you define a set of filters — channel, priority, tag, team, SLA status, and more — and see every matching conversation in one place. You might keep a view for "urgent + unassigned," another for your direct reports, and another for a specific product area.

The crucial thing to understand: views do not reassign anything. A view is a lens, not a queue change. A conversation that shows up in your "VIP" view is still assigned to whichever team or teammate owns it — the view just surfaces it. This is what lets a manager watch urgent work across the whole operation without disturbing who is actually responsible for each thread.

Collaboration: notes, mentions, and looping people in

The reason teams move off a forwarded-email setup is collaboration, and this is where a shared inbox earns its keep.

• Internal notes let teammates discuss a conversation privately, on the same thread, without the customer seeing.
• @mentions notify a specific teammate — or an entire team — and pull them to the conversation. Because teams are real objects, you can @-mention a whole group at once.
• Looping in teammates or teams brings additional people into a conversation for a specialist or back-office hand-off, while keeping everything on one record.

The unifying idea is one customer record. Whoever touches the conversation — first agent, escalation owner, or looped-in specialist — sees the same history, so context is never lost in a hand-off.

SLAs and macros

Two more Inbox features turn a shared queue into a managed support operation.

SLAs let you set targets (for example, first-response and resolution times), prioritize urgent or VIP conversations, and track whether the team is hitting its commitments. SLA status can drive views and Workflows, so breaching conversations bubble to the top automatically.

Macros (formerly called "saved replies") are the productivity multiplier. A macro can insert a pre-written response and bundle a set of actions — tag, assign, snooze, close, change priority, set a data attribute, even trigger an external API call — all applied in one click. You can scope a macro to the whole workspace, a specific team, or just yourself. Intercom markets macros as improving Inbox efficiency by "up to 43%"; treat that as a vendor figure rather than a guarantee, but the underlying win — turning a repetitive multi-step reply into one keystroke — is real.

Where Fin AI fits, ahead of the human inbox

Modern Intercom is built so the Fin AI agent answers first and the human Inbox handles what is left. Fin sits in front of the shared inbox across channels (chat, email, and more), attempts to resolve the question autonomously, and only then routes a human.

Fin is designed to escalate and hand off when that is the right call — when a customer asks for a human, when it detects strong frustration, when the conversation is stuck in a loop, or when Fin is not confident. Because Fin and your team work from the same customer record, an escalated conversation arrives in the relevant team inbox with its full history, so the agent picks up mid-context rather than starting cold. Handover rules decide which team unresolved conversations land in.

The practical effect: the volume your humans see is whatever Fin could not (or should not) close on its own. Your team inboxes increasingly hold the harder, higher-context conversations — an argument for routing rules and SLAs that prioritize them.

Setting up an Intercom shared inbox: an outline

The exact clicks shift as Intercom updates its UI, but the shape of the setup is stable:

1. Create your team inboxes. Go to Settings > Inbox > Team inboxes, choose New team inbox, and name it after how you actually divide work — by channel, topic, region, or customer tier.
2. Add teammates to each team inbox so the right people see the right queue.
3. Choose an assignment method per inbox — Manual, Round Robin, or Balanced — based on whether you want agents to claim work or have it distributed.
4. Write assignment rules / Workflows to route incoming conversations to the correct team by attribute, keyword, language, or account value.
5. Set assignment limits / workload management so no one is overloaded.
6. Build views for the slices you monitor (urgent, unassigned, breaching SLA, your team).
7. Create macros for your most common replies and action bundles.
8. Configure SLAs and tie them to priority and views.
9. Decide Fin's role and handover rules — what it resolves, when it escalates, and which team gets unresolved conversations.

Best practices

• Route into team inboxes first, then to people. Topic/tier-based team inboxes keep work visible and prevent conversations from going dark when one person is out.
• Prefer Balanced over Round Robin if fairness matters. Round robin ignores assignment limits; Balanced actively levels load.
• Use views, not new inboxes, for monitoring. A "breaching SLA" view beats spinning up another queue you have to staff.
• Invest in macros early. A handful of good action-bundling macros pays back fast on repetitive volume.
• Keep Fin's knowledge current. Everything Fin resolves before the human inbox depends on the quality of your help content.
• Review assignment regularly. As volume and team shape change, rules that were right six months ago quietly start misrouting.

Honest limits

No tool is perfect, and a shared inbox has real trade-offs worth naming:

• Round robin does not respect assignment limits. It is genuinely sequential, so a less-active agent can still get piled on; reach for Balanced if that bites.
• Views can multiply into clutter. It is easy to create a dozen views nobody maintains; prune them.
• Assignment rules grow complex. Layered Workflows can become hard to debug — when a conversation lands in the wrong place, the cause is often a rule interaction, not a single setting.
• Cost scales with how you use it. The Inbox/help desk is part of every Intercom seat, and Fin is billed per resolution — so heavier AI deflection has a usage cost. We cover the model in what Intercom is; confirm current numbers on Intercom's pricing page before budgeting.
• It is opinionated. Intercom's Inbox is designed around its own conversational, AI-first model. If your operation is heavily structured ticketing with deep custom fields and forms, parts of it can feel light.

Where an AI agent layer fits

Plenty of teams already run a help desk they like and just want stronger autonomous resolution sitting in front of the human inbox — the same pattern Fin embodies inside Intercom. That is the category Macha works in: an AI agent layer that runs on top of an existing help desk, reads the customer's real question, draws on your connected knowledge and conversation history, resolves in-thread, and escalates to a human with full context when it is not confident.

Two honest caveats, because this is a guide and not an ad: Macha only connects to Zendesk and Freshdesk — it does not integrate with Intercom, so if Intercom is your platform, Fin is your built-in version of this idea, not Macha. And like any AI agent, Macha is only as good as the knowledge you connect it to. If you do run Zendesk or Freshdesk and most of your inbox is repetitive questions your help center could answer, you can try it free — 7-day free trial, no credit card required.

Frequently asked questions

Does Intercom have a shared inbox? Yes. Intercom's agent workspace is called the Inbox, and it works as a shared inbox: multiple teammates see, route, and resolve customer conversations from one place. You organize it with team inboxes (shared queues for a group) and personal assignment for individual ownership.

What is the difference between a team inbox and a personal inbox in Intercom? A team inbox belongs to a group — you assign a conversation to a whole team, and every member can see and manage it. Personal assignment ("Mine") is work assigned to you specifically. Most teams route into a team inbox first, then assign to an individual from there.

How does Intercom assign conversations? Four ways: Manual (teammates claim work), Round Robin (even sequential distribution to active teammates), Balanced (to whoever has the fewest active conversations), and Assignment Rules/Workflows (auto-route by attribute, keyword, language, or account value). Assignment limits and workload management cap how much any one person holds.

What are Intercom views and do they reassign conversations? Views are saved filters that surface matching conversations in one place. They do not reassign — a conversation shown in a view still belongs to whatever team or teammate it is assigned to. Views are for monitoring, not routing.

Where does Fin AI fit in the Intercom inbox? Fin answers first, ahead of the human Inbox, across channels. It resolves what it can autonomously and escalates to a human team — with full conversation history on the same customer record — when the customer asks for a person, shows frustration, gets stuck, or Fin is not confident. Handover rules decide which team gets unresolved conversations.

What are macros in the Intercom inbox? Macros (formerly "saved replies") insert a pre-written response and can bundle actions — tag, assign, snooze, close, set priority, change a data attribute, or call an external API — applied in one click. They can be scoped to the whole workspace, a team, or just you.

The bottom line

Intercom's Inbox is a full-featured shared inbox: conversations from the Messenger, email, and every connected channel converge into one workspace, team inboxes keep group work visible while personal assignment gives each thread an owner, and four assignment methods plus rules, limits, views, macros, and SLAs let you run it like a real support operation rather than a chaotic group mailbox. The modern twist is that Fin AI answers ahead of the human inbox, so your team increasingly handles the harder, escalated conversations — with full context preserved. Set up team inboxes by how you actually divide work, prefer Balanced assignment when fairness matters, lean on views and macros, and keep your Fin knowledge current, and the Intercom Inbox becomes a genuinely well-managed shared queue.

Verified against Intercom's official help documentation and product pages, June 2026. Intercom revises Inbox features and terminology periodically — confirm current behavior in your own workspace before relying on specifics.