Seller Support resolves most things. When it does not, the difference between a problem fixed in two days and one that drags for three weeks is knowing the escalation ladder and working it in order.

Three rungs, each with its own trigger and its own timeframe — plus one case where you skip all of them.

[Watch the walkthrough](https://kb.trackiq.com/kb-assets/kbvideo-escalation-explainer-3c1a6250.mp4)

*Prefer to watch? One hundred and forty-three seconds on building a case that can be actioned, escalating by phone with a script, and knowing when severity justifies skipping the ladder.*

## **Rules that apply throughout**

**Start at step 1 unless it is genuinely urgent.** Account suspension or the removal of a revenue-critical ASIN justifies using every route at once. Almost nothing else does.

**Document every action.** Case IDs, dates, who you spoke to, what was promised.

**Move up when a step fails inside its timeframe** — not before, and not much after.

**Stay factual, concise and respectful.** Every rung is staffed by someone who did not cause your problem, and the tone materially affects whether they escalate for you.

# **Step 1: open a case**

**Always the starting point.** Right for listing errors, wrong category assignments, variation and linking problems, catalogue issues and policy questions.

**Seller Central → Help → Get Help and Resources.** Pick the closest issue, or **"My issue is not listed"** to describe it yourself.

**Choose the correct category** — product detail page, account health, fulfilment — because it decides which team receives it. A misrouted case fails slowly.

**Include everything, first time:**

**ASINs.** **Any existing case IDs.** **A timeline of events.** **Screenshots.** **Feed files and error messages.** **The exact resolution you want.**

**That last one matters more than people expect.** "This is wrong" invites a generic reply. "Please change the browse node from X to Y" gives someone something to action.

**Expect a first response within 24 hours.**

## **Two parallel routes worth knowing**

**Advertising and campaign manager issues go through the ads console support**, not Seller Central. Raising them in the wrong place wastes a day.

**Catalogue issues should also be raised through Brand Registry support**, in parallel with the Seller Central case. Two teams, two chances.

**If you have a strategic account manager, email them as well as raising the case.** Not instead — the case number is what everything else references.

## **If it stalls**

**Reply once in the same thread** with clarification or new evidence.

**If nothing moves after 24 hours or two exchanges, go to step 2.**

# **Step 2: phone**

**When the case has stalled, been closed prematurely, or the associate has misunderstood the request.** Also when time matters — a suppressed ASIN or rank falling because of a catalogue error.

**Seller Central → Help → Manage Support Cases**, select the case, reply. Some cases only offer email; when that happens, open a new case and reference the previous case ID.

**On the call, do three things:**

**Summarise briefly and give the case ID.**

**Ask explicitly for escalation** to a higher-level specialist or manager.

**Ask them to document the notes in the case and keep it open** until resolved. A case closed as resolved when it is not resets your progress.

## **A script that works**

Opening: *"I'm calling to escalate case 1234 regarding ASIN B09Z4X4383."*

Issue: *"This ASIN is assigned to the wrong browse node — Boat Tie Downs. It's a Boat Trailer Guide-On and belongs under Sports & Outdoors → Boating & Sailing → Boat Trailer Accessories → Boat Trailer Guides & Rollers."*

Request: *"I've already submitted a flat file and a category change request and the node hasn't updated. Could you escalate to a higher-level catalogue specialist and note that we're requesting a browse node correction from X to Y?"*

Close: *"I'd like the case kept open until the update is confirmed. Could you document these notes in the case?"*

**The pattern: identify, state the correct answer, ask for a specific escalation, ask for documentation.**

**Expect a follow-up by email within 24 hours** of the escalation.

## **If it still stalls**

**Go to step 3.** And on a critical issue, keep contacting support daily — you reach a different person each time, and outcomes genuinely vary with who picks it up.

# **Step 3: public escalation**

**When the case is stuck and phone support has produced nothing in 24 hours.**

Amazon's seller help account on X can be reached by direct message or a public post. **Both create a timestamp and often nudge internal routing.**

**Include:** the case ID, the ASINs, one or two sentences of summary, and the specific action requested.

**Use your brand account or a dedicated support handle**, and keep the tone factual. This is a routing mechanism, not a complaint channel — a measured post gets picked up, an angry one gets ignored.

# **When to escalate immediately**

Skip the ladder and use every route at once for:

**Account suspension.**

**Removal or suppression of a revenue-critical ASIN.**

**Anything actively costing significant daily revenue.**

**In those cases the cost of waiting exceeds the cost of over-escalating.** Everywhere else, working the ladder in order is faster, because each rung expects the previous one to have been tried.

**Which means the judgement call is really about severity**, and severity is a question about revenue rather than about how annoying the problem is.

![Issues ranked by severity, not by when you noticed them](/kb-assets/shot-alerts-severity-40ae4b.png)

**Ranking your open problems by what they are actually costing per day is what tells you which one earns a phone call today** — see [**Alert Categories, Priorities and What Actually Triggers Them**](https://kb.trackiq.com/hc/knowledge-base/articles/alert-categories-explained). Working from an inbox of Amazon notifications instead sorts your problems by arrival time, which has nothing to do with their cost.

## **Common mistakes**

**Escalating before step 1 has had its 24 hours.**

**Vague requests** that give nobody an action to take.

**Miscategorising the case**, so it sits with the wrong team.

**Raising advertising issues in Seller Central**, or catalogue issues without also using Brand Registry.

**Letting a case be closed** before the problem is actually fixed.

**Losing the case ID**, which every later step needs.

## **Related**

- [**Common TrackIQ Questions**](https://kb.trackiq.com/hc/knowledge-base/articles/common-trackiq-questions) — problems that are not Amazon's to fix.
- [**Triage a Rank Drop**](https://kb.trackiq.com/hc/knowledge-base/articles/triage-a-rank-drop) — diagnosing before escalating.
- [**Find the Variation Dragging Your Rating Down**](https://kb.trackiq.com/hc/knowledge-base/articles/find-the-variation-dragging-your-rating) — catalogue work that often needs a case.