The Work Number: The representative on the phone gave me the bes...
A The Work Number customer review by GetHuman user ~wannie from November 22nd, 2017
Background on ~wannie's case
GetHuman: ~wannie - can you tell our other The Work Number customers when your case took place?
~wannie: Yeah. It was middle of the night, on November 13th.
GetHuman: Did you reach out to The Work Number, and if so, how?
GetHuman: And which of these common The Work Number customer issues best describes the reason you wanted to talk to them?
(Shows ~wannie a list of common The Work Number problems)
~wannie: "Overcharge/Strange charge" was why I was trying to call.
~wannie's review of The Work Number customer service
GetHuman: So how would you sum up your experience for GetHuman's The Work Number 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.
~wannie: The representative on the phone gave me the best service he could, the problem was more so with WN's system of managing and updating information and providing direct customer service instead of automated message menu's.
GetHuman: Let's quantify your experience contacting The Work Number. On a scale of 1 to 5, how easy is it go get help on a The Work Number problem?
~wannie: I'd give them a three 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?
~wannie: I'd give them a one out of five on communication.
GetHuman: And what about The Work Number's ability to quickly and effectively address your problem?
~wannie: For that I would say three out of five.
GetHuman: And finally- any advice for other The Work Number customers?
~wannie: Call them early in the day or late. Don't forget any personal or account information you might need for The Work Number to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~wannie taken from his The Work Number customer service problem that occurred on November 13th, 2017.