Categories
Amazon Anxiety and stress Decision-making Decision-making Leadership

Amazon KDP: Even when they say it’s fixed, it isn’t

Amazon told me my KDP two-step verification problem was fixed. Screenshots prove otherwise. I remain locked out, trapped in an endless cycle of contradictory advice and system failures. This isn’t just incompetence—it’s abdication of responsibility. Read the evidence

Amazon told me it was fixed.

Manager Nidheesh assured me that two-step verification had been temporarily disabled, just long enough for me to log in, update my phone number, and restore access. That should have been the end of it.

It wasn’t.

On 30 August 2025, I logged in from Safari on my MacBook Pro M1 Max. Here’s what I got:

  • Error 413 — Amazon’s own CloudFront choking on the request.
  • A second screen demanding a verification code, despite the repeated promises that 2SV had been disabled.
  • And finally, the same dead end I’ve been facing for months.
Amazon KDP: Even when they say it’s fixed, it isn’t
Amazon KDP: Even when they say it’s fixed, it isn’t
Amazon KDP: Even when they say it’s fixed, it isn’t
Amazon KDP: Even when they say it’s fixed, it isn’t

Screenshots don’t lie. The system is not fixed. The advice is contradictory. And the “solutions” are nothing more than recycled boilerplate, dressed up as support.

Once again, Amazon proves that its so-called customer obsession is theatre. The reality is a closed loop: blame the user, recycle advice, insist the system works, then quietly hope the customer goes away.

I’m not going away. Every failed login, every error message, every contradictory reply is being published in full. This isn’t just about me—it’s about every author whose work and livelihood can be stranded inside Amazon’s broken machinery.

And Andy Jassy, CEO of Amazon—your name is on every single one of these failures.

⚑ Lesson for leaders

Proof before proclamation—verify the fix

Announcing a fix without confirming it in the customer’s reality destroys trust. If you ask for evidence, your systems must accept it; if you promise a deactivation, the customer must be able to complete the task. Leadership owns the loop end-to-end until the outcome is verified.

  • Single owner. One named person stays on the case until closure—no handballing.
  • Evidence both ways. Provide proof-of-fix (steps, screenshots, audit note) and accept customer evidence without friction.
  • Keep the channel open. If you request artefacts, ensure your inboxes/portals can receive them (no bounces, no size traps).
  • Verify in the customer context. Test the fix in the same flow, device and region the customer uses—then confirm in writing.
  • Timebox and escalate. Set an SLA for verification; auto-escalate after a single failed attempt.

Trust isn’t a slogan—it’s a behaviour you can measure. Close the loop, or you lose the customer.

Related stories

Author