Safeco Insurance: RUN AWAY FROM SAFECO.THEY ARE NOT DEPENDABLE, N...
A Safeco Insurance customer review by GetHuman user GetHuman-427722 from November 22nd, 2017
Background on GetHuman-427722's case
GetHuman: GetHuman-427722 - can you tell our other Safeco Insurance customers when your case took place?
GetHuman-427722: Yeah. It was afternoon, on November 17th.
GetHuman: Did you reach out to Safeco Insurance, and if so, how?
GetHuman: And which of these common Safeco Insurance customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-427722 a list of common Safeco Insurance problems)
GetHuman-427722: "Update account information" was why I was trying to call.
GetHuman-427722's review of Safeco Insurance customer service
GetHuman: So how would you sum up your experience for GetHuman's Safeco 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.
GetHuman-427722: RUN AWAY FROM SAFECO.THEY ARE NOT DEPENDABLE, NOT RELIABLE , AND THEY ARE DECEIVERS IN THEIR CLAIMS. DON'T USE THEM!!!!!
GetHuman: Let's quantify your experience contacting Safeco Insurance. On a scale of 1 to 5, how easy is it go get help on a Safeco Insurance problem?
GetHuman-427722: I'd give them a four 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-427722: I'd give them a one out of five on communication.
GetHuman: And what about Safeco Insurance's ability to quickly and effectively address your problem?
GetHuman-427722: For that I would say five out of five.
GetHuman: And finally- any advice for other Safeco Insurance customers?
GetHuman-427722: Call them early in the day or late. Don't forget any personal or account information you might need for Safeco Insurance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-427722 taken from his Safeco Insurance customer service problem that occurred on November 17th, 2017.