Today, I experienced one of the most exasperating phone calls in recent memory—one that left me questioning the very systems designed to protect our financial security.
The call was supposedly from my bank, but as you’ll see, it was anything but straightforward.
This incident underscores the importance of vigilance when it comes to safeguarding personal information, especially in an age rife with scams and fraud.
Let’s rewind a bit.
I’m Daniel Shensmith, a barrister practicing in England and Wales, and I also run the Black Belt Barrister channel.
On this platform, I often discuss legal matters, but today, I want to focus on a critical topic: the safety protocols we should all observe during phone interactions with banks.
First and foremost, banks consistently warn customers against accepting incoming calls or texts asking for sensitive information.
Scammers frequently employ these tactics to trick unsuspecting individuals into revealing security details.
They might call you, claiming to be from your bank, and request personal information that can ultimately lead to unauthorized access to your accounts.
Years ago, it was common for banks to call and ask for confirmation of personal details like your date of birth.
However, once people realized how easily these calls could be spoofed—making it appear as if they were coming from the bank—most of us became more cautious.
The media has reported numerous stories of individuals losing their life savings after being deceived by such scams.
In my case, I recently filled out a routine form for my business bank account, which requires periodic updates about the nature of my business and any changes over the past year.
Naturally, I anticipated a follow-up call for clarification.
When I received the call, the caller claimed to be following up on the form I submitted.
This detail led me to believe that it might genuinely be the bank reaching out.
However, the conversation quickly took a familiar turn.
The caller requested that I confirm my postcode and company name.
My immediate response was a firm “no.” How could I be sure they were actually representing the bank?
This led us into a frustrating back-and-forth where they insisted they needed my security details.
I countered that they should prove their identity first.
I suggested they send me a secure message through the bank’s official app or website instead.
The response?
They wanted to send me a text message.
Alarm bells went off in my head.
I knew that providing a code sent via text to someone who called me could open the door to fraud.
Ironically, the bank’s own website advises customers against sharing such codes with anyone who calls them unexpectedly.
Yet here I was, engaged in a conversation that seemed to contradict those very guidelines.
My instincts told me that while this might indeed be the bank, I couldn’t take the risk of compromising my account security.
To add to the absurdity, we had previously contacted the bank to verify a similar phone call.
That time, we confirmed it was legitimate, but they insisted we hang up and wait for a callback from a different department.
We refused, citing the potential for fraud.
