Great West Health: This tip worked for reaching a human, but the p...
A Great West Health customer review by GetHuman user ~rotomonkey from October 27th, 2017
Background on ~rotomonkey's case
GetHuman: ~rotomonkey - can you tell our other Great West Health customers when your case took place?
~rotomonkey: Yes I can. It was middle of the night, on October 21st.
GetHuman: Did you reach out to Great West Health, and if so, how?
GetHuman: And which of these common Great West Health customer issues best describes the reason you wanted to talk to them?
(Shows ~rotomonkey a list of common Great West Health problems)
~rotomonkey: "Get insurance" was why I was trying to call.
~rotomonkey's review of Great West Health customer service
GetHuman: So how would you sum up your experience for GetHuman's Great West Health 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.
~rotomonkey: This tip worked for reaching a human, but the person I reached asked me how I got this number then put me on hold to transfer me to another number.
GetHuman: Let's quantify your experience contacting Great West Health. On a scale of 1 to 5, how easy is it go get help on a Great West Health problem?
~rotomonkey: 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?
~rotomonkey: I'd give them a three out of five on communication.
GetHuman: And what about Great West Health's ability to quickly and effectively address your problem?
~rotomonkey: For that I would say four out of five.
GetHuman: And finally- any advice for other Great West Health customers?
~rotomonkey: Call them early in the day or late. Don't forget any personal or account information you might need for Great West Health to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~rotomonkey taken from his Great West Health customer service problem that occurred on October 21st, 2017.