Tweet
“It’s only because of their stupidity that they’re able to be so sure of themselves.” — Franz Kafka, The Trial
If Kafka had wandered into the offices of DCBL, he would have nodded in inspiration — and wouldn’t have needed to write fiction.
Act I: The Debt That Shouldn’t Have Lived
It began with a payment — made in good faith, made in full, and yes, made without a reference number.
A human oversight. A forgivable glitch.
The kind of thing most companies resolve with a quick glance at their bank statement and a shred of common sense.
But not DCBL.
No, they saw this as the cue for Act I of their finest procedural pantomime.
The payment — same amount, same date, same account — was suddenly “unallocated.”
So instead of, say, checking their records or picking up a phone, they did what any performatively indifferent organisation might do:
They escalated it straight to court.
No call.
No letter.
No “Hey, is this yours?”
Just a CCJ — gift-wrapped in silence and dropped like a bomb on an unsuspecting credit file.
Because why resolve an issue in five minutes when you can turn it into a legally binding catastrophe?
Act II: Silence in Stereo
Contact was made. Emails were sent. Evidence was shared.
What came in return?
Silence.
Then contradiction.
Then… more silence.
(A haunting trilogy, soon to be adapted for stage.)
Calls were placed to the two heads of the same beast: DCBL Ltd and DCB Legal Ltd.
One claimed the other was responsible.
The other claimed to have no idea who I was.
Apparently, they’re “separate legal entities.”
Except, of course, when they’re not.
This wasn’t communication — it was institutional amnesia dressed in business casual.
Eventually, a Subject Access Request was submitted. You know — that thing they’re legally obliged to respond to?
Spoiler: they didn’t.
Not properly.
Not promptly.
Not lawfully.
What followed wasn’t a GDPR-compliant disclosure.
It was a game of inbox ping-pong played by departments in denial.
Emails bounced. Replies stalled. Deadlines drifted past like tumbleweeds.
The UK GDPR wasn’t followed — it was skimmed, admired from a distance, and then gently ignored.
Act III: The Call That Disappeared
Then came the pièce de résistance:
The phone call.
Long. Documented. Central to the entire dispute.
Recorded? Absolutely.
Critical? Undeniably.
Available? Oh, of course not.
Despite internal notes quoting the call — and even referencing what was said — the actual recording had mysteriously vanished.
No deletion log.
No technical fault.
Not even the courtesy of a made-up exemption.
Just the old fallback: “Only some calls are recorded for training and monitoring purposes.”
Right. Because what are the odds that the one call that could unravel the procedural nonsense —
The one that proves miscommunication, misconduct, and mishandling —
Just happens to fall into the unrecorded abyss.
The timing? Impeccable.
The coincidence? Cinematic.
The transparency? Missing in action.
Where Are We Now?
A formal complaint has been filed with the Information Commissioner’s Office.
A civil claim is being prepared.
And this post?
It exists as a cautionary tale — not of debt, but of dereliction.
If you ever find yourself entangled with DCBL, here’s what I’ve learned:
It was a systemic shrug, disguised as process.
DCBL didn’t mishandle a case — they outsourced accountability, ran it through four departments, buried it under shared inboxes, and called the mess a response.
They’ve taken “We’re looking into it” and turned it into a corporate doctrine.
They don’t just delay.
They curate silence.
Five stars for literary absurdity.
Zero for lawful procedure.
And a standing ovation for whoever trained them to confuse a GDPR deadline with a vague suggestion.
“You are under arrest,” said the guard.
“But why?” asked K.
“That’s not for us to tell you.”
— Franz Kafka, The Trial
If Kafka had wandered into the offices of DCBL, he would have nodded in inspiration — and wouldn’t have needed to write fiction.
Act I: The Debt That Shouldn’t Have Lived
It began with a payment — made in good faith, made in full, and yes, made without a reference number.
A human oversight. A forgivable glitch.
The kind of thing most companies resolve with a quick glance at their bank statement and a shred of common sense.
But not DCBL.
No, they saw this as the cue for Act I of their finest procedural pantomime.
The payment — same amount, same date, same account — was suddenly “unallocated.”
So instead of, say, checking their records or picking up a phone, they did what any performatively indifferent organisation might do:
They escalated it straight to court.
No call.
No letter.
No “Hey, is this yours?”
Just a CCJ — gift-wrapped in silence and dropped like a bomb on an unsuspecting credit file.
Because why resolve an issue in five minutes when you can turn it into a legally binding catastrophe?
Act II: Silence in Stereo
Contact was made. Emails were sent. Evidence was shared.
What came in return?
Silence.
Then contradiction.
Then… more silence.
(A haunting trilogy, soon to be adapted for stage.)
Calls were placed to the two heads of the same beast: DCBL Ltd and DCB Legal Ltd.
One claimed the other was responsible.
The other claimed to have no idea who I was.
Apparently, they’re “separate legal entities.”
Except, of course, when they’re not.
This wasn’t communication — it was institutional amnesia dressed in business casual.
Eventually, a Subject Access Request was submitted. You know — that thing they’re legally obliged to respond to?
Spoiler: they didn’t.
Not properly.
Not promptly.
Not lawfully.
What followed wasn’t a GDPR-compliant disclosure.
It was a game of inbox ping-pong played by departments in denial.
Emails bounced. Replies stalled. Deadlines drifted past like tumbleweeds.
The UK GDPR wasn’t followed — it was skimmed, admired from a distance, and then gently ignored.
Act III: The Call That Disappeared
Then came the pièce de résistance:
The phone call.
Long. Documented. Central to the entire dispute.
Recorded? Absolutely.
Critical? Undeniably.
Available? Oh, of course not.
Despite internal notes quoting the call — and even referencing what was said — the actual recording had mysteriously vanished.
No deletion log.
No technical fault.
Not even the courtesy of a made-up exemption.
Just the old fallback: “Only some calls are recorded for training and monitoring purposes.”
Right. Because what are the odds that the one call that could unravel the procedural nonsense —
The one that proves miscommunication, misconduct, and mishandling —
Just happens to fall into the unrecorded abyss.
The timing? Impeccable.
The coincidence? Cinematic.
The transparency? Missing in action.
Where Are We Now?
A formal complaint has been filed with the Information Commissioner’s Office.
A civil claim is being prepared.
And this post?
It exists as a cautionary tale — not of debt, but of dereliction.
If you ever find yourself entangled with DCBL, here’s what I’ve learned:
- Document everything. Twice.
- Never confuse silence with compliance.
- And for the love of Kafka — do not mistake politeness for legality.
It was a systemic shrug, disguised as process.
DCBL didn’t mishandle a case — they outsourced accountability, ran it through four departments, buried it under shared inboxes, and called the mess a response.
They’ve taken “We’re looking into it” and turned it into a corporate doctrine.
They don’t just delay.
They curate silence.
Five stars for literary absurdity.
Zero for lawful procedure.
And a standing ovation for whoever trained them to confuse a GDPR deadline with a vague suggestion.
“You are under arrest,” said the guard.
“But why?” asked K.
“That’s not for us to tell you.”
— Franz Kafka, The Trial
Comment