I’ve just had one of those experiences that sadly fails to surprise. I have a Lloyds Bank credit card, and in attempting to do an online transaction with it, was presented with the Click Safe authentication screen. This told me that I would be sent an SMS message with a code that I should enter on the next screen.
The problem was that the code was going to be sent to my old mobile number. Several months ago when I changed my mobile number I had logged in to my card account and updated it. Maybe it had regressed? I’ve checked but my online account was up to date. Clearly Lloyds have separate databases holding customer information, and they don’t always talk to each other. It’s the sort of incredibly annoying thing that still happens.
My penalty for being in this situation was that I had to phone the euphemistically named Customer Services, never something I’ve looked forward to with Lloyds.
I had to speak to three people, which included a gap in between the second and third where I was told I would have to wait at least ten minutes, and I could phone back another time. I don’t think there’s ever been a time when I’ve called when they haven’t been ‘extremely busy’.
Of course, I had to explain the issue three times. All of the staff tried to be helpful and polite. The last chap had to take me through some laborious authentication questions, and then told me that he’d updated the system to authorise the transaction I was trying to make, and he’d updated my phone number. I should wait five minutes, then try the transaction again.
I waited more than five minutes, and tried again.
I was told that the authorisation had been declined by the bank.
I waited, and tried again. Same result.
I phoned again, and although this time I check to use a number specifically for credit cards, I still had to be put through to ‘credit cards’ after explaining the problem.
The chap on the phone then explained to me that the problem was with the expiry date of the card. I guess that the error message couldn’t have told me that, as it would help someone who was trying to make a fraudulent transaction. I was using a password protection tool to auto-fill my card details, and although the information in the database is correct, it was appearing incorrectly on the payment form, and I hadn’t noticed. I still don’t know why that happens. I tried again with the correct information, and this time it worked.
There are a couple of take-outs.
Firstly, there’s no excuse for the lack of a joined-up view of the customer by Lloyds. When I updated my account online with my new phone number, it should automatically feed into whatever Click Safe uses.
Then there’s the inevitable transferring of calls, and the need to explain the problem multiple times. There has to be a better way.
It’s not all down to the business though. I did submit incorrect information when I tried again. I didn’t check, and if anyone had asked me, I would have insisted that I had entered the correct information. I know from experience on both sides of the fence that people will often swear blind that they did or didn’t do something online, only for the system logs to prove differently. People can look very sheepish when presented with the evidence, but that’s how people are. It’s not acting in bad faith. We’re fallible creatures who don’t always understand our own motives, and who don’t notice what actions we take. As far as possible, it’s the job of UX (and CX offline) to mitigate the impacts.