Fifth Third Bank: absolutely horrible. waited and waited. dsconne...
A Fifth Third Bank customer review by GetHuman user GetHuman-321726 from November 28th, 2017
Background on GetHuman-321726's case
GetHuman: GetHuman-321726 - can you tell our other Fifth Third Bank customers when your case took place?
GetHuman-321726: Sure. It was middle of the night, on November 24th.
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 GetHuman-321726 a list of common Fifth Third Bank problems)
GetHuman-321726: "Replacement Card" was why I was trying to call.
GetHuman-321726'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.
GetHuman-321726: absolutely horrible. waited and waited. dsconnected. sent to wrong departments. No one knows how to find any
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?
GetHuman-321726: I'd give them a one 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-321726: I'd give them a two out of five on communication.
GetHuman: And what about Fifth Third Bank's ability to quickly and effectively address your problem?
GetHuman-321726: For that I would say five out of five.
GetHuman: And finally- any advice for other Fifth Third Bank customers?
GetHuman-321726: 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 GetHuman-321726 taken from his Fifth Third Bank customer service problem that occurred on November 24th, 2017.