WageWorks: cust serv rep was thorough in explanation altho...
A WageWorks customer review by GetHuman user GetHuman-363053 from November 19th, 2017
Background on GetHuman-363053's case
GetHuman: GetHuman-363053 - can you tell our other WageWorks customers when your case took place?
GetHuman-363053: Yup. It was morning, on November 14th.
GetHuman: Did you reach out to WageWorks, and if so, how?
GetHuman: And which of these common WageWorks customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-363053 a list of common WageWorks problems)
GetHuman-363053: "Coverage question" was why I was trying to call.
GetHuman-363053's review of WageWorks customer service
GetHuman: So how would you sum up your experience for GetHuman's WageWorks 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-363053: cust serv rep was thorough in explanation although I did NOT like the answer to my question: Do I have to have a DOCTORS PRESCRIPTION for my OTC needs? Answer was YES.RIDICULOUS but it's not WageWorks, IT'S THE IRS!!! ABSURD!
GetHuman: Let's quantify your experience contacting WageWorks. On a scale of 1 to 5, how easy is it go get help on a WageWorks problem?
GetHuman-363053: 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?
GetHuman-363053: I'd give them a one out of five on communication.
GetHuman: And what about WageWorks's ability to quickly and effectively address your problem?
GetHuman-363053: For that I would say one out of five.
GetHuman: And finally- any advice for other WageWorks customers?
GetHuman-363053: Call them early in the day or late. Don't forget any personal or account information you might need for WageWorks to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-363053 taken from his WageWorks customer service problem that occurred on November 14th, 2017.