Customer support outsourcing costs, and who hides them

A founder with more support email than hours has three options, and the internet writes about two of them. You can answer it yourself. You can put something on your site that answers out of your own documentation. Or you can pay a company to put a person on it.

Deacon is ours, and it is the middle one. You paste one line of HTML to put it on your site, point it at your help pages, and it answers visitors from what it read there. Its free plan asks for no card and never expires. This page is about the third option, which we do not sell and have never written up.

The provider prices below were read from each company's own page on 22 September 2026, and every section links the page they came off. One figure comes from a stored copy of a page that will not serve us, and it says so where it appears. Where a company publishes no rate, that is what this page says about it.

What it costs, and which providers will tell you

Here is the part that makes support hard to shop for. We opened the pricing page of eleven companies that sell you people to answer customer questions. Five printed a number. The other six printed a form and a calendar link.

Those five publish three different units, which is the second problem. Hugo and Remote CoWorker sell an hour. Influx and Triniter sell a person by the month. Magic sells a week.

Influx is the most detailed of them. Its page says "Talent as a Service agents start from $1,400 per month for a Level 1 digital support agent in APAC, and from $1,700 per month in the Americas", and that "Part-time options (4h/day) are available from $1,000 per month". Its Managed Operations product, which adds training and quality checks, starts from $2,000 a month in APAC or EMEA and $2,100 in the Americas. Read the FAQ under it before you compare those two. A team leader is required on Managed Operations and costs extra, and where one Level 1 agent will do for Talent as a Service, "most clients start with two to five agents" on the other. There is "no setup fee and no long-term contract" on either. Figures from influx.com/pricing.

Hugo prints one number, "Starting at $11/hr per agent", and lists what the rate covers as "Onboarding, Management, QA, Training, WFM included", with "365/24/7 coverage in 60+ languages" and month-to-month contracts. Figures from hugoinc.com/pricing. Triniter is blunter still. "We have a flat pricing of $1999/person/month. No hidden fees." Figures from triniter.com/pricing. Magic sells assistants by the week, $270 for 20 hours and $540 for 40, billed every four weeks, with nothing to sign. Figures from getmagic.com/pricing.

Remote CoWorker is the fifth, and it keeps its rates inside a calculator rather than printing them in a table. Choose Customer Support and a non-voice agent and it quotes $8 to $9 an hour for an entry-level full-timer, $10 to $11 in the middle and $11 to $13 for a senior one, with a team leader from $8 to $10. Beside that it shows what local hiring would supposedly cost, and that second figure is worth ignoring, because the page reaches it by taking its own rate and multiplying by 3.3333. Figures from remotecoworker.com/pricing.

The table opens on the smallest thing anybody will sell you, an hour of a freelancer. Upwork's own rate page refuses to serve us, so that range is read from a stored copy of the page dated 12 December 2025 rather than from this week, and it covers contracts worldwide rather than any one country.

What you can buy off a published page is an hour or a person. The companies that would sell you something closer to a month of answered email are exactly the ones that will not print a price. EverHelp charges per ticket on its shared and AI teams, Helpware lists per transaction, outcome-based and gainsharing among its billing models, and Simply Contact's page says "Pay for outcomes, not headcount". Every one of those sits behind a form.

The ranges you find instead of rates come from the providers' own blogs, and they are wide enough to be useless. Helpware's write-up of what outsourced customer service costs answers its own headline question with $8 to $60 an hour, then gives a narrower $8 to $42 in a table further down the same page. It breaks the regions out from $6 to $12 in Uganda to $28 to $42 in North America, puts a dedicated agent at $1,800 to $3,500 a month, and says you can save up to 60% against a US in-house team by hiring in the Philippines. Those are Helpware's own figures with nothing under them. Four numbers on that page do carry a source, and the only hourly one among them is a Clutch range for the UK and Australia rather than any of the rates the page is about.

The category's biggest publisher puts no number on it at all. Zendesk's page on customer service outsourcing says outsourcing can come in cheaper than an in-house team and lists the overheads it removes, and there is not a rate anywhere on it.

For what a contact costs once somebody is answering, our cost per contact entry has the published benchmarks. Gartner's 2019 poll of service leaders put an assisted contact at $8.01 against about $0.10 for self-service. SQM Group's 2021 study of North American call centres put a call at $8.60 and a solved problem at $12.04. HDI's 2016 survey of IT support centres put the median ticket at $18.50. All three are old, and that entry also carries Gartner's 2024 benchmark of $13.50 and $1.84, which does not reconcile with the 2019 pair.

What someone answering for your product can and cannot know

A person you hire out answers from what you wrote down. That is the whole of their access to your product.

They cannot read your code. They cannot reproduce a bug on a branch, and they cannot tell a customer whether Thursday's release caused it. What they have is a script, your help pages, and whatever you said in the handover call. Every release you ship after that call is a document somebody has to write and somebody else has to read. When Hugo lists "Onboarding, Management, QA, Training, WFM included" inside its rate, that is the provider running the training. The material is still yours to write.

The class of question this works for is larger than most founders expect. Order status, refunds, password resets, where to change a billing address, how to cancel and why an invoice looks wrong all have a written procedure and a screen to carry it out on. A person can work through those all day and be genuinely better at it than you are, because they are doing it full time and you are doing it between two other things.

What the arrangement cannot take is the question whose answer lives in your head or in the code. An outsourced agent does one of two things with that. They send it back to you, which is the problem you started with plus a day, or they answer it anyway, which is worse than the day.

Then the person leaves. Verint surveyed 1,000 agents working in contact centres of more than 300 agents for The State of Agent Experience 2026, and 31% said they were likely to leave their role within six months, rising to 46% among the 18 to 34s against 8% of those aged 45 and over. What you taught the last one goes out of the door with them, and the replacement starts from your documentation again. Figures from No Jitter's write-up of the Verint survey.

Software reading your documentation has the same ceiling and a different way of failing. It is exactly as good as what you have written down, and no better. The difference is what you get back when it comes up short. A guess from a tired agent produces an unhappy customer and no record of why. Deacon produces the question, in a list, with a box to write the answer in.

Where outsourcing wins and Deacon has nothing

Deacon has no voice agent and no phone number. If your customers ring, nothing we sell touches that, and a BPO is the answer. The same holds for a human being awake at three in the morning. Deacon answers at three in the morning, out of your help pages, and when your pages do not cover the question it says so in its own words and the widget shows an email field. Hugo publishes cover round the clock and Influx sells it across time zones, both with people on the end of it.

Languages split the same way. Hugo publishes cover in 60 plus languages, spoken by people. Deacon replies in whatever language the visitor wrote in, whatever language your help pages are in. Its own words are English, though. The buttons, the ask box and the decline a visitor reads once a plan's answers are used up are all English, whoever is reading them.

A spike is the third one. Hugo says a team can scale up or down "with just 24 hour notice", and Influx sells headcount month to month with a month's notice to stop. Deacon has a ceiling, the answers your plan includes, and it does not raise itself. Past it, visitors get an ordinary decline and an email field, nothing is billed for those turns, and you can still read and reply to every conversation from the dashboard.

The last one decides it outright for a lot of shops. Issuing a refund, changing an order, cancelling a subscription and resending a receipt all mean acting inside another system, and Deacon acts in none. It has no ticketing, no helpdesk integrations, no WhatsApp, Instagram or SMS channel and no support inbox for email. There is no shared inbox with routing, assignment or a rota either. A question about the visitor's own account, invoice or data is turned down whatever your help pages say about it, on purpose. Deacon answers in a widget on your website, and that is the whole of its reach.

The arithmetic for 450 questions a month

Here is a month with every assumption in it stated. A software product, one founder, 450 support questions arriving by email and through the site. Eight minutes a question, which is what the worked example in our average handle time entry uses for a small software company's email. That entry links a Kustomer analysis of retail clients finding handle times anywhere from 0.82 to 46.6 minutes, so eight is a placeholder until you have timed your own. Eight minutes across 450 questions is 60 hours, and that multiplication is ours.

Two things fall out of that table. Buying an hour beats buying a person until you need something close to a full-time one, and a freelancer is still the only seller in the set who will let you buy exactly 60 hours. The companies sell cover by the month rather than hours, so the cheapest of their published floors lands around $1,000 for roughly 84 hours, most of which you have no use for.

The third option works on the 450 instead of the price. Say 300 of them are already answered somewhere on your site, which you can check in an afternoon against last month's inbox. Software answering those leaves you 150 questions, or 20 hours by the same eight-minute arithmetic. The comparison that decides it is 60 hours against 20 hours and one flat bill, and the 20 hours left are the ones only you could have done anyway.

We priced the whole AI side of this at a thousand questions a month in how much an AI chatbot costs, where the same month runs from $12 to $227 depending on what the vendor has decided to count. Shrinking the 300 is a separate job, and it is written up in how to reduce support tickets.

Deacon

Ours, and the only one on this page you can have running before you have spoken to anybody.

You paste one line of HTML to put the widget on your site. A crawl finds your pages and teaches it none of them until you have ticked the ones you want it to learn from, and it also takes the files you upload and any text you paste. It answers visitors out of that and nothing else. When it has nothing to go on it declines in its own words and the widget shows an email field. Leave an address in the chat and the conversation turns up unread in your dashboard, and your owners get an email about it three minutes later, unless one of you has opened the conversation by then or has the dashboard open anyway.

One flat plan a month, seats included, with a single meter that counts answers. The code has no overage charge in it at all, so a busy month cannot produce a bill you did not choose, and no plan upgrades itself. A plan caps four things and nothing else, which are how many answers you get, how much you can load into its knowledge, how many pages a month it will crawl and how many people sit on the team. The figures are on the pricing page, and the rest of what Deacon does is on the features page.

Where it sits between the other two is plain enough. An outsourced agent knows what you wrote down and can act inside your systems. You know everything, can act anywhere, and have no hours. Deacon knows what you wrote down, acts nowhere, and has every hour in the month.

None of the helpdesk half exists here. Nothing queues, nothing routes, nobody is on a rota and no clock is counting down to a reply you promised. Two or three people splitting a day's email need software built for that, which is a shared inbox rather than either option on this page, and the five kinds of customer support tool sorts out which is which.

Sorting last month's questions into two piles

The decision is not really about the prices above. Open last month's support email and put every question into one of two piles.

Pile one is every question whose answer was already written down somewhere you control, in a help page, a changelog, a pricing page or an email you have now sent forty times. Pile two is everything that needed you, your code, or somebody logged into another system with permission to give money back.

The two sizes pick the option between them. A large pile one and a small pile two is the case software was built for, because the answers exist already and the work is in repeating them. A large pile two, and in particular one full of refunds, order changes and account work, is the case for paying a person, because somebody has to be logged in and it will never be Deacon.

If both piles are large you need both. Start with the half that asks for no handover call and no contract, run it for a month, and count what is left in pile two before you go shopping for a person.