If you run a store with real sales and real ad spend, you have probably noticed the same thing: most support tickets are the same handful of questions. "Where is my order?" "Can I return this?" "Did my discount apply?" That repetition is exactly what a chatbot platform is built to absorb.
This guide skips the ranked vendor parade. Instead it answers the questions an operator actually needs settled before signing a contract — what these platforms resolve, what they cost per resolution, where they fail, and how they differ from the broader "AI employee" category you are also being pitched.
What a support chatbot platform actually does
A modern support chatbot is a conversational layer on one surface — your chat widget, your help inbox, sometimes SMS or WhatsApp. It reads the buyer's question, pulls structured data (the order, the tracking number, the returns policy), answers, and escalates to a human when it is unsure.
The category has quietly reorganized around one idea: you pay for outcomes, not seats. Gorgias — which states its tools power "customer conversations for 40% of Shopify brands" (a vendor claim) — charges per resolved conversation, with each resolved conversation costing $0.90 on most plans and overage rates climbing to $1.00–$2.00 per interaction. A conversation is billable only when the AI closes it entirely on its own; anything handed to a human is not charged as an AI resolution.
Zendesk works the same way. Its AI agents are included in Suite and Support plans "with pricing based on the successful outcomes they deliver", with Suite Team starting at $55 per agent per month and Suite Professional at $115. Zendesk does not publish its per-resolution rate; third-party reporting puts it around $1.50 per committed resolution and $2.00 pay-as-you-go — treat those as time-stamped secondary figures, not official numbers.
Two structural facts matter more than any feature list. First, outcome pricing means your bill tracks volume, not headcount. Second, every serious vendor builds in a handoff path — which is an admission, baked into the business model, that these platforms do not handle everything.
The honest support-desk math
Vendor pages quote a per-resolution price and let you imagine the savings. Let's run it with operating numbers instead.
Say your store takes 300 support conversations a month — mostly order status, returns, and product questions. Assume the AI fully resolves half (150), a human handles the other half, and human handling runs 8 minutes per conversation. The resolution share is an assumption for the arithmetic, not a promised rate — Gorgias itself won't promise an automation rate, saying it "emerges from usage over time."
Option A — a human virtual assistant handles all 300. That is 300 × 8 min = 40 hours a month. At a mid-level offshore rate — Philippines virtual assistants run about $6–$10/hour at one to three years' experience — 40 × $8 ≈ $320/month, bounded by their working hours. At a fully-loaded US rate of $28–$65/hour, 40 × $40 ≈ $1,600/month.
Option B — the chatbot resolves Tier-1, a human takes the rest. 150 AI resolutions × $0.90 Gorgias annual rate = $135, plus the helpdesk subscription. The remaining 150 conversations × 8 min = 20 human hours → ~$160 offshore or $800 US. Total: **$295/month offshore-hybrid**, ~$935 US-hybrid.
Read that carefully. Against a US-cost baseline, the AI route is dramatically cheaper. Against a $6–$10/hour offshore VA, the pure dollar gap on 300 tickets is small — the stronger argument becomes instant 24/7 response and no management overhead, not price.
And neither option removes the human. Option B concentrates human attention on the hard half, because the AI skimmed off the easy tickets. Doubling your ticket volume doubles VA hours (and eventually forces a second hire); it only linearly raises per-resolution fees with no hiring step. That scaling difference is the quietest, most durable reason operators move.
Where these platforms fail — and who pays
The listicles are shy about failure. You should not be, because the liability lands on you.
The canonical case: Air Canada's website chatbot told a grieving customer he could claim a bereavement discount retroactively, contradicting the airline's real policy. A British Columbia tribunal found the airline liable for negligent misrepresentation and ordered it to pay CA$812.02, rejecting the argument that the chatbot was a separate legal entity. The tribunal confirmed companies remain responsible for what their AI tells customers. Your store owns every answer the bot gives.
So the practical failure map for an operator looks like this:
- Routine, structured tickets (order status, returns policy, tracking) resolve reliably — this is the layer the whole category is built on.
- Ambiguous, high-stakes edge cases are where confident wrong answers happen. The Air Canada case was a policy hallucination, not a glitch.
- Anything consequential should run through a review step. When independent vendors all converge on human-in-the-loop for serious actions, that is the industry telling you where the reliability line currently sits.
The honest expectation is a ramp, not a switch. The AI needs your policies, macros, and catalog before its resolution share climbs — which is exactly why Gorgias won't commit to a number up front.
Chatbot vs. "AI employee": not the same product
Here is where awareness-stage shopping gets confusing. The same search that surfaces support chatbots also surfaces "AI employees" and "AI agents for ecommerce." They are different things.
A chatbot answers on one surface. An AI employee takes multi-step actions across several of your tools, with your approval. Gartner draws the same line and warns about "agent washing" — rebranding chatbots and assistants as agents without real agentic capability — estimating only about 130 of thousands of self-described agentic vendors are the real thing, and predicting over 40% of agentic AI projects will be canceled by the end of 2027.
The upside is real too. Gartner also predicts that by 2029, agentic AI will autonomously resolve 80% of common customer service issues without human intervention. Note the qualifier — "common" issues — which is precisely the Tier-1 layer the support category already handles.
If you want the full breakdown of how chatbots, human virtual assistants, and AI employees compare for a store, our guide to AI employees for ecommerce maps all three layers. For the hiring-math angle specifically, see which AI tools help reduce time-to-hire and the deeper dive on AI employee service management.
Where PodVector AI's Victor fits
PodVector AI's Victor is an AI employee, not a support chatbot platform — so he solves a different problem than Gorgias or Zendesk, and the two can coexist.
Victor sees every order, every ad dollar, and every supplier cost together, so he can tell you the true per-order profit on each product. He integrates with Shopify, Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo, and delivers reports straight to your Google Drive. On the support side, Victor drafts customer-support emails and you approve the send — the same human-in-the-loop pattern every serious vendor lands on.
That approval gate is the point. Every write action Victor takes — pausing a Meta campaign, adjusting a Google Ads budget, changing a price or discount in Shopify, building a Klaviyo flow — runs past you before it executes. Victor is not a dashboard you read; he is an operator who proposes the move, shows you the profit math behind it, and acts only once you say go.
For a store weighing where support fits in a broader automation plan — or wanting to bring on this kind of help — our page on hiring AI developers and operators walks through the decision.
See your true per-order profit with Victor →
FAQs
What is a customer support AI chatbot platform for ecommerce?
It is software that answers buyer questions on one channel — your chat widget or help inbox — by reading structured data like orders, tracking, and returns policy, then escalating anything it can't resolve to a human. It is scoped to support conversations, not to running your ads, catalog, or email.
How much does a support chatbot cost per conversation?
Most platforms now price per resolved conversation. Gorgias lists $0.90 on most plans with overages up to $2.00; third-party reporting puts Zendesk around $1.50–$2.00 per resolution on top of seat fees. You pay only when the AI closes a conversation entirely on its own.
Is a chatbot cheaper than hiring a virtual assistant?
It depends on your baseline. Against a fully-loaded US VA at $28–$65/hour, per-resolution AI is far cheaper on Tier-1 volume. Against an offshore VA at $6–$10/hour, the dollar gap on a few hundred tickets is small — the real wins are 24/7 response and no management time.
Can an AI chatbot replace my whole support team?
No, and no shipping product claims it can. Outcome pricing is built on the handoff — you are billed only for what the AI fully resolves, and the rest routes to a human. The team shrinks per ticket; it does not disappear.
Who is responsible if the chatbot gives a wrong answer?
You are. A British Columbia tribunal held Air Canada liable for its chatbot's misinformation and rejected the "separate legal entity" defense. Budget review time for edge cases — it is the new cost that replaces execution time.
Is PodVector AI's Victor a support chatbot?
No. Victor is an AI employee that works across Shopify, Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo to compute true per-order profit and take approval-gated actions. He drafts support emails for you to approve, but his job is operating the store, not staffing a chat widget — so he complements a support platform rather than replacing one.