Wells Fargo: Communication was very robotic, provided no hel...
Eine Wells Fargo Kundenbewertung durch GetHuman-Benutzer ~anonymous von November 23., 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Wells Fargo customers when your case took place?
~anonymous: Yes I can. It was late at night, on November 18..
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 ~anonymous a list of common Wells Fargo problems)
~anonymous: "Overcharge on Account" was why I was trying to call.
~anonymous'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.
~anonymous: Communication was very robotic, provided no help, and thanked me for calling Wells Fargo. The whole thing took two minutes and by the way, he added that "the system is currently down." Totally worthless call.
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?
~anonymous: 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?
~anonymous: I'd give them a two out of five on communication.
GetHuman: And what about Wells Fargo's ability to quickly and effectively address your problem?
~anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
~anonymous: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Wells Fargo weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Wells Fargo customer service problem that occurred on November 18., 2017.