Bank of America: Trying to find any BOA rep who works with or is...
A Bank of America customer review by GetHuman user ~cpwhitin from November 21st, 2017
Background on ~cpwhitin's case
GetHuman: ~cpwhitin - can you tell our other Bank of America customers when your case took place?
~cpwhitin: Yes I can. It was middle of the night, on November 12th.
GetHuman: Did you reach out to Bank of America, and if so, how?
GetHuman: And which of these common Bank of America customer issues best describes the reason you wanted to talk to them?
(Shows ~cpwhitin a list of common Bank of America problems)
~cpwhitin: "Technical support" was why I was trying to call.
~cpwhitin's review of Bank of America customer service
GetHuman: So how would you sum up your experience for GetHuman's Bank of America 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.
~cpwhitin: Trying to find any BOA rep who works with or is familiar with your ART CONSERVATION PROJECT. None of the operators succeeded in putting me through to a person or a number that helped. Most baffling!
GetHuman: Let's quantify your experience contacting Bank of America. On a scale of 1 to 5, how easy is it go get help on a Bank of America problem?
~cpwhitin: 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?
~cpwhitin: I'd give them a one out of five on communication.
GetHuman: And what about Bank of America's ability to quickly and effectively address your problem?
~cpwhitin: For that I would say four out of five.
GetHuman: And finally- any advice for other Bank of America customers?
~cpwhitin: Call them early in the day or late. Don't forget any personal or account information you might need for Bank of America to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~cpwhitin taken from his Bank of America customer service problem that occurred on November 12th, 2017.