We increased the maximum simultaneous chat interactions from 3 to 5, and agent burnout complaints skyrocketed.
Agents say they can’t keep up with 5 concurrent chats. Response times increased from 30 seconds to 2 minutes per message. CSAT dropped 0.5 points. Should we revert?
From a speech analytics perspective, agents handling 5 concurrent chats produce lower-quality responses.
Our topic detection flagged a 30% increase in ‘copy-paste’ responses when agents handled 5 chats vs 3. The agents were reusing the same canned response across multiple chats without personalizing. Quality suffers at high concurrency.
The utilization setting should vary by agent experience level.
# Set per-agent utilization based on tenure
for agent in agents:
if agent.tenure_months < 6:
max_chats = 2 # New agents
elif agent.tenure_months < 24:
max_chats = 3 # Experienced
else:
max_chats = 4 # Senior
body = {'utilization': {'chat': {'maximumCapacity': max_chats}}}
api.put_routing_user_utilization(agent.id, body)
Under European Working Time regulations, excessive multitasking may constitute an unsafe working condition.
If agents report burnout and stress from handling too many concurrent interactions, the employer has a duty-of-care obligation to reduce the workload. Document the utilization change and the resulting reduction in stress complaints for your HR records.
Yes, revert immediately. The data supports it.
Our A/B test across 500 agents showed:
| Max Chats | Response Time | CSAT | Agent Satisfaction |
|---|---|---|---|
| 3 | 28s | 4.3 | 7.8/10 |
| 4 | 45s | 4.0 | 6.2/10 |
| 5 | 118s | 3.5 | 4.1/10 |
The optimal setting depends on chat complexity, but 3 is the safe default for technical support.