Lululemon: to complain about your products not wearing we...
A Lululemon customer review by GetHuman user GetHuman58609 from December 8th, 2017
Background on GetHuman58609's case
GetHuman: GetHuman58609 - can you tell our other Lululemon customers when your case took place?
GetHuman58609: Sure. It was evening, on November 29th.
GetHuman: Did you reach out to Lululemon, and if so, how?
GetHuman: And which of these common Lululemon customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman58609 a list of common Lululemon problems)
GetHuman58609: "Returns" was why I was trying to call.
GetHuman58609's review of Lululemon customer service
GetHuman: So how would you sum up your experience for GetHuman's Lululemon 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.
GetHuman58609: to complain about your products not wearing well and wish a replacement
GetHuman: Can you tell the rest of us a bit more from what happened on 11/29/17?
GetHuman58609: excessive pilling on shirts, jacket and pants that have lost its shape and look like a rag
GetHuman: Let's quantify your experience contacting Lululemon. On a scale of 1 to 5, how easy is it go get help on a Lululemon problem?
GetHuman58609: I'd give them a one 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?
GetHuman58609: I'd give them a four out of five on communication.
GetHuman: And what about Lululemon's ability to quickly and effectively address your problem?
GetHuman58609: For that I would say one out of five.
GetHuman: And finally- any advice for other Lululemon customers?
GetHuman58609: Call them early in the day or late. Don't forget any personal or account information you might need for Lululemon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman58609 taken from his Lululemon customer service problem that occurred on November 29th, 2017.