LA Fitness: I had a problem trying to cancel my seation wit...
A LA Fitness customer review by GetHuman user ~Mimi from November 16th, 2017
Background on ~Mimi's case
GetHuman: ~Mimi - can you tell our other LA Fitness customers when your case took place?
~Mimi: Sure. It was afternoon, on November 7th.
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 ~Mimi a list of common LA Fitness problems)
~Mimi: "Setup Service" was why I was trying to call.
~Mimi'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.
~Mimi: I had a problem trying to cancel my seation with personal trainer,, at the sit at AL, fitness,, the manger was not helpful to help me cancel or to give me some kind of *-***,,,* to call,, I went home google it. As soon as I call this * Bruce helped me solve it!! Thx much you made Ma day for most u save me from canceling the member-ship!!
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?
~Mimi: I'd give them a four 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?
~Mimi: I'd give them a five out of five on communication.
GetHuman: And what about LA Fitness's ability to quickly and effectively address your problem?
~Mimi: For that I would say two out of five.
GetHuman: And finally- any advice for other LA Fitness customers?
~Mimi: 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 ~Mimi taken from his LA Fitness customer service problem that occurred on November 7th, 2017.