What does an outsourced support provider deliver?
An outsourced e-commerce support provider delivers trained agents on shifts, working in the store's help desk from a script and a knowledge base the store supplies, priced per agent-hour or per ticket, often with phone and chat coverage and multiple languages. Good providers bring coverage a small store cannot staff, and people who can hold a difficult conversation with a frustrated customer.
The scope is the contract's hours and the script's coverage. Agents answer from what the script says and what they can find in the tools they have access to; consistency depends on training and turnover, and limits on refunds are enforced by supervision after the fact.
What does an Order Support FTE deliver instead?
An Order Support FTE on ftes.ai delivers ownership of the post-purchase function: every ticket read against the order, the shipment scan and the policy before it is answered, routine cases resolved inside the refund and goodwill limits the owner set, exchanges offered before refunds where policy allows, and anything above a limit or on the always-escalate list handed to the store's own people with the full context attached. It is reviewed on first-reply time, resolutions inside policy and escalation accuracy in the Targets tab.
The function runs at any hour and at any volume without a shift change, and its consistency comes from the policy document rather than from training, which is why the returns policy checklist matters before it starts.
Where does the outsourced team win?
The outsourced team wins where the work needs a person: a customer who is angry and needs to be heard, a phone call, a complaint that touches safety or a legal claim, a language or market the store does not otherwise cover, and any conversation where judgment about the relationship matters more than the policy. The Order Support FTE escalates those by design; a store without its own people to escalate to needs an outsourced team for exactly that.
The outsourced team also wins for a store whose post-purchase volume is small and unpredictable, where the fixed cost of a function is more than the tickets justify.
Where does the Order Support FTE win?
The Order Support FTE wins on the routine volume that scales with orders: order-status questions, returns inside the window, exchanges the policy allows, order edits before dispatch. It answers from the records rather than from a script, so a where-is-my-order reply states the actual carrier scan; it applies the limits by mechanism, so a refund above the limit cannot be issued by anyone having a bad day; and it tags every ticket's cause, so the owner can remove ticket types upstream rather than staff them.
It also wins on the record. Every resolution carries the order, the scan, the policy excerpt and the reason, and every escalation carries the same, so the store can answer why a return was accepted a year later.
How do the costs compare honestly?
The costs are on different units. An outsourced provider charges per agent-hour or per ticket, with minimums and coverage windows, paid whether the queue was full or empty. An Order Support FTE is metered in tokens from the organization wallet on ftes.ai, shared with any other roles the store runs, with a visible balance and a hard stop at zero, paid for tickets actually handled. The post-purchase support cost framework is the honest way to compare them: tickets per order by type, times handling cost, on the store's own numbers.
Which is cheaper depends on volume, mix and how much of the queue is routine. For a store where most tickets are order status and returns, the metered function usually costs less per resolved ticket; for a store whose tickets are mostly conversations, people may. Neither vendor should claim otherwise without the store's numbers.
What is the strongest pattern for a store?
The strongest pattern is a split by ticket type rather than by hour. The Order Support FTE handles the routine post-purchase volume inside policy and limits, and escalates everything else. People, the store's own team or an outsourced one, handle the escalations, the phone, the languages and the conversations that need a human voice, with the FTE's context in front of them so each takes minutes rather than an investigation. The owner keeps the policy and the limits.
That split keeps judgment with people and routine volume with the Digital FTE, which is the division every ftes.ai role is built on.