Farmer's Insurance: they were quick to answer my call and had all t...
A Farmer's Insurance customer review by GetHuman user ~Dragon_Billy from November 20th, 2017
Background on ~Dragon_Billy's case
GetHuman: ~Dragon_Billy - can you tell our other Farmer's Insurance customers when your case took place?
~Dragon_Billy: Yeah. It was afternoon, on November 17th.
GetHuman: Did you reach out to Farmer's Insurance, and if so, how?
GetHuman: And which of these common Farmer's Insurance customer issues best describes the reason you wanted to talk to them?
(Shows ~Dragon_Billy a list of common Farmer's Insurance problems)
~Dragon_Billy: "Update account information" was why I was trying to call.
~Dragon_Billy's review of Farmer's Insurance customer service
GetHuman: So how would you sum up your experience for GetHuman's Farmer's Insurance 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.
~Dragon_Billy: they were quick to answer my call and had all the answers I needed. They were very friendly and professional.
GetHuman: Let's quantify your experience contacting Farmer's Insurance. On a scale of 1 to 5, how easy is it go get help on a Farmer's Insurance problem?
~Dragon_Billy: I'd give them a one 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?
~Dragon_Billy: I'd give them a four out of five on communication.
GetHuman: And what about Farmer's Insurance's ability to quickly and effectively address your problem?
~Dragon_Billy: For that I would say one out of five.
GetHuman: And finally- any advice for other Farmer's Insurance customers?
~Dragon_Billy: Call them early in the day or late. Don't forget any personal or account information you might need for Farmer's Insurance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Dragon_Billy taken from his Farmer's Insurance customer service problem that occurred on November 17th, 2017.