Connect to IntercomMeasure Support Team Efficiency in Intercom
Efficiency metrics are the bridge between headcount and capacity planning. Without them, hiring decisions are made on intuition — and scale decisions miss their window. With them, you can forecast staffing needs, justify headcount requests, and identify automation opportunities.
The manual metrics approach
- 1Export agent and team metrics from Intercom Reports quarterly.
- 2Calculate derived metrics (conversations per agent per day, etc.).
- 3Use in capacity planning discussions and headcount requests.
The problem: Quarterly is fine for headcount planning. For day-to-day operational decisions, monthly or weekly is necessary. Manual extraction at that frequency is not sustainable.
With Supportman
Every Friday afternoon, efficiency metrics arrive in Slack — conversations replied to, median first reply, median time to close, and a 7-day emoji ratings summary — for the team channel and each active agent's personal DM.
- Connect Supportman to Intercom and Slack (OAuth, two clicks).
- Friday team digest posts to your channel; per-agent DMs go to each active rep.
- Capacity discussions start with real numbers from last Friday, not memory.
Efficiency metrics need a weekly pulse — Supportman delivers conversations replied to, first reply, time to close, and emoji CSAT every Friday in Slack.
Can I use Supportman data to justify a headcount request?
The Friday digest provides directional evidence — rising volume, slower first reply, longer time to close. For a formal headcount request, export underlying data from Intercom Reports and apply your own capacity model.
What is a good conversations-per-agent benchmark for B2B SaaS support?
Ranges vary enormously: 20–40 conversations per agent per day for complex technical support; 60–120 per agent per day for transactional support. Your benchmark should be your own historical baseline.