Fifth Third Bank: Unfortunately, it was the checking and savings...
A Fifth Third Bank customer review by GetHuman user ~Anon E Mouse from November 11th, 2017
Background on ~Anon E Mouse's case
GetHuman: ~Anon E Mouse - can you tell our other Fifth Third Bank customers when your case took place?
~Anon E Mouse: Yes. It was afternoon, on November 8th.
GetHuman: Did you reach out to Fifth Third Bank, and if so, how?
GetHuman: And which of these common Fifth Third Bank customer issues best describes the reason you wanted to talk to them?
(Shows ~Anon E Mouse a list of common Fifth Third Bank problems)
~Anon E Mouse: "Account Access" was why I was trying to call.
~Anon E Mouse's review of Fifth Third Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's Fifth Third Bank 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.
~Anon E Mouse: Unfortunately, it was the checking and savings acct line, and I needed car loans. But she transferred me to another human, who answered within * minutes.
GetHuman: Let's quantify your experience contacting Fifth Third Bank. On a scale of 1 to 5, how easy is it go get help on a Fifth Third Bank problem?
~Anon E Mouse: 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?
~Anon E Mouse: I'd give them a one out of five on communication.
GetHuman: And what about Fifth Third Bank's ability to quickly and effectively address your problem?
~Anon E Mouse: For that I would say one out of five.
GetHuman: And finally- any advice for other Fifth Third Bank customers?
~Anon E Mouse: Call them early in the day or late. Don't forget any personal or account information you might need for Fifth Third Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anon E Mouse taken from his Fifth Third Bank customer service problem that occurred on November 8th, 2017.