Once you decide to build or improve your customer support operation, the question becomes how many people you actually need. Most companies want a dedicated team of trained specialists handling that work. The challenge is staffing it accurately: enough people to serve clients well, without paying for capacity you don’t use.

Answering that requires three numbers:

• Your customer base size and growth projections

• Your average monthly support tickets

• Your average tickets handled per representative per month

Then apply this formula:

Average Monthly Support Tickets / (Tickets per Representative per Month)

A few factors shape this number: your current and projected support volume, and how complex your product or service is – complexity affects both how long each ticket takes to resolve and how many tickets come in at once. Understanding your customers closely, and estimating how many tickets one person typically generates per month, is what lets you land on a number that fits your business.

New product launches usually raise support volume too, so it’s worth staffing up before a launch rather than reacting to a backlog after it.

The goal is balance: enough reps to serve clients well, without overstaffing and adding unnecessary cost. Tracking your rep-to-client ratio lets you adjust as you grow, which keeps satisfaction high without overspending.

Things to Consider While Calculating

Start by understanding the composition of your client base. You should be able to answer the following: 

What is the current size of your total client base?

At what rate does your client base grow?

Are there factors that could affect that growth rate – campaigns, new products, and so on?

These answers show you how fast your client base is growing and what your support team will need to keep up. Here are the calculations you’ll need to make.

Next, calculate the average number of support tickets your team receives each month.

For instance, you might look at data from the previous three years and find that for every 5 new clients your company gains, you get 1 new support ticket per month.

Use your own historical data to work out this ratio for your business – it’s a key input for sizing your support demand. Companies that use arborist estimating software often see fewer estimate-related inquiries, since customers get clear, automated pricing upfront.

How many reps you need depends on your company’s specific needs and growth trajectory. Start by reviewing historical ticket volume across different periods, then align staffing with those patterns – enough people for peak times, without idle capacity when demand drops.

Also consider whether the role calls for technical expertise (software installs, integrations) or general support skills (password resets, account questions).

Finally, factor in automation and self-service tools – some ticket types can be resolved without an agent, which reduces headcount needs without hurting service quality.

Figure Your Tickets Per Representative Per Month

Using past data, find the average number of tickets each representative resolves per month. This tells you how your support team currently performs and how large it needs to be.

If you already run a support operation, use your own numbers. If not, research typical tickets-per-representative figures for your industry and support channel.

A higher number looks efficient on paper, but pushing it too far can hurt customer satisfaction and loyalty.

With those numbers in hand, you can calculate your total staffing needs. Apply the same formula as before: divide your average monthly ticket volume by the average number of tickets one representative can resolve in a month.

That gives you the number of representatives needed to meet average demand. This figure varies by team and can usually improve with better efficiency and organization.

Keep in mind that any staffing decisions should also account for your client base growth and your customer satisfaction scores.

To figure out agents per customer, look at your average daily ticket volume – this shows what your client base is likely to generate, which tells you how many people you need to handle it.

Start by calculating your total daily ticket count, then divide it by your current headcount to see the workload per person. Account for seasonal spikes, and keep checking your typical daily volume so the ratio of agents to customers stays accurate as your business grows.

Once you know how to calculate the number of support representatives your company needs, you’re ready to build the operation around that number. Business management software like ArboStar gives arborists the data to size staffing accurately, avoid overhiring, and keep customer service running smoothly.

What’s the formula for calculating how many support reps I need?

Divide your average monthly support tickets by the average number of tickets one representative resolves per month. The result is your baseline staffing need.

What factors affect how many agents I should hire?

Your current and projected ticket volume, how complex your product or service is, whether tickets need technical expertise or general support skills, and how much of the workload automation or self-service tools can absorb.

How does client base growth affect staffing?

As your client base grows, monthly ticket volume typically grows with it. It’s worth staffing up ahead of growth drivers like new product launches, rather than after volume has already spiked.

Is there a benchmark for tickets per representative?

There’s no universal number. Use your own historical data if you have it, or research typical figures for your industry and support channel. Pushing the number too high to look efficient can hurt customer satisfaction.

How do seasonal peaks affect the calculation?

Ticket volume can spike during peak seasons, so it’s worth rechecking your typical daily ticket count regularly rather than relying on a single calculation done once a year.

Can automation reduce how many agents I need to hire?

Yes. Self-service tools and automated workflows can resolve some ticket types without an agent, which lowers headcount needs without reducing service quality.