Skip to content
Supportman
FRT & Metrics

Manage Your Intercom Support Backlog with Slack Visibility

Backlog visibility is a team lead problem. When the queue grows, team leads need to know before agents are overwhelmed. When it clears, they need to know so they can shift resources. The information lives in Intercom; the decisions happen in Slack.

Without Supportman

The manual approach

  1. 1Check the Intercom inbox view regularly for queue depth.
  2. 2Export unresolved ticket counts for reporting.
  3. 3Manually redistribute workload based on what you observe.

The problem: Queue depth check requires an Intercom login and the right view configured. Team leads who miss a check period miss the window for early intervention.

With Supportman

With Supportman

Open conversation counts and aging ticket data appear in Slack automatically, giving team leads a backlog pulse without an Intercom login.

  1. Enable backlog reporting in Supportman settings.
  2. Backlog snapshot posts to Slack daily or on demand.
  3. Team leads manage workload distribution from Slack context alone.
Common questions

Can I see which conversations have been waiting the longest?

The digest shows aging buckets (e.g. open for > 2 hours, > 8 hours, > 24 hours) rather than individual conversation lists. Drilling into specific conversations still requires opening Intercom.

Can I get a backlog snapshot on demand rather than on a schedule?

On-demand backlog reports via a Slack slash command are on the roadmap.

Five minutes to live, no IT ticket required.