Designing Your Support Crew
The staffing recommendation, and the reasoning behind every number in it.
Team design turns discovery data into a specific recommendation: this many agents, on this schedule, covering these channels, with these optional additions. Every one of those decisions traces back to something you told us — none of it is a default template stretched to fit.
What we determine, and from what
| Decision | Driven primarily by |
|---|---|
| Agent count | Peak-hour workload and required coverage hours — not the daily average alone |
| Shift pattern | When your customers actually contact you, in their time zone |
| Dedicated vs blended role | Whether one agent can productively cover two channels without either suffering |
| Voice / chat / email allocation | Relative volume and the concurrency each channel supports |
| Supervisor requirement | Team size and how much daily oversight the campaign genuinely needs |
| QA requirement | Risk level of the work and whether you need formal scored review from day one |
| Coverage window | Your stated business hours plus any extended or overnight requirement |
Why the daily average is not enough
Two businesses with identical daily contact volume can need very different teams. One receives contacts evenly across an eight-hour day; the other gets half of it in a ninety-minute morning rush. Peak-hour load, not the daily average, is what determines whether customers wait. Our methodology is set out in full in the resource on how many agents your business needs, and team design applies it to your specific numbers rather than a generic formula.
Illustrative examples
These are worked examples to show the reasoning, not a menu of fixed packages. Your actual configuration follows from your actual numbers.
| Business | Stated volume | Illustrative starting configuration |
|---|---|---|
| Ecommerce store | 60 chats/day, 25 tickets/day | 2 cross-trained support agents, handling chat live and tickets in the gaps |
| Roofing company | 80 fresh leads/day | 2 dedicated appointment setters working speed-to-lead cadence |
| SaaS business | Inbound calls + tickets + live chat | 3-agent blended team, weighted toward the channel with the tightest response target |
What happens next
The design becomes the recommendation in your written proposal. If you disagree with the reasoning — you know something about your volume pattern we do not — say so before agent selection starts. This is the cheapest point in the process to change course.
FAQs on this stage
What is the minimum number of agents?
Two. That is the smallest team we take on, and it is deliberate. A single agent has no cover for illness, holidays or training time, which makes the arrangement fragile from day one. Two agents give you continuity and a realistic view of how the setup performs.
Can I increase the number of agents later?
Yes. Scaling up is the normal path — two agents to three, five, ten or more. New agents need training time on your material, so give us reasonable notice rather than expecting capacity the same week.