Ford: I was lied to several times by Shane Hanna*At D...
A Ford customer review by GetHuman user ~Ragena Combs from November 16th, 2017
Background on ~Ragena Combs's case
GetHuman: ~Ragena Combs - can you tell our other Ford customers when your case took place?
~Ragena Combs: Sure. It was afternoon, on November 15th.
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 ~Ragena Combs a list of common Ford problems)
~Ragena Combs: "Repairs" was why I was trying to call.
~Ragena Combs'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.
~Ragena Combs: I was lied to several times by Shane Hanna*At Don Vance Ford in Marshfield, MO, regarding two rebates I qualified for. Here it is * months after purchasing my vehicle and I still don't have either one of them!!*Finally called Ford Customer service and was treated very good. I hope they will finally get me my rebates!!!!!
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?
~Ragena Combs: 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?
~Ragena Combs: I'd give them a two out of five on communication.
GetHuman: And what about Ford's ability to quickly and effectively address your problem?
~Ragena Combs: For that I would say three out of five.
GetHuman: And finally- any advice for other Ford customers?
~Ragena Combs: 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 ~Ragena Combs taken from his Ford customer service problem that occurred on November 15th, 2017.