Wells Fargo Home Mortgages: This number got me to a human fast and helped r...
A Wells Fargo Home Mortgages customer review by GetHuman user ~Pay Toll from November 22nd, 2017
Background on ~Pay Toll's case
GetHuman: ~Pay Toll - can you tell our other Wells Fargo Home Mortgages customers when your case took place?
~Pay Toll: Yes. It was afternoon, on November 12th.
GetHuman: Did you reach out to Wells Fargo Home Mortgages, and if so, how?
GetHuman: And which of these common Wells Fargo Home Mortgages customer issues best describes the reason you wanted to talk to them?
(Shows ~Pay Toll a list of common Wells Fargo Home Mortgages problems)
~Pay Toll: "Overcharge/Strange charge" was why I was trying to call.
~Pay Toll's review of Wells Fargo Home Mortgages customer service
GetHuman: So how would you sum up your experience for GetHuman's Wells Fargo Home Mortgages 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.
~Pay Toll: This number got me to a human fast and helped right away
GetHuman: Let's quantify your experience contacting Wells Fargo Home Mortgages. On a scale of 1 to 5, how easy is it go get help on a Wells Fargo Home Mortgages problem?
~Pay Toll: I'd give them a five 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?
~Pay Toll: I'd give them a two out of five on communication.
GetHuman: And what about Wells Fargo Home Mortgages's ability to quickly and effectively address your problem?
~Pay Toll: For that I would say five out of five.
GetHuman: And finally- any advice for other Wells Fargo Home Mortgages customers?
~Pay Toll: Call them early in the day or late. Don't forget any personal or account information you might need for Wells Fargo Home Mortgages to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Pay Toll taken from his Wells Fargo Home Mortgages customer service problem that occurred on November 12th, 2017.