Connect to IntercomAgent Concurrency
Agent Concurrency (also called Simultaneous Chat Count) measures how many active live-chat or messaging conversations an agent handles at the same time. It is unique to synchronous and near-synchronous channels. Setting the right concurrency is a balance between efficiency (higher concurrency = more customers served per agent-hour) and quality (lower concurrency = more focused responses, faster replies within a conversation). Concurrency above a threshold degrades quality significantly as agents lose context across simultaneous threads.
Average Concurrency = Total active simultaneous conversations ÷ Number of agents actively handling chats (sampled at regular intervals)
Platforms let you set a maximum concurrency cap per agent. Actual concurrency averages lower than the cap due to natural conversation flow. Measure average actual concurrency across a shift rather than just the configured cap — the cap tells you the ceiling, not the typical experience.
B2B SaaS, live chat channel
Calculate average concurrency
- 1Setting the same concurrency cap for all agents regardless of experience — new agents show quality degradation at 3 simultaneous; experienced agents can manage 4–5.
- 2Measuring maximum concurrency only — peaks don't represent the typical experience. Average concurrency over a shift is the more useful metric.
- 3Ignoring conversation complexity when setting caps — a simple FAQ chat can be handled at 5 concurrent; a technical troubleshooting session should be capped at 2.
- 4Not adjusting concurrency during peak periods — increasing concurrency during a queue surge has diminishing throughput returns while hurting quality faster.