Wells Fargo: they ****** me out of lots of monny and now bla...
Eine Wells Fargo Kundenbewertung durch GetHuman-Benutzer ~metoknow von November 24., 2017
Background on ~metoknow's case
GetHuman: ~metoknow - can you tell our other Wells Fargo customers when your case took place?
~metoknow: Yes. It was afternoon, on November 15..
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 ~metoknow a list of common Wells Fargo problems)
~metoknow: "Account Access" was why I was trying to call.
~metoknow'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.
~metoknow: they ****** me out of lots of monny and now blame me for there **** up during there merge and i spoke to others who have the same prob they will **** your account right from under you now i want my old bank back they help you instead of ******* you
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?
~metoknow: 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?
~metoknow: 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?
~metoknow: For that I would say four out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
~metoknow: 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 ~metoknow taken from his Wells Fargo customer service problem that occurred on November 15., 2017.