LloydsTSB: wrote to lloyds at east dulwich re my debit car...
A LloydsTSB customer review by GetHuman user ~jm cairns from November 6th, 2017
Background on ~jm cairns's case
GetHuman: ~jm cairns - can you tell our other LloydsTSB customers when your case took place?
~jm cairns: Sure. It was middle of the night, on November 1st.
GetHuman: Did you reach out to LloydsTSB, and if so, how?
GetHuman: And which of these common LloydsTSB customer issues best describes the reason you wanted to talk to them?
(Shows ~jm cairns a list of common LloydsTSB problems)
~jm cairns: "Setup an account" was why I was trying to call.
~jm cairns's review of LloydsTSB customer service
GetHuman: So how would you sum up your experience for GetHuman's LloydsTSB customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~jm cairns: wrote to lloyds at east dulwich re my debit card renewel as i live in bulgaria i wrote to them twice in one month but do not have the courtesy to reply i asked how i could gj.m.cairnset a renewel and save me coming to the uk but they have completely ignored me can you help???
GetHuman: Let's quantify your experience contacting LloydsTSB. On a scale of 1 to 5, how easy is it go get help on a LloydsTSB problem?
~jm cairns: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~jm cairns: I'd give them a two out of five on communication.
GetHuman: And what about LloydsTSB's ability to quickly and effectively address your problem?
~jm cairns: For that I would say five out of five.
GetHuman: And finally- any advice for other LloydsTSB customers?
~jm cairns: Call them early in the day or late. Don't forget any personal or account information you might need for LloydsTSB to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jm cairns taken from his LloydsTSB customer service problem that occurred on November 1st, 2017.