Valve Software: And it's actually * days, not ** minutes.*Took...
A Valve Software customer review by GetHuman user GetHuman-198186 from November 14th, 2017
Background on GetHuman-198186's case
GetHuman: GetHuman-198186 - can you tell our other Valve Software customers when your case took place?
GetHuman-198186: Sure. It was evening, on November 5th.
GetHuman: Did you reach out to Valve Software, and if so, how?
GetHuman: And which of these common Valve Software customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-198186 a list of common Valve Software problems)
GetHuman-198186: "Complaint" was why I was trying to call.
GetHuman-198186's review of Valve Software customer service
GetHuman: So how would you sum up your experience for GetHuman's Valve Software 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-198186: And it's actually * days, not ** minutes.*Took me * messages to get a clear answer out of the representative. And a couple weeks later I found out that his answer was wrong.
GetHuman: Let's quantify your experience contacting Valve Software. On a scale of 1 to 5, how easy is it go get help on a Valve Software problem?
GetHuman-198186: 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-198186: I'd give them a one out of five on communication.
GetHuman: And what about Valve Software's ability to quickly and effectively address your problem?
GetHuman-198186: For that I would say two out of five.
GetHuman: And finally- any advice for other Valve Software customers?
GetHuman-198186: Call them early in the day or late. Don't forget any personal or account information you might need for Valve Software to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-198186 taken from his Valve Software customer service problem that occurred on November 5th, 2017.