Wells Fargo: Agent words were scripted, had a friendly tone...
A Wells Fargo customer review by GetHuman user ~stephanielee869 from November 4th, 2017
Background on ~stephanielee869's case
GetHuman: ~stephanielee869 - can you tell our other Wells Fargo customers when your case took place?
~stephanielee869: Sure. It was middle of the night, on October 27th.
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 ~stephanielee869 a list of common Wells Fargo problems)
~stephanielee869: "Overcharge on Account" was why I was trying to call.
~stephanielee869'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.
~stephanielee869: Agent words were scripted, had a friendly tone but didn*€*t make an effort to connect. Was very educational and made sure she had her information straight when she gave it to me.
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?
~stephanielee869: 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?
~stephanielee869: I'd give them a four out of five on communication.
GetHuman: And what about Wells Fargo's ability to quickly and effectively address your problem?
~stephanielee869: For that I would say three out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
~stephanielee869: 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 ~stephanielee869 taken from his Wells Fargo customer service problem that occurred on October 27th, 2017.