Progressive Insurance: I LOVE PROGRESSIVE STAFF ALWAYS VERY FRIENDLY T...
Progressive Insurance Ulasan pelanggan oleh pengguna GetHuman ~CEE CEE dari November 27, 2017
Background on ~CEE CEE's case
GetHuman: ~CEE CEE - can you tell our other Progressive Insurance customers when your case took place?
~CEE CEE: Yup. It was afternoon, on November 25.
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 ~CEE CEE a list of common Progressive Insurance problems)
~CEE CEE: "Overcharge/Strange charge" was why I was trying to call.
~CEE CEE'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.
~CEE CEE: I LOVE PROGRESSIVE STAFF ALWAYS VERY FRIENDLY THEY DO A VERY GOOD JOB AND I THINK I WILL BE WITH THEM FOR A VERY LONG TIME!!
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?
~CEE CEE: 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?
~CEE CEE: 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?
~CEE CEE: For that I would say five out of five.
GetHuman: And finally- any advice for other Progressive Insurance customers?
~CEE CEE: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Progressive Insurance mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~CEE CEE taken from his Progressive Insurance customer service problem that occurred on November 25, 2017.