From a monitored review to a case
- Review Magic scans an active listing according to its monitoring schedule.
- New or changed review data is normalized and checked for supported policy signals.
- A potential violation receives a case file with the review text, policy basis, evidence, and proposed wording.
- By default the case queues automatically — subscriptions inside plan inclusions, Pay Per Removal inside the monthly removal budget. It waits only when the account opted into per-case review or no budget is set.
- Operations files cases through Amazon’s official process, strongest first, and records the external case reference.
- Review Magic waits and checks the source again before recording a removal.
Statuses that may need your action
| Status | Meaning | Who can act |
|---|---|---|
| Waiting on budget | The case is built and needs money consent: set or raise the monthly removal budget. It files automatically as soon as budget allows. | Client owner or billing admin; an agency only with separate exact client delegation. |
| Pending slot | The account has reached its concurrent active-case limit. | Usually no action; a slot promotes automatically when another case completes. |
| Queued by cap | The monthly removal budget or success-fee cap has no remaining room. | Raise it to file sooner — otherwise queued cases file automatically when the month resets. |
Statuses handled by Review Magic
| Status | Meaning |
|---|---|
| Queued | Ready for an operations specialist to claim. |
| Claimed | An operations specialist is reviewing and preparing the filing. |
| Submitted | The case was filed and the external reference was recorded. |
| Pending verification | The system is waiting before checking whether the review still exists. |
| Removed | A follow-up check confirmed that the review was no longer present. |
| Not removed | The review remained present or the attempt did not produce a verified removal. |
| Cancelled | The case was withdrawn before submission. |
Hands-off, answered
Do I need to approve anything before you file? No. We find the violation, build the case, and file it — strongest cases first, ranked by how likely Amazon is to remove the review.
How do you decide which reviews get appealed? Every flagged review is scored on policy-evidence strength. We work the list from most to least removable. On subscriptions, choosing among your 1–3-star reviews is our call — that is the point of hands-off.
What do I control, and what will I pay? Pay Per Removal: the monthly removal budget is the ceiling on how many removals we may bill; you pay only for verified removals. Subscriptions: included removals come first, and your plan price is the ceiling unless your cap allows more.
Why does my dashboard show cases I never asked for? Because the work is already done. Cases appear once your account, card, and products are in — from there everything files automatically, and this help center or support can answer anything specific.
Money authority: who sets budgets and fees
Case selection, wording, and filing are handled by Review Magic — no role approves individual cases. The one customer control is money: the monthly removal budget (and any success-fee cap), which only a client owner or billing admin can set or raise.
An agency can exercise that money authority only when the verified client owner has granted the current, separate fee delegation. Ordinary operational access does not imply money authority.
How a removal is confirmed
A submitted case does not become a success merely because Amazon accepted the filing. Review Magic performs a later source check and records durable removal evidence only when the review is absent.
Success-fee billing is tied to that confirmed outcome. If a filing does not result in a verified removal, no success fee is charged for the attempted case.
Why timing varies
Catalog size, review volume, case limits, evidence quality, Amazon response behavior, and verification windows all affect timing. Queue position is also isolated by account and safety rules; one large portfolio should not be allowed to erase every other customer’s access to processing.
Use the status and activity history instead of relying on a fixed completion promise. Contact support when a status has not changed beyond the time shown in the portal or when the evidence shown is incorrect.
Continue the task