HSBC (US): Nearly impossible to reach a human. Had to put...
A HSBC (US) customer review by GetHuman user ~virginiarappe from October 26th, 2017
Background on ~virginiarappe's case
GetHuman: ~virginiarappe - can you tell our other HSBC (US) customers when your case took place?
~virginiarappe: Sure. It was late at night, on October 21st.
GetHuman: Did you reach out to HSBC (US), and if so, how?
GetHuman: And which of these common HSBC (US) customer issues best describes the reason you wanted to talk to them?
(Shows ~virginiarappe a list of common HSBC (US) problems)
~virginiarappe: "Question" was why I was trying to call.
~virginiarappe's review of HSBC (US) customer service
GetHuman: So how would you sum up your experience for GetHuman's HSBC (US) 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.
~virginiarappe: Nearly impossible to reach a human. Had to put in account number and other security information before even getting the basic touchtone options. Then had to say my card was stolen in order to speak to human--and that after *** minutes on hold!
GetHuman: Let's quantify your experience contacting HSBC (US). On a scale of 1 to 5, how easy is it go get help on a HSBC (US) problem?
~virginiarappe: I'd give them a four 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?
~virginiarappe: I'd give them a one out of five on communication.
GetHuman: And what about HSBC (US)'s ability to quickly and effectively address your problem?
~virginiarappe: For that I would say four out of five.
GetHuman: And finally- any advice for other HSBC (US) customers?
~virginiarappe: Call them early in the day or late. Don't forget any personal or account information you might need for HSBC (US) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~virginiarappe taken from his HSBC (US) customer service problem that occurred on October 21st, 2017.