What we do
Tools
Industries
Department
How we workLet's talk →
Home/Intercom/Intercom Ticketing System
Intercom tickets

The Intercom Ticketing System: Customer, Back-Office and Tracker Tickets in Practice

A customer asks for a refund in the Messenger. The agent can't issue it, finance can, and finance doesn't work in the inbox. That handoff is what Intercom's ticketing system is for. Tickets sit beside chat in the same inbox, come in three categories, move through states the customer can see, and carry SLAs. What a ticket can't do is reach into your billing or order system to find out whether the work actually got done.

Three kinds of Intercom ticket

Customer tickets are always shared with the customer, who can follow the state in the Messenger, email or the customer portal. A conversation can be converted into one, or the customer submits one through a form.

Back-office tickets hand work to an internal team, like a refund for finance or an escalation to engineering. They're internal by default, stay linked to the conversation, and cross-post notes and state changes back to it.

Tracker tickets gather one problem hitting many customers. Link the related conversations and customer tickets, then send one update to everyone affected.

Setting up a ticket type from scratch

  1. 1

    Create the ticket type

    Settings Inbox Tickets

    Name it for the work ("Refund request", "Bug report"), pick its category, and add the fields it should capture. The type's description stays internal.

    Watch for: conversations can only become customer tickets. A back-office or tracker ticket is created from the conversation and linked to it, not converted.

  2. 2

    Write the states your customers will read

    Each type needs at least one state in each of the four categories: Submitted, In progress, Waiting on customer and Resolved. Give each a customer-facing label that tells the customer what happens next.

    Watch for: internal state labels must be unique across the workspace. Customer-facing labels can repeat.

  3. 3

    Attach an SLA with a workflow

    Add an Apply SLA step to a workflow triggered when a ticket is created, branching by ticket type if each needs its own target. Customer tickets can use first reply, next reply, time to close and time to resolve. Back-office and tracker tickets only use the last two.

    Watch for: only one SLA is active on a conversation at a time. A later workflow that applies another one replaces the first.

  4. 4

    Decide when the clock pauses

    States in Waiting on customer can pause the SLA if you configure them to. SLA targets only count your office hours, so a short target can spill into the next working day.

Intercom ticket habits that hide unfinished work

Resolved in Intercom, not done in the real world

How you'll know: A refund ticket shows Resolved, and the customer writes back a week later because the money never arrived.

Fix: Resolving only changes the ticket. Tie the state to the system where the work happens, so the ticket moves when the refund, replacement or fix is recorded there.

Every issue as a customer ticket

How you'll know: Customers see internal back-and-forth labels like "Waiting on finance" in the Messenger.

Fix: Keep the customer ticket for what they should see, and open a linked back-office ticket for the internal work. Its state changes still cross-post to the conversation for the agent.

One bug, forty separate tickets

How you'll know: Agents answer the same outage one customer at a time.

Fix: Open a tracker ticket, link every related conversation to it, and send one update when the fix ships.

An SLA that quietly got replaced

How you'll know: A priority ticket shows the standard target instead of the faster one.

Fix: Two workflows applied SLAs and the second won. Put the SLA logic for each ticket type in one workflow with branches.

Tickets that know the order and close when the work does

01

Ticket fields filled from your order and account systems

When a ticket is created, its order number, plan, invoice standing and shipping status come from the system that holds them, so the agent and the back-office team start from the full record.

02

States that follow the work outside Intercom

We listen for ticket events from Intercom, pass the request to billing, fulfillment or your own admin tool, and move the ticket's state when that system confirms the work, where the Intercom API allows.

03

Trackers linked to the tools engineering really uses

Jira has an Intercom app already. If your team runs an in-house tracker, or one without an app, we link tracker tickets to it so status changes reach the customers waiting on the fix.

04

Which lookups slow down your Intercom tickets today?

The order screen, the billing dashboard, the admin panel: n-frames builds the connection that brings that data onto the ticket.

Intercom ticketing, answered

Does Intercom have a real ticketing system, or just chat?

It has both, in one inbox. Tickets come in customer, back-office and tracker categories, each type with its own fields and states, SLAs applied through workflows, and the option to turn a conversation into a customer ticket.

Can Intercom tickets have SLAs?

Yes. You apply them with an Apply SLA step in a workflow, for example one triggered when a ticket is created. Time to resolve is a ticket-only target, and back-office and tracker tickets use time to close and time to resolve, since reply targets need a customer in the thread.

Can I create custom ticket types in Intercom?

Yes, under Settings, Inbox, Tickets. Each type picks a category, the fields it captures and its own states, so a bug report and a refund request can follow different paths.

Does an Intercom ticket automatically know a customer's order or account status?

Not unless that data has been connected. Intercom can show attributes you sync in and call your systems through its data connectors, but your order or billing system needs an endpoint that answers. n-frames builds that side, so the ticket carries the order and account status when it opens.

What is the difference between a back-office ticket and a tracker ticket in Intercom?

A back-office ticket is one piece of internal work for one customer, such as a refund, linked to their conversation. A tracker ticket is one problem shared by many customers, with all their conversations and tickets linked so a single update reaches everyone.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.