Ford Motor Credit: Asked for a signed and dated Release of Lien on...
A Ford Motor Credit customer review by GetHuman user GetHuman-253252 from November 20th, 2017
Background on GetHuman-253252's case
GetHuman: GetHuman-253252 - can you tell our other Ford Motor Credit customers when your case took place?
GetHuman-253252: Yeah. It was late at night, on November 14th.
GetHuman: Did you reach out to Ford Motor Credit, and if so, how?
GetHuman: And which of these common Ford Motor Credit customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-253252 a list of common Ford Motor Credit problems)
GetHuman-253252: "Request a loan" was why I was trying to call.
GetHuman-253252's review of Ford Motor Credit customer service
GetHuman: So how would you sum up your experience for GetHuman's Ford Motor Credit 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-253252: Asked for a signed and dated Release of Lien on a vehicle that has been paid off for more than * years.
GetHuman: Let's quantify your experience contacting Ford Motor Credit. On a scale of 1 to 5, how easy is it go get help on a Ford Motor Credit problem?
GetHuman-253252: 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-253252: I'd give them a five out of five on communication.
GetHuman: And what about Ford Motor Credit's ability to quickly and effectively address your problem?
GetHuman-253252: For that I would say five out of five.
GetHuman: And finally- any advice for other Ford Motor Credit customers?
GetHuman-253252: Call them early in the day or late. Don't forget any personal or account information you might need for Ford Motor Credit to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-253252 taken from his Ford Motor Credit customer service problem that occurred on November 14th, 2017.