Wells Fargo: Once the automated response picked up the call...
A Wells Fargo customer review by GetHuman user ~rn1256 from November 16th, 2017
Background on ~rn1256's case
GetHuman: ~rn1256 - can you tell our other Wells Fargo customers when your case took place?
~rn1256: Yeah. It was evening, on November 7th.
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 ~rn1256 a list of common Wells Fargo problems)
~rn1256: "Statement Request" was why I was trying to call.
~rn1256'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.
~rn1256: Once the automated response picked up the call i did not answer their questions that led me to banker response.
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?
~rn1256: I'd give them a two 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?
~rn1256: I'd give them a five out of five on communication.
GetHuman: And what about Wells Fargo's ability to quickly and effectively address your problem?
~rn1256: For that I would say one out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
~rn1256: 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 ~rn1256 taken from his Wells Fargo customer service problem that occurred on November 7th, 2017.