Wells Fargo: Well went n bank With a good attitude came out...
A Wells Fargo customer review by GetHuman user GetHuman-107792 from November 17th, 2017
Background on GetHuman-107792's case
GetHuman: GetHuman-107792 - can you tell our other Wells Fargo customers when your case took place?
GetHuman-107792: Yeah. It was evening, on November 12th.
GetHuman: Did you reach out to Wells Fargo, and if so, how?
GetHuman: And which of these common Wells Fargo customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-107792 a list of common Wells Fargo problems)
GetHuman-107792: "Statement Request" was why I was trying to call.
GetHuman-107792's review of Wells Fargo customer service
GetHuman: So how would you sum up your experience for GetHuman's Wells Fargo 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-107792: Well went n bank With a good attitude came out pissed off The bank teller an her attitude sucked I had to ask * times for balance after deposit If she don't lik femalecustomers why work their
GetHuman: Let's quantify your experience contacting Wells Fargo. On a scale of 1 to 5, how easy is it go get help on a Wells Fargo problem?
GetHuman-107792: I'd give them a three 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-107792: I'd give them a one out of five on communication.
GetHuman: And what about Wells Fargo's ability to quickly and effectively address your problem?
GetHuman-107792: For that I would say five out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
GetHuman-107792: Call them early in the day or late. Don't forget any personal or account information you might need for Wells Fargo to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-107792 taken from his Wells Fargo customer service problem that occurred on November 12th, 2017.