IntercomDeclan IvoryExplainer
2026 customer service planning series: Vol. 05
Summary
AI-first customer service makes capacity planning less predictable because automation changes volume, work mix, human responsibilities, and performance over time. The proposed planning model puts automation rate—AI Agent involvement rate multiplied by AI Agent resolution rate—alongside inbound volume, human output for complex remaining work, and occupancy. It recommends ambitious automation assumptions only when backed by named ownership, content and systems investment, work-type targets, and staged improvement, while modeling lower cases closed per person and more time for off-queue work. Finance should treat the plan as a revisable set of assumptions, review it at least quarterly, and avoid cutting headcount before automation is proven. Surplus capacity should be redirected to AI improvement, product feedback, new channels, or proactive customer experience work rather than automatically reduced.
Context
AI changes the fundamentals of customer service capacity planning: it alters the work mix, may increase demand, shifts human time toward complex and system-level work, and makes automation performance dynamic. Using pre-AI assumptions about productivity, work mix, and the relationship between volume and headcount can underestimate staffing needs and create understaffing risks.
Approach / What changed
Center the plan on automation rate, calculated from AI Agent involvement rate and AI Agent resolution rate, alongside inbound volume, human output for remaining complex work, and occupancy. Set bold but investment-backed automation targets, model lower human case output, allocate explicit time for off-queue improvement work, and review assumptions with finance at least quarterly.
Takeaways
Automation rate combines AI Agent involvement rate and AI Agent resolution rate, showing the share of total volume AI resolves, the work left for humans, and the headcount assumptions the plan can support.
As humans handle fewer but harder conversations, plans should use lower cases-closed-per-person assumptions and count AI improvement, content work, and other system-level responsibilities as productive work.
Capacity plans should protect time for reviewing AI conversations, improving triage and handovers, contributing to content and procedures, and feeding insights to product and engineering.
Source and freshness
- Source
- intercom.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.