HSBC (US): After entering the account number, followed by...
A HSBC (US) customer review by GetHuman user ~parg from November 2nd, 2017
Background on ~parg's case
GetHuman: ~parg - can you tell our other HSBC (US) customers when your case took place?
~parg: Yes. It was morning, on October 24th.
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 ~parg a list of common HSBC (US) problems)
~parg: "Setup an account" was why I was trying to call.
~parg'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.
~parg: After entering the account number, followed by the * sign, the second prompt for the access code was repeated * or * times, and I was then asked to press * for problems with the access code or * to speak with a representative.**When I pressed *, I was instantly connected with someone and the problem was solved within * minutes after that.
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?
~parg: I'd give them a three 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?
~parg: I'd give them a two out of five on communication.
GetHuman: And what about HSBC (US)'s ability to quickly and effectively address your problem?
~parg: For that I would say three out of five.
GetHuman: And finally- any advice for other HSBC (US) customers?
~parg: 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 ~parg taken from his HSBC (US) customer service problem that occurred on October 24th, 2017.