The Day Halifax’s Complaint System Exposed Itself — And Didn’t Even Notice

My post content

Most people think banks mishandle complaints because of rude staff or slow replies. But sometimes the truth is far more interesting — and far more revealing.

This is the story of how Halifax’s own complaint‑handling system quietly admitted something it should never have done:

It decides which customer emails are allowed to reach a human.

And it only takes one Gmail thread to prove it.

1. The Setup: A Final Response They Expected Me to Accept

On 28 April, Halifax issued its “final response.” In their world, this is the moment the customer:

• gives up,

• accepts the outcome, and goes away quietly

In other words, they expected a surrender notice.

But instead, on 7 May, I replied directly to the handler’s email with:

• technical questions

• reasonable adjustment issues

• valuation challenges

• recycled‑device concerns

• FOS references

A normal complaint system would:

• deliver the reply

• reopen the case

• force the handler to respond

Halifax’s system did none of that.

2. The Behaviour Switch: From “Active Complaint” to “Silence Him.”

Here’s where it gets interesting.

On 6 May

My email behaved normally — routed to the handler.

On 7 May

My email vanished into the “pending/unassigned” bin.

Same email address. Same thread. Same handler.

Different system behaviour.

Why?

Because the moment Halifax issued its final response, the system flipped into a different mode:

Mode A — Before final response:

All replies go straight to the handler.

Mode B — After final response:

Replies are diverted into a “pending” bin unless the handler manually reopens the case.

She didn’t reopen it. She never saw my reply. The system swallowed it.

And then it auto‑closed the complaint.

3. The Smoking Gun: No 8 May Reply

If Halifax had seen my 7 May message, there would be:

• a reply

• a reopening

• an escalation

• Ombudsman rights

• a closure confirmation

Instead, there is nothing.

Because the handler never received it.

Because the system never delivered it.

Because the system decided my reply didn’t “count.”

This is not a human mistake. This is a workflow failure.

4. Why This Is a Breach — And a Serious One

Under FCA DISP rules, a firm must:

• Consider all evidence before closing

• not block or divert customer replies

• Do not close a complaint while issues remain

• not operate systems that restrict communication

• Do not deny a customer their right to escalate

My 7 May reply contained:

• regulated questions

• reasonable adjustment issues

• valuation challenges

• FOS references

All of which must be reviewed before closure.

They weren’t.

Because the system hid my email.

This is exactly what the FCA calls:

“Obstruction of the complaint process.”

5. The Pattern They Never Expected Me to Spot

Most customers would never notice the difference between:

• a reply that reaches a handler

• a reply that gets swallowed by the system

But I did.

Because the behaviour changed overnight.

And because the routing of my 6 May and 7 May emails was completely different, despite being sent to the same address.

That’s how I caught them.

Not by shouting. Not by escalating. Not by threatening.

Just by watching the system slip.

6. The Conclusion: Halifax Didn’t Ignore Me — Their System Did

This wasn’t:

• a rude handler

• a lazy handler

• a deliberate snub

This was:

• a broken workflow

• a mis‑routed reply

• a failure to process customer communication

• a closure without reviewing evidence

• a breach of FCA DISP rules

• a denial of escalation rights

And the best part?

**Their own system exposed it.

All I had to do was notice.**