GameFly: The "live" assistant gave automated answers tha...
A GameFly customer review by GetHuman user GetHuman-435228 from November 26th, 2017
Background on GetHuman-435228's case
GetHuman: GetHuman-435228 - can you tell our other GameFly customers when your case took place?
GetHuman-435228: Yup. It was morning, on November 24th.
GetHuman: Did you reach out to GameFly, and if so, how?
GetHuman: And which of these common GameFly customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-435228 a list of common GameFly problems)
GetHuman-435228: "Complaint" was why I was trying to call.
GetHuman-435228's review of GameFly customer service
GetHuman: So how would you sum up your experience for GetHuman's GameFly 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-435228: The "live" assistant gave automated answers that were entirely unhelpful. Had the person actually read my complaint she would have known that the answers she gave were useless. Plus, as I was typing out a reply she ended the conversation with me. Thanks GameFly!
GetHuman: Let's quantify your experience contacting GameFly. On a scale of 1 to 5, how easy is it go get help on a GameFly problem?
GetHuman-435228: 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-435228: I'd give them a five out of five on communication.
GetHuman: And what about GameFly's ability to quickly and effectively address your problem?
GetHuman-435228: For that I would say five out of five.
GetHuman: And finally- any advice for other GameFly customers?
GetHuman-435228: Call them early in the day or late. Don't forget any personal or account information you might need for GameFly to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-435228 taken from his GameFly customer service problem that occurred on November 24th, 2017.