Erroneous Related Accounts Suspension: Successful Case Resolution
Hello everyone!
Let’s talk about mistakes more!
Related accounts. One of the difficult but solvable deactivations.
We begin the process of finding out possible connections. We found out that one possible connection could be by registered name in the accounts. The related account was reactivated before. So we realized that Amazon mistakenly deactivated our client’s account. And our mission was to persuade Amazon that our client’s account was a good one and Amazon made a mistake.
Before us, the client sent a couple of good appeals, but Amazon rejected it all the time. He attached screenshots of the related account reactivation, but Amazon stubbornly stood its ground. It was possible to continue writing appeals in different ways – standard PoA, where we briefly and clearly describe the problem, corrective, and preventive measures. It was possible to go the other way – to write a long voluminous letter and create cases. But we decided to do otherwise.
The first thing we decided to do was call and talk to the support, maybe we could find out something. On the first call, we once again clarified the possible information of the related account (email, registered name in the account, date of registration of the account). The call ended with the words – “we are sending your application to the internal team. Please wait.” Naturally, Amazon can’t tell us how long to wait. We called every 2-3 days. So, we called 4 times, but the answer was “still under review, wait for an answer.”
At the same time, we sent a message to Jeff’s team, where we attached a screenshot of the related account reactivation and a letter where we described the chronology of two accounts, thereby trying to convince them that the client’s account was deactivated in error. There was a glimmer of hope that such a respected Amazon team would help us with something, but alas, no.
In order not to delay the case for a long time and not wait for an answer from Amazon, we wrote a complaint to a third-party service. The scheme is the same – a screenshot of the related account reactivation and an accompanying letter with evidence.
A couple of days later, a response came from both the third-party service and Amazon (how unexpectedly) – “Your account has been reactivated. Sorry for the inconvenience.”
The moral of the story is – do not wait for the grass to grow, especially if it is Amazon. Act on your own, because it can take a very long time to wait for an answer (especially if you know that your account deactivation was in error, and it is unlikely that Amazon can provide specific arguments for the deactivation). It will only scare you with rejects. We all make mistakes sometimes.
To prove the truth and show Amazon that they made a little mistake (sometimes a huge one) – we will be glad to help you, you can count on us.
