Bank of America Credit: debe haber una comunicacion mas directa con los...
A Bank of America Credit customer review by GetHuman user ~Guillermo from November 24th, 2017
Background on ~Guillermo's case
GetHuman: ~Guillermo - can you tell our other Bank of America Credit customers when your case took place?
~Guillermo: Yup. It was evening, on November 15th.
GetHuman: Did you reach out to Bank of America Credit, and if so, how?
GetHuman: And which of these common Bank of America Credit customer issues best describes the reason you wanted to talk to them?
(Shows ~Guillermo a list of common Bank of America Credit problems)
~Guillermo: "Complaint" was why I was trying to call.
~Guillermo's review of Bank of America Credit customer service
GetHuman: So how would you sum up your experience for GetHuman's Bank of America Credit 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.
~Guillermo: debe haber una comunicacion mas directa con los clientes que tienen sus cuentas y estan por fuera de los EE UU
GetHuman: Let's quantify your experience contacting Bank of America Credit. On a scale of 1 to 5, how easy is it go get help on a Bank of America Credit problem?
~Guillermo: 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?
~Guillermo: I'd give them a three out of five on communication.
GetHuman: And what about Bank of America Credit's ability to quickly and effectively address your problem?
~Guillermo: For that I would say four out of five.
GetHuman: And finally- any advice for other Bank of America Credit customers?
~Guillermo: Call them early in the day or late. Don't forget any personal or account information you might need for Bank of America Credit to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Guillermo taken from his Bank of America Credit customer service problem that occurred on November 15th, 2017.