Overview

Amazon’s seller‑support function is deteriorating rapidly as the company trims roughly 16,000 corporate positions in 2026. At the same time, a suite of new policies pushes more operational responsibility onto sellers. The convergence of slower assistance and higher compliance burdens creates immediate risk for anyone who depends on Amazon’s help desk to keep listings, accounts, and inventory running smoothly.

Key Points

• Support response times — Cases that once closed in a few days now linger for weeks or months, especially suspension appeals.
• Template‑only replies — Sellers frequently receive generic answers that ignore case specifics, forcing multiple reopenings.
• AI routing errors — Amazon’s automated support often misclassifies issues, sends tickets down the wrong workflow, and sometimes closes them prematurely.
• FBA prep services removed — Sellers must now prepare and label shipments themselves or contract third‑party providers, adding cost and logistics.
• Prepaid return‑label rule — All seller‑fulfilled orders, even high‑value items, now require prepaid return labels, increasing return expenses.
• Inventory claim window cut — The period to file claims for lost or damaged FBA stock dropped from 18 months to 60 days, tightening the margin for error.

How the Support Shift Is Implemented

1. Workforce reduction rollout — Amazon announced the elimination of 16,000 corporate roles, targeting layers that include back‑office and support functions. For example, a senior support analyst in the U.S. office received a 90‑day internal‑transfer window before separation.
2. AI‑first ticket triage — New generative‑AI tools automatically scan incoming tickets, assign a category, and suggest a resolution path. A seller reporting a “listing suppression” may be routed to a self‑service article instead of a live agent.
3. Escalation gate tightening — The system now requires a higher confidence score before escalating to a human. If the AI rates a case as 70 % certain, it closes the ticket, even when the seller’s issue persists, as seen in cases where “account health” warnings remain unresolved.