Commonwealth Choice: Comm Choice told me a year ago (April ****) tha...
A Commonwealth Choice customer review by GetHuman user ~Joe from November 9th, 2017
Background on ~Joe's case
GetHuman: ~Joe - can you tell our other Commonwealth Choice customers when your case took place?
~Joe: Yup. It was middle of the night, on November 4th.
GetHuman: Did you reach out to Commonwealth Choice, and if so, how?
GetHuman: And which of these common Commonwealth Choice customer issues best describes the reason you wanted to talk to them?
(Shows ~Joe a list of common Commonwealth Choice problems)
~Joe: "Update account information" was why I was trying to call.
~Joe's review of Commonwealth Choice customer service
GetHuman: So how would you sum up your experience for GetHuman's Commonwealth Choice 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.
~Joe: Comm Choice told me a year ago (April ****) that my rate is going up in May ****. I called several times, including today March *, and they still won*t tell me what my new rate will be. Highly unprofessional.
GetHuman: Let's quantify your experience contacting Commonwealth Choice. On a scale of 1 to 5, how easy is it go get help on a Commonwealth Choice problem?
~Joe: 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?
~Joe: I'd give them a one out of five on communication.
GetHuman: And what about Commonwealth Choice's ability to quickly and effectively address your problem?
~Joe: For that I would say one out of five.
GetHuman: And finally- any advice for other Commonwealth Choice customers?
~Joe: Call them early in the day or late. Don't forget any personal or account information you might need for Commonwealth Choice to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Joe taken from his Commonwealth Choice customer service problem that occurred on November 4th, 2017.