W-2 eXpress: ** min of hold time and finally gave up- i wond...
A W-2 eXpress customer review by GetHuman user GetHuman-409629 from November 3rd, 2017
Background on GetHuman-409629's case
GetHuman: GetHuman-409629 - can you tell our other W-2 eXpress customers when your case took place?
GetHuman-409629: Yes. It was morning, on October 26th.
GetHuman: Did you reach out to W-2 eXpress, and if so, how?
GetHuman: And which of these common W-2 eXpress customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-409629 a list of common W-2 eXpress problems)
GetHuman-409629: "None of those really matches why I wanted to call W-2 eXpress that day." was why I was trying to call.
GetHuman-409629's review of W-2 eXpress customer service
GetHuman: So how would you sum up your experience for GetHuman's W-2 eXpress 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-409629: ** min of hold time and finally gave up- i wonder if companies are really saving money by doing this when employees are spending time on hold
GetHuman: Let's quantify your experience contacting W-2 eXpress. On a scale of 1 to 5, how easy is it go get help on a W-2 eXpress problem?
GetHuman-409629: 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?
GetHuman-409629: I'd give them a one out of five on communication.
GetHuman: And what about W-2 eXpress's ability to quickly and effectively address your problem?
GetHuman-409629: For that I would say four out of five.
GetHuman: And finally- any advice for other W-2 eXpress customers?
GetHuman-409629: Call them early in the day or late. Don't forget any personal or account information you might need for W-2 eXpress to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-409629 taken from his W-2 eXpress customer service problem that occurred on October 26th, 2017.