Wells Fargo: Immediately got an automated line, went through...
Eine Wells Fargo Kundenbewertung durch GetHuman-Benutzer GetHuman-401846 von November 18., 2017
Background on GetHuman-401846's case
GetHuman: GetHuman-401846 - can you tell our other Wells Fargo customers when your case took place?
GetHuman-401846: Sure. It was morning, on November 14..
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-401846 a list of common Wells Fargo problems)
GetHuman-401846: "Complaint" was why I was trying to call.
GetHuman-401846'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-401846: Immediately got an automated line, went through * phases before getting a person. Individual has transferred me twice and am now speaking with an foreign outsourced call center.
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-401846: 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-401846: 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-401846: For that I would say one out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
GetHuman-401846: 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 GetHuman-401846 taken from his Wells Fargo customer service problem that occurred on November 14., 2017.