Wells Fargo: Trying to make a deposit at the branch using ac...
Eine Wells Fargo Kundenbewertung durch GetHuman-Benutzer ~JM_StPete von November 27., 2017
Background on ~JM_StPete's case
GetHuman: ~JM_StPete - can you tell our other Wells Fargo customers when your case took place?
~JM_StPete: Yes. It was afternoon, on November 23..
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 ~JM_StPete a list of common Wells Fargo problems)
~JM_StPete: "Statement Request" was why I was trying to call.
~JM_StPete'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.
~JM_StPete: Trying to make a deposit at the branch using account name, address and phone number. Refused and demanded full account number. All other banks can but WF can't. Do NOT bank with these guys. Waste of time, money and too much frustration.
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?
~JM_StPete: 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?
~JM_StPete: 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?
~JM_StPete: For that I would say one out of five.
GetHuman: And finally- any advice for other Wells Fargo customers?
~JM_StPete: 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 ~JM_StPete taken from his Wells Fargo customer service problem that occurred on November 23., 2017.