One of the easiest things to underestimate in a growing business is customer support.

From the outside, it can look fairly straightforward. Customers have questions, the team answers them, and problems get resolved. When the volume increases, the obvious response is usually to add more people.

I've learned that the hiring is often the easy part.

The harder part is making sure the operation around those people is capable of supporting them. If you take a small support team that is already struggling with volume and simply add more agents, you haven't necessarily solved the problem. You've increased the number of people operating inside the same system.

I experienced this directly at Feline Skinscience, where I scaled the customer support team from one person to eight as the business grew. The volume and complexity of customer interactions had changed significantly from the point where the original support structure had been created, so the operation needed to change with it.

That meant looking at much more than headcount.

The first problem is usually capacity

When support volume starts increasing, the pressure tends to show up fairly quickly.

Response times start getting longer. Agents have more conversations open at once. More complicated cases sit unresolved because there isn't enough time to investigate them properly. Managers become involved in more escalations. Eventually, customers feel the impact.

At that point, hiring makes sense.

But hiring eight people doesn't magically create an eight-person operation.

Someone has to decide how work is distributed. New people need training. There needs to be somewhere for them to find the information they need. Escalations need to go somewhere. Someone needs to understand what good performance looks like and how to identify when the operation is struggling.

The bigger the team becomes, the more important those things become.

With one person, a lot of information can simply exist in their head. With eight people, that becomes a liability. You need to start making the knowledge accessible to everyone rather than relying on the person who happens to know the answer.

That was one of the biggest shifts in the support operation I was working with.

Scaling the team meant scaling the system around it

As the team grew, we needed to establish clearer ways of handling the work.

That included SOPs and workflows, but also escalation processes and clearer expectations around performance. Customer support wasn't just about answering tickets anymore. The team was dealing with returns, refunds, cancellations, disputes, chargebacks and more complicated customer situations that required judgement.

The more varied the work became, the less useful a simple "answer the customer" approach was.

Agents needed to know what they could resolve themselves, when they needed to escalate something and where to find the information required to make a decision. Without that clarity, you end up with a team that is technically larger but still dependent on a small number of people to keep things moving.

That's one of the reasons I don't think SOPs should be treated as the entire solution.

Documentation is useful, but it has to sit within an operating system that people actually understand. If an agent has to search through ten documents to work out what to do with a particular customer, the documentation hasn't really solved the problem.

The system needs to make the right action easier to find.

Performance data changes the conversation

Another important part of scaling the operation was being able to see what was actually happening.

Customer support can be difficult to manage when the only measure of performance is how busy everyone feels.

Someone might say the team is overwhelmed. Another person might say response times are fine. A manager might feel that a particular type of ticket is taking too long. Without data, everyone can have a different version of reality.

Using Freshdesk reporting gave us a much clearer view of the operation.

Metrics such as first-contact resolution, ticket volumes and response performance helped show where the team was doing well and where there were opportunities to improve. That made conversations about performance much more useful because we weren't relying entirely on impressions.

Data doesn't replace judgement, though.

A metric can tell you that something is happening. It doesn't necessarily tell you why.

If first-contact resolution drops, for example, the answer isn't automatically to tell agents to resolve more tickets on the first response. It might mean the team doesn't have enough information, that a particular type of issue is becoming more common, or that another part of the business is creating problems that are landing with support.

That's where the operational side becomes important.

You have to look beyond the number.

Customer support tells you a lot about the rest of the business

One thing I've come to appreciate about customer support is that it often gives you a view of problems that other parts of the business don't see as clearly.

Customers will tell you when something is confusing. They'll tell you when a product isn't meeting expectations, when a delivery process isn't working, when the website isn't clear or when a policy doesn't make sense from their perspective.

Support teams end up sitting at the intersection of all of that.

That's why I don't think customer service should be treated as an isolated function that simply handles whatever arrives in the inbox.

The patterns coming through support can tell you something about the wider operation.

If the same question is being asked repeatedly, perhaps the customer-facing information isn't clear enough. If a particular type of refund keeps becoming an escalation, maybe the underlying policy or process needs attention. If customers are repeatedly contacting support because they can't get information about their order, there may be an issue further upstream.

The support team can resolve the individual problem, but operations should also be asking why the problem keeps appearing.

That's where the function becomes much more valuable.

More people doesn't mean less management

There's also a misconception that once you've hired enough people, the manager's involvement should decrease.

In my experience, the nature of the management changes instead.

With a very small team, you can be close to every piece of work. As the team grows, that becomes impossible and, eventually, undesirable.

The role becomes more about creating the environment in which the team can perform consistently.

That means making sure people have the information they need, understanding where they are struggling, identifying recurring operational problems and helping people develop enough confidence to make decisions themselves.

It also means recognising when a problem is actually a people issue and when it is a system issue.

If one person repeatedly makes the same mistake, that may require coaching. If eight people are making the same mistake, I'd be looking at the process before I blamed the team.

That distinction can save a lot of unnecessary frustration.

The goal is a support operation that can absorb change

The biggest lesson for me from scaling the team was that capacity isn't just about the number of people you have.

It's about how well the people, processes, information and management structure work together.

A team of eight with poor processes can be less effective than a team of four with clear ownership and good systems. Adding people can give you more capacity, but only if the operation is designed to make use of that capacity.

And customer support doesn't exist in a vacuum. The business keeps changing. Products change. Policies change. Order volumes change. Customer expectations change. New problems appear.

The support operation needs to be able to change with it.

That's probably the part of scaling customer support that I find most interesting. The challenge isn't simply getting more people to answer more tickets. It's building an operation that can handle a growing and changing workload without quality disappearing along the way.

When that happens, customer support becomes more than a cost centre or an inbox that needs clearing.

It becomes a useful source of information about how the business is actually performing.

And for an operator, that's valuable information.