LA Fitness: Have to mail in cancellation app or visit local...
A LA Fitness customer review by GetHuman user GetHuman-78793 from November 25th, 2017
Background on GetHuman-78793's case
GetHuman: GetHuman-78793 - can you tell our other LA Fitness customers when your case took place?
GetHuman-78793: Yup. It was middle of the night, on November 21st.
GetHuman: Did you reach out to LA Fitness, and if so, how?
GetHuman: And which of these common LA Fitness customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-78793 a list of common LA Fitness problems)
GetHuman-78793: "Setup Service" was why I was trying to call.
GetHuman-78793's review of LA Fitness customer service
GetHuman: So how would you sum up your experience for GetHuman's LA 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.
GetHuman-78793: Have to mail in cancellation app or visit local locations to see the one operational manager to cancel?? And the manager took a leave for * days in a roll...Is that the competitive landscape in fitness sector?
GetHuman: Let's quantify your experience contacting LA Fitness. On a scale of 1 to 5, how easy is it go get help on a LA Fitness problem?
GetHuman-78793: 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?
GetHuman-78793: I'd give them a four out of five on communication.
GetHuman: And what about LA Fitness's ability to quickly and effectively address your problem?
GetHuman-78793: For that I would say five out of five.
GetHuman: And finally- any advice for other LA Fitness customers?
GetHuman-78793: Call them early in the day or late. Don't forget any personal or account information you might need for LA Fitness to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-78793 taken from his LA Fitness customer service problem that occurred on November 21st, 2017.