LA Fitness: I moved *** miles away. I was told by the VP...
A LA Fitness customer review by GetHuman user ~Anonymous TX from November 27th, 2017
Background on ~Anonymous TX's case
GetHuman: ~Anonymous TX - can you tell our other LA Fitness customers when your case took place?
~Anonymous TX: Sure. It was morning, 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 ~Anonymous TX a list of common LA Fitness problems)
~Anonymous TX: "Update Account Information" was why I was trying to call.
~Anonymous TX'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.
~Anonymous TX: I moved *** miles away. I was told by the VP - Jay Ramirez that I could get a **% buyout. It has been ** days and many outbound phone calls to that location and no termination. It is near impossible to get out of this ****.
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?
~Anonymous TX: 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?
~Anonymous TX: 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?
~Anonymous TX: For that I would say five out of five.
GetHuman: And finally- any advice for other LA Fitness customers?
~Anonymous TX: 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 ~Anonymous TX taken from his LA Fitness customer service problem that occurred on November 21st, 2017.