EyeMed Vision Care: The person I spoke to quickly answered all my q...
A EyeMed Vision Care customer review by GetHuman user GetHuman-45691 from November 24th, 2017
Background on GetHuman-45691's case
GetHuman: GetHuman-45691 - can you tell our other EyeMed Vision Care customers when your case took place?
GetHuman-45691: Sure. It was middle of the night, on November 23rd.
GetHuman: Did you reach out to EyeMed Vision Care, and if so, how?
GetHuman: And which of these common EyeMed Vision Care customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-45691 a list of common EyeMed Vision Care problems)
GetHuman-45691: "Complaint" was why I was trying to call.
GetHuman-45691's review of EyeMed Vision Care customer service
GetHuman: So how would you sum up your experience for GetHuman's EyeMed Vision Care 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-45691: The person I spoke to quickly answered all my questions. She was efficient & friendly. A joy to deal with!
GetHuman: Let's quantify your experience contacting EyeMed Vision Care. On a scale of 1 to 5, how easy is it go get help on a EyeMed Vision Care problem?
GetHuman-45691: I'd give them a five 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-45691: I'd give them a four out of five on communication.
GetHuman: And what about EyeMed Vision Care's ability to quickly and effectively address your problem?
GetHuman-45691: For that I would say five out of five.
GetHuman: And finally- any advice for other EyeMed Vision Care customers?
GetHuman-45691: Call them early in the day or late. Don't forget any personal or account information you might need for EyeMed Vision Care to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-45691 taken from his EyeMed Vision Care customer service problem that occurred on November 23rd, 2017.