Read the ticket
Parse what the shopper is asking — tracking, delay, return window, address — before any tool runs.
Customer support
Customer Support Agent
The same "where is my order" tickets every day. An agent looks them up, answers from systems you already run, and stops when the case is not a lookup.
Last updated: August 31, 2026
The work today
Support queues fill with tracking, delivery, and return-status questions that already have answers in the OMS, carrier feed, and policy docs. People spend the morning copying those answers. Leadership then asks for "AI that just refunds." That is how you get a helpful model with a write tool and no stop button.
What the agent does
A support agent reads the request, calls only the lookup tools it is allowed to use, answers from live records, and escalates anything that looks like a chargeback, a regulator, a delivered-not-received dispute, or a write that moves money. Week one is reads plus a human queue — not createRefund.
Workflow
How a turn runs
Reads, tools, then a stop. Skip the stop and you have a demo.
Look up the order
Call named order, shipment, and policy tools. If the systems disagree, say so. Do not invent a status.
Answer or hand off
Reply from the record, or open the human queue with the evidence already assembled.
Stop on money
Refunds, cancellations, address changes, and gift cards wait for a person. The agent drafts; it does not send.
Systems
What it is allowed to touch
Named tools only. Anything undeclared is unreachable, regardless of the prompt.
Order and shipment
OMS or platform order API plus carrier events. One canonical order id — not three aliases the model has to guess between.
Policy and help content
Return windows, restocking rules, and published help articles the agent is allowed to quote.
Ticket system
Where the human queue lives. The agent writes a brief, not a second inbox nobody owns.
Approval
Anything that moves money or changes a fulfilled order is a proposal. A named reviewer sees the assembled evidence and takes the action in the commerce system. Prompt text is not an authorization boundary.
What good looks like
Outcomes we will stand behind
Qualitative on purpose. We do not have published agent case studies, so we will not invent a percentage.
First pass on repeat tickets
WISMO and tracking leave the queue when the record is clean. Ambiguous cases still reach a person — faster, with context.
A written stop list
Chargeback, attorney, regulator, PII correction, and over-rule discounts are named escalations, not "be helpful" leftovers.
An audit trail
Every tool call is logged. You can show what the agent saw, what it said, and who approved a write.
This page is the commercial summary for a customer support agent. The long-form build — tool catalogs, week-one read list, and eval notes — lives in the field-guide posts linked below. Those posts keep their own URLs. This page does not replace them.
Returns and fraud (not a sixth page)
Return-status questions (“was it received?”, “is the refund issued?”) are the same job as WISMO: look up a record, answer from it, escalate when the record is wrong.
Abuse and refund investigation are a section of this family, not /ai-agents/support/ and not a standalone SKU. If most of the pain is “people keep asking where the label is,” start with WISMO. If the pain is “we are eating fraudulent returns,” read the fraud and refund-investigation guides first — those are different tools and a different approval path.
What we will not do in week one
- Attach
createRefund,cancelOrder,updateAddress, orissueGiftCardbefore a reviewer owns the queue. - Let the model browse the open web “to be helpful” on a tracking question.
- Treat a help-center chatbot as an agent.
If your OMS or carrier templates already close most tickets, you may not need an agent. That is a valid readiness outcome.
How we start
Readiness first — can the agent join an order to a shipment without guessing? Then one scoped agent on the engagement at eCommerce AI Agents. AWS is how it stays up; it is not the first question we ask you.
Field-guide depth
These posts are the long-form canonicals. This page does not replace them, and they are not redirected here.
AI Customer Support Agent for eCommerce: Tool Access, Escalation, and Audit (2026)
A support agent that looks up orders is not a refund machine. Week-one reads only; reuse Gateway ~180 ms to ~95 ms and the ~$791/mo AgentCore silhouette — not ticket-cut KPIs.
WISMO Automation with AI Agents: Order Lookup, Tracking, and Escalation (2026)
WISMO is about 18% of helpdesk volume (Gorgias, via Redo) — automate lookup and delay notice, not invented ETAs. Reuse Gateway ~180 ms to ~95 ms and the ~$791/mo AgentCore silhouette.
AI Agents for Return Fraud and Abuse Detection (2026)
AI identifies return risk, gathers evidence, scores, and flags. It is never proof of fraud and must never automatically accuse customers. Reuse Gateway ~180→95 ms and ~$791/mo at 50K sessions.
AI Agent for eCommerce Refund Investigation (2026)
Investigate this refund — customer, order, product, shipping, return history, policy — then Recommend Approve, Reject, Partial, Replacement, or Human Review. Reuse Gateway ~180→95 ms and ~$791/mo at 50K.
AI Agent vs Workflow Automation: What Should eCommerce Businesses Use? (2026)
AI agents do not replace Shopify Flow or OMS state machines. Hybrid is the default: rules own money movement; the agent returns a structured decision. Reuse Gateway ~180 to 95 ms and ~$791/mo at 50K sessions — not store conversion KPIs.
Human-in-the-Loop AI Agents for eCommerce: Where Automation Should Stop (2026)
HITL is a queue with session id and tool trace — not a prompt. Reuse Gateway ~180 to 95 ms and ~$791/mo at 50K sessions. Do not auto-approve on SLA timeout.
The eCommerce AI Agent Readiness Assessment: Is Your Business Ready? (2026)
Score org-wide AI agent readiness /30 — data, integration, process, governance, priority. Below 16, skip writes. Reuse Gateway ~180→95 ms and ~$791/mo at 50K sessions.
The engagement
eCommerce AI Agents on AWS
Production AI agents for eCommerce on Amazon Bedrock AgentCore — support and WISMO, inventory, merchandising, margin, returns and B2B. Tool boundaries, evals before launch, and a human on anything that moves money.
Agentic Commerce Readiness
Make your store sellable to AI shopping agents. ACP and UCP protocol surfaces, an MCP server over your catalog, and product data that survives an agent comparison — built on AWS.
Where this sits
Family page → industry or decide tree → the engagement. AWS cases on this site are not agent results.
Other families
Five kinds of work
Sales & B2B
Quote requests, reorders, and account questions from buyers who will not tolerate a chatbot. An agent drafts the next step; a human still owns the relationship.
Sales & B2B agent →
Operations
The morning pile: exceptions, stalled orders, and the work nobody wants to triage. An agent ranks what needs a human today — it does not silently rewrite the warehouse.
Operations agent →
Inventory
What to reorder today, what is about to stock out, and what has quietly become dead stock — answered against live data, not last month's report.
Inventory agent →
Knowledge & catalog
If orders, customers, products, and inventory cannot be joined, an agent will guess. This is the data layer that makes every other agent honest.
Knowledge agent →
Common questions
Before you start
Is this a chatbot on the help center?
No. A chatbot that searches articles and cannot call getOrder is FAQ search. Ship that as search. A support agent uses named tools, a handoff rule, and a stop on money-moving writes.
Will it auto-refund?
Not in week one, and not by default. Refunds, cancellations, and gift cards are human-approved. The field-guide support post is explicit about this — the commercial page is not a looser promise.
Do you have case studies of support agents in production?
Not yet. Proof of work is the published support and WISMO field-guide posts, with copyable tool catalogs and eval notes. AWS case studies on this site are not agent-delivery stories.
Where do returns and fraud sit?
On this page, as a section — not a sixth family URL. Return-status lookups belong here. Fraud scoring and refund investigation have their own long-form guides, linked below.
Scope a support agent
Tell us the tickets that repeat every week. We will say whether an agent is the right first pass — and if a template already closes them, we will say that too.