Progressive Insurance: I waiting on the phone for twenty minutes and s...
A Progressive Insurance customer review by GetHuman user ~doc23456 from November 28th, 2017
Background on ~doc23456's case
GetHuman: ~doc23456 - can you tell our other Progressive Insurance customers when your case took place?
~doc23456: Yeah. It was middle of the night, on November 21st.
GetHuman: Did you reach out to Progressive Insurance, and if so, how?
GetHuman: And which of these common Progressive Insurance customer issues best describes the reason you wanted to talk to them?
(Shows ~doc23456 a list of common Progressive Insurance problems)
~doc23456: "Overcharge/Strange charge" was why I was trying to call.
~doc23456's review of Progressive Insurance customer service
GetHuman: So how would you sum up your experience for GetHuman's Progressive 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.
~doc23456: I waiting on the phone for twenty minutes and still didn't get a human so I could cancel my Automobile policy!
GetHuman: Let's quantify your experience contacting Progressive Insurance. On a scale of 1 to 5, how easy is it go get help on a Progressive Insurance problem?
~doc23456: 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?
~doc23456: I'd give them a three out of five on communication.
GetHuman: And what about Progressive Insurance's ability to quickly and effectively address your problem?
~doc23456: For that I would say two out of five.
GetHuman: And finally- any advice for other Progressive Insurance customers?
~doc23456: Call them early in the day or late. Don't forget any personal or account information you might need for Progressive Insurance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~doc23456 taken from his Progressive Insurance customer service problem that occurred on November 21st, 2017.