I have a **** Ford Escape with **,*** miles...
A Ford customer review by GetHuman user ~be from November 23rd, 2017
Background on ~be's case
GetHuman: ~be - can you tell our other Ford customers when your case took place?
~be: Yes I can. It was middle of the night, on November 17th.
GetHuman: Did you reach out to Ford, and if so, how?
GetHuman: And which of these common Ford customer issues best describes the reason you wanted to talk to them?
(Shows ~be a list of common Ford problems)
~be: "Complaint" was why I was trying to call.
~be's review of Ford customer service
GetHuman: So how would you sum up your experience for GetHuman's Ford 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.
~be: I have a **** Ford Escape with **,*** miles. * weeks ago my front brakes locked up dealership charged almost ***.** for this repair then after repairs made the ABS light came on. Dealership manager very nice and did not charge me for this repair (***). Now * weeks later car back at dealership for the THIRD WINDOW THAT THE REGULATOR HAS FAILED!!!!!. Hopefully FORD will step up to the plate and realize this is THEIR problem and fix it for FREE.
GetHuman: Let's quantify your experience contacting Ford. On a scale of 1 to 5, how easy is it go get help on a Ford problem?
~be: 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?
~be: I'd give them a five out of five on communication.
GetHuman: And what about Ford's ability to quickly and effectively address your problem?
~be: For that I would say four out of five.
GetHuman: And finally- any advice for other Ford customers?
~be: Call them early in the day or late. Don't forget any personal or account information you might need for Ford to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~be taken from his Ford customer service problem that occurred on November 17th, 2017.