Bank of America: never talked to a human. system repeatedly trie...
Eine Bank of America Kundenbewertung durch GetHuman-Benutzer GetHuman-429272 von November 21., 2017
Background on GetHuman-429272's case
GetHuman: GetHuman-429272 - can you tell our other Bank of America customers when your case took place?
GetHuman-429272: Yeah. It was afternoon, on November 17..
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 GetHuman-429272 a list of common Bank of America problems)
GetHuman-429272: "Billing" was why I was trying to call.
GetHuman-429272'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.
GetHuman-429272: never talked to a human. system repeatedly tried to solve the problem with options. call eventually disconnected.
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?
GetHuman-429272: 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?
GetHuman-429272: I'd give them a five out of five on communication.
GetHuman: And what about Bank of America's ability to quickly and effectively address your problem?
GetHuman-429272: For that I would say four out of five.
GetHuman: And finally- any advice for other Bank of America customers?
GetHuman-429272: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Bank of America weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-429272 taken from his Bank of America customer service problem that occurred on November 17., 2017.