Skip to content
Supportman
FRT & Metrics

Get Alerts for Intercom Volume Spikes in Slack

A volume spike in your support inbox is the canary in the coalmine for product problems. Customers experience an issue, reach out for help, and your support team absorbs the load while the product team has no idea there is a problem.

Without Supportman

The current reality for most teams

  1. 1Agents notice the queue growing.
  2. 2Team lead checks Intercom and confirms the spike.
  3. 3Team lead messages the product team to flag a possible incident.
  4. 4Product team investigates, discovers the issue, and starts a response.

The problem: The time between incident start and product team awareness is typically 30–90 minutes — all absorbed by a support team that did not sign up to be an incident detection system.

With Supportman

With Supportman

Supportman monitors volume trends and posts to Slack when inbound volume deviates significantly from the rolling average.

  1. Configure volume spike sensitivity in Supportman settings.
  2. Spike alert posts to #support and optionally #incidents within minutes.
  3. Product and engineering teams are in the loop before the support queue hits critical mass.
Common questions

How does Supportman define a volume spike?

By default, a spike is defined as inbound volume exceeding 2x the rolling 7-day average for the same time window. The sensitivity threshold is configurable.

Can volume spike alerts ping a specific person or channel?

Yes — you configure the target Slack channel, and within that channel you can set up Slack notification keywords to trigger alerts for specific users.

Five minutes to live, no IT ticket required.