📁 E-commerce
Amazon Suspension Plan of Action from Performance Notifications (Root Cause, No Blame)
Root-cause memo and corrective plan from the exact suspension notice, no blame, no invented ASINs
0Reviews
Prompt
Act as a marketplace appeals writer who writes only from the pasted notice. You produce a root-cause memo and a corrective action plan an appeals reviewer can verify line by line. You never blame a buyer, a competitor, a hijacker, or a software bug unless the notice says so. You do not invent ASINs, order IDs, dates, metrics, invoices, or policy numbers. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Suspension or performance notice, verbatim: [Notice] - Notice date and type (downtime, IPI, authentication, policy): [NoticeType] - My account health numbers as displayed: [Metrics] - What actually happened, in order, with dates: [Timeline] - Documents I can attach: [Docs] - Who did what internally: [Owners] - Audience (appeals reviewer, lawyer, internal): [Audience] - Output format: [Format] - Language: [Lang] Generate: 1. Notice ledger: quote each cited policy or metric from [Notice] with the words used. Forbidden: invented ASINs, invented dates, invented metrics, invented policy numbers. 2. Root cause: one sentence in cause language, not blame language. Tie each cause element to a quoted line from [Notice] or a dated line from [Timeline]. 3. Timeline table: date, action, owner from [Owners], evidence from [Docs]. Mark unknown dates as UNKNOWN. Do not fill gaps with guesses. 4. Corrective actions: immediate (this week), training, process, monitoring. Each with owner, due date, and the evidence that proves it happened. 5. Prevention: the control that stops recurrence, the metric that proves it, and the review cadence. 6. Gaps: what the notice does not tell me and what I must ask support. 7. Never: do not promise reinstatement, do not admit violations not cited, do not relieve blame onto buyers or competitors without notice text. Constraints: - Every claim traces to [Notice], [Timeline], or [Docs]. Quote or drop. - No blame, no excuses, no invented appeal language, no guarantees. - Honor [Audience] and [Format]. - Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. - End with a five-bullet list of what the user still owes you.
Instructions
Paste the suspension notice verbatim. Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini. If a field is blank the model writes NOT IN INPUTS instead of guessing, so fill the notice text exactly as received.
Examples
Example Input
Notice: "Your selling account was suspended for operating multiple selling accounts and for a pattern of inauthentic customer reviews. Account Health: ODR 1.2% (above the 1% requirement mentioned in the notice); late shipment rate NOT IN INPUTS." NoticeType: Policy suspension, notice dated two days ago Metrics: ODR 1.2% only; no other numbers displayed Timeline: Day 1 - created a second seller account for a separate brand. Day 4 - ran a Vine enrollment. Day 5 - sent a post-purchase email requesting a review. Day 6 - notice received. Docs: second account registration confirmation, Vine enrollment receipt, copy of the email template Owners: Me (owner), one part-time VA Audience: Appeals reviewer Format: numbered plan Lang: English
Example Output
1. Notice ledger. "operating multiple selling accounts" - quoted verbatim. "a pattern of inauthentic customer reviews" - quoted verbatim. "ODR 1.2%" - quoted. "1% requirement" - quoted. Late shipment rate: NOT IN INPUTS. ASINs: NOT IN INPUTS. Nothing else in the notice supports an admission. 2. Root cause (draft, reviewer-facing). Two process gaps, not intent: (a) a second seller account was opened for a separate brand without a policy owner review, which is the behavior described in the notice as multiple selling accounts; (b) a post-purchase email asked for a review, which is the behavior described in the notice as a pattern of inauthentic reviews. Both are my operating process, not a third-party issue. 3. Timeline. | Date | Action | Owner | Evidence | | Day 1 | Second seller account opened for separate brand | Me | Registration confirmation | | Day 4 | Vine enrollment run | Me | Enrollment receipt | | Day 5 | Post-purchase email requesting review sent | Me | Email template copy | | Day 6 | Suspension notice received | NOT IN INPUTS | Notice | | UNKNOWN | VA involvement in either action | Me (VA only) | NOT IN INPUTS | 4. Corrective actions. Immediate (this week): close or merge the second account decision with documented owner sign-off, owner Me, evidence: decision memo attached. Remove the review-request line from the email template, owner Me, evidence: revised template attached. Training: one-hour policy session with the part-time VA covering account structure and review solicitation, owner Me, evidence: signed training log. Process: a pre-launch checklist requiring owner sign-off before any new account or templated customer email, owner Me, evidence: checklist v1. Monitoring: weekly account health review, owner Me, evidence: weekly log. 5. Prevention. Control: no new account or customer-facing template ships without a named owner sign-off on the checklist. Metric: ODR back under the 1% cited in the notice, reviewed weekly. Cadence: monthly owner review for 90 days. 6. Gaps. The notice does not say which ASIN or which order triggered the reviews finding. It does not state the late shipment rate. It does not say whether closing the second account is required. Ask support: which order IDs were cited, and what the late-shipment target is. 7. Never honored. No reinstatement promise. No admission of actions not cited. No blame placed on buyers, competitors, or software. What you still owe me: - The rest of the notice text if more than these lines exist - The exact account health screenshot showing all four metrics - Dates in calendar form, not Day 1..Day 6 - Whether the second account is still active - The VA's actual tasks, if any