BPO or a dedicated team: who decides how your customers are served

There comes a point when the tickets no longer fit in the team. Somebody answers at night, first response drifts to two days, and the phrase «this cannot go on» shows up. From then on you are offered two paths described with the same words —outsourcing customer support— that in practice are not alike: hiring a BPO, or putting a dedicated person inside your operation.

What changes between the two is not how many hands you get. It is who decides how the work is done, and where what gets learned doing it ends up.

What you are buying in each case

A BPO sells a closed service. You hand over a volume and some rules, and it comes back handled with their process, their shifts, their tool and their people. It is their operation running for you, and that is their strength: they have many people trained on the same script and they can add more next week.

A dedicated team is the opposite in structure and the same in purpose. One full-time person who logs into your helpdesk with their own user, applies your policy and writes in your tone. They do not hand you a finished service: they do the work inside your operation. You direct; the provider answers for that person being there, knowing the job and performing.

Put like that it sounds like a nuance. It shows better compared against the criteria you feel in month three.

Who sets the criteria when the case is not written down

Every support policy leaves gaps. The customer is right and the policy says no. The order went out late because of the carrier and the customer wants the next delivery free. Nobody writes that down before it happens the first time.

In a closed service, that gap is filled by their process. It has to be: with one team serving several clients, you need a rule that works for all of them. The answer comes out correct and it comes out foreign. It is not the one you would have given.

With a dedicated person, the gap is filled by asking you, and by the third time there is no need to ask. There is no magic in it: the same person sees the same cases every day and builds your criteria, not a criteria.

Where the knowledge of your product ends up

This is the difference you pay for late. Answering tickets teaches you what breaks, what people ask before buying, which item runs small and which line of the manual nobody understands. That knowledge is worth money and it goes somewhere.

In a closed service it goes to their knowledge base and their script, which are theirs. If you change provider, you start from zero: what was known lived in their documentation and in their people, and neither of the two stays with you.

With a dedicated team it goes to your helpdesk, your canned answers and your documentation, because that person works inside your tools. And it also reaches your desk: whoever answers your tickets every day knows what needs fixing on the product page, and tells you. That is what turns customer support into something more than a cost.

What happens with peaks

Here the BPO wins, and it is worth saying so for the rest to hold up. If your volume multiplies in November and drops back in February, a large team absorbs that by moving people between accounts. It is built for exactly that.

A dedicated person is one person: they feel the peak just as your team does. What changes is where they start from. By November they already know your catalogue, your returns policy and your carriers, instead of learning them with a full queue. If the peak is predictable, you prepare before it and add another role. If the peak is huge and short, the closed service fits better.

In an ecommerce this is rarely an all-or-nothing choice: there are stores that run support with a dedicated person all year and reinforce the campaign some other way.

What happens when you want to change something

A practical question: you want to change the returns policy on Tuesday and have it applied on Wednesday.

With a closed service that goes through their circuit: notice, script update, shift training, effective date. It is reasonable —with many people answering, a badly communicated change is worse than no change— and it is slow.

With a dedicated person, you tell them on Tuesday. The cost of coordinating a change is one conversation. If your operation barely changes, the difference does not matter. If you change prices, supplier or catalogue every couple of weeks, it is the whole difference.

How long it takes you to notice something is wrong

This is the one people look at least when deciding and the one that hurts most afterwards. A service delivered closed is measured by what the provider reports, and what it reports arrives aggregated: volume, average times, satisfaction. A lot of bad replies fit inside an average.

When the work happens in your tools, the replies can be read. You can open any ticket and see how it was answered. The times are on your dashboard, not on a slide. And the warnings arrive earlier: the same question three times is a signal, and only whoever reads them all can see it.

That does not mean you have to supervise. It means you can. The difference between those two is the difference between finding out in March and finding out the following week.

When the BPO is the right choice

There are three situations where we would not hesitate.

• Very high and fairly stable volume. When the work does not fit in one person or in a few, what you need is a structure with shifts, supervision and cover, and building that yourself is building a company inside your company.
• Several languages at once. If you serve in five languages, covering each one with a dedicated person is an entire payroll. A large team spreads that far better.
• Genuine 24/7 cover. Not «until eleven», but nights, weekends and public holidays with no gaps. That means shifts, and shifts are solved by whoever already has them.

If you are in any of the three, the comparison ends here and you do not need the rest of the article.

When the dedicated team is the right choice

And the three on the other side, which describe most of the companies that write to us.

• The work fits in one person or a few. A ticket queue that today takes half the team in snatched moments is usually one full role, badly shared out.
• You need to know the product to answer. Catalogues with variants, services with conditions, anything where the right answer depends on knowing how what you sell works.
• Your tone is part of what you sell. If your brand shows in how you write, a foreign script is visible from the first email.

And the question that works for both

Whichever you choose, the useful question is not «how much does it cost». It is who answers when it fails. Who provides the equipment, where your data is kept while somebody works, what happens the day that person falls ill, who manages their performance and what a replacement costs you. Those answers separate the real providers, and we have ours written down in remote talent so you can compare them with whoever you are considering.

If what you have is a queue that never goes down and a team answering at night, start by measuring one real week of volume: how many tickets come in, through which channels and how many go unanswered. With that number the decision takes half an hour; without it, the decision is intuition and it is paid for in month three.