How outsourced live chat teams are staffed and measured, why chat concurrency changes the economics, and what to define before handing your chat channel to a provider.
Why chat is bought differently from voice
Live chat looks like a cheaper version of phone support. It is actually a different operating model, and the difference is concurrency. A phone agent handles one conversation at a time. A chat agent handles several simultaneously — commonly two to four, depending on complexity.
That single fact drives everything else. It changes staffing math, it changes how quality is measured, and it changes how you should read a provider's quote. A chat rate that looks similar to a voice rate is not comparable until you know the concurrency assumption behind it, because an agent handling three conversations costs a third as much per conversation as one handling a single chat.
Concurrency is also the main lever a provider can pull to protect margin. Pushing agents from three concurrent chats to five reduces cost and quietly degrades response times and answer quality. Agree the target concurrency in the contract and report against it. It is the most important number in a chat engagement and the one most often left unspecified.
What outsourced chat teams handle well
- Pre-sales questions on product fit, availability, shipping, and pricing, where a fast answer directly affects conversion
- Order and account support — status, changes, returns, and routine account administration
- Guided troubleshooting where steps can be sent as links, screenshots, or short instructions
- Qualification and routing, capturing intent and passing high-value visitors to sales
- After-hours coverage, where chat is often the most cost-effective way to stay reachable overnight
Chat handles poorly anything requiring extended diagnosis, emotional de-escalation, or complex negotiation. Build a clear path to escalate those conversations to voice rather than letting them run long in a channel that is not suited to them.
Where chat outsourcing creates revenue, not just savings
Support chat is a cost centre. Sales chat is not. A visitor asking a question on a product page is signalling intent, and the response time on that message correlates directly with conversion. Many organizations staff chat purely as deflection and miss this entirely.
If chat sits on commercial pages, measure it commercially: chat-assisted conversion rate, average order value with and without a chat interaction, and revenue per chat. These numbers usually justify better staffing than a pure cost view would allow, and they change the conversation about whether to extend coverage hours.
Metrics that matter
- First response time — the single strongest driver of chat satisfaction, measured in seconds
- Average response time within a conversation — the gaps between replies, where concurrency problems reveal themselves first
- Concurrency — actual chats handled simultaneously, reported against the contracted target
- Resolution rate — conversations closed without escalation or follow-up contact
- Abandonment — visitors who leave the queue before being connected
- Conversion and revenue per chat where chat sits on commercial pages
Watch the gap between first response time and in-conversation response time. A team can hit an aggressive first-response target and still deliver a poor experience if the customer then waits ninety seconds between every subsequent reply. That pattern is the clearest signal that concurrency has been pushed too far.
What to prepare before launch
A response library, not scripts
Chat rewards speed, and pre-approved responses for common questions make speed achievable. They should be building blocks agents adapt, not scripts they paste. Customers recognize a canned response immediately, and it undermines the one advantage chat has over a help article.
Tone and brand guidance
Chat is written, permanent, and easily screenshotted. Define how formal the voice should be, what the team may and may not commit to, how to handle complaints, and when to move a conversation to another channel.
System integration
Agents need order lookup, account access, and customer history inside the chat tool. Alt-tabbing between systems destroys the response times that make chat worth having.
Routing and coverage rules
Decide which pages trigger proactive chat, how sales and support conversations are separated, what happens when queues are full, and what the experience is outside staffed hours. An unanswered chat widget is worse than no widget.
Chat and automation together
Most mature chat operations run a bot in front of the human team to handle status lookups, common questions, and intent capture, then pass anything else to an agent with the conversation context attached. Handled well, deflection is real and customers do not notice the transition. Handled badly, the bot becomes an obstacle customers try to escape.
Two rules make the difference: always offer a visible route to a human, and never make the customer repeat what they already told the bot. If a provider proposes automation, ask to see the handoff, not the deflection rate.
Frequently asked questions
How many chats can one outsourced agent handle at once?
Commonly two to four concurrent conversations depending on complexity. The figure should be contractually agreed and reported, because raising it is the easiest way for a provider to cut cost at the expense of response quality.
Is outsourced live chat cheaper than phone support?
Per conversation, usually yes, because agents handle several chats simultaneously. Compare quotes on cost per conversation at a stated concurrency rather than on hourly rate alone.
Can outsourced chat agents sell as well as support?
Yes, and chat on commercial pages should be measured on conversion and revenue per chat rather than deflection. Sales-capable chat generally requires different hiring and training from support chat.
Should we use a chatbot alongside outsourced chat agents?
A bot handling status lookups and common questions in front of a human team works well, provided customers always have a visible route to an agent and never have to repeat information already given to the bot.
What happens to chat outside staffed hours?
Define this before launch. Options include hiding the widget, switching to a form or ticket capture, or extending coverage through a provider delivery location in another time zone. An unanswered live widget damages trust.