When escalation equals violation (and the mailbox times out)
There are moments when customer service stops being a process and becomes performance art. Amazon has reached that stage.
For weeks I’ve been stuck in a loop: Kindle Direct Publishing (KDP) says my problem is Retail’s to fix, Retail says it’s KDP’s, and both sides insist I restart from scratch every time.
I escalated, looping in multiple Amazon email addresses. The result? An auto-generated reprimand scolding me for copying “an address not associated with my account.” Escalation itself had been redefined as a violation.
And now—because farce has no ceiling—I’ve received something even better: a Mail Delivery Subsystem error. Gmail reports that support@kdp.amazon.com refused to connect, timed out, and is effectively undeliverable.
Let’s be clear: the “support” inbox of the world’s largest online retailer can’t reliably accept mail.

What the AI sees
If Amazon is running AWS Comprehend (its own sentiment analysis tool) over my case, the dashboards must be shrieking:
- Sentiment: incandescent, escalating, hostile.
- Escalation risk: catastrophic — customer is going fully public.
- Agent adherence: robotic, repetitive, dismissive.
- Resolution metrics: in freefall.
And yet none of it matters, because even their support mailbox is now failing to support.
From Kafka to Monty Python
This is no longer just Kafka in a call centre. This is Monty Python’s “Dead Parrot” sketch with a corporate logo.
- Me: “This parrot is dead.”
- Amazon: “No sir, your account is functioning normally. Just enable Two-Step Verification.”
- Me: “I already did. It doesn’t work.”
- Amazon: “Have you tried enabling Two-Step Verification?”
- Me: “Your support inbox is literally dead.”
- Amazon: “We’ll escalate this to Retail.”
The leadership lesson
AI without ownership is just theatre. Escalation without accountability is recursion. And a support inbox that times out is the corporate equivalent of a locked door with a “customer-centric” sign nailed to it.
If you lead a team, don’t let this happen to you. A system can measure anger, but only empowered humans can resolve it.
2 replies on “Kafka in a call centre”
[…] Kafka in a call centre—a theme I’ve already explored in detail in this post, where even the support inbox itself […]
[…] At one point, their support inbox literally bounced my messages back, unable to accept mail. Kafka would have blushed. Monty Python would have laughed. I captured it in Kafka in a call centre. […]