24 Hour Fitness: terrible... called three times and each t...
A 24 Hour Fitness customer review by GetHuman user ~ #24hrfitnessux from November 18th, 2017
Background on ~ #24hrfitnessux's case
GetHuman: ~ #24hrfitnessux - can you tell our other 24 Hour Fitness customers when your case took place?
~ #24hrfitnessux: Sure. It was evening, on November 14th.
GetHuman: Did you reach out to 24 Hour Fitness, and if so, how?
GetHuman: And which of these common 24 Hour Fitness customer issues best describes the reason you wanted to talk to them?
(Shows ~ #24hrfitnessux a list of common 24 Hour Fitness problems)
~ #24hrfitnessux: "Cancel membership" was why I was trying to call.
~ #24hrfitnessux's review of 24 Hour Fitness customer service
GetHuman: So how would you sum up your experience for GetHuman's 24 Hour Fitness 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.
~ #24hrfitnessux: terrible... called three times and each time the rep seemingly pretended to not be able to hear me after I said I would like to cancel.
GetHuman: Let's quantify your experience contacting 24 Hour Fitness. On a scale of 1 to 5, how easy is it go get help on a 24 Hour Fitness problem?
~ #24hrfitnessux: 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?
~ #24hrfitnessux: I'd give them a four out of five on communication.
GetHuman: And what about 24 Hour Fitness's ability to quickly and effectively address your problem?
~ #24hrfitnessux: For that I would say five out of five.
GetHuman: And finally- any advice for other 24 Hour Fitness customers?
~ #24hrfitnessux: Call them early in the day or late. Don't forget any personal or account information you might need for 24 Hour Fitness to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ #24hrfitnessux taken from his 24 Hour Fitness customer service problem that occurred on November 14th, 2017.