Lulu.com: * persons to talk to to fix my problem. NO phon...
A Lulu.com customer review by GetHuman user GetHuman-250864 from November 21st, 2017
Background on GetHuman-250864's case
GetHuman: GetHuman-250864 - can you tell our other Lulu.com customers when your case took place?
GetHuman-250864: Yes. It was middle of the night, on November 13th.
GetHuman: Did you reach out to Lulu.com, and if so, how?
GetHuman: And which of these common Lulu.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-250864 a list of common Lulu.com problems)
GetHuman-250864: "Cancel order" was why I was trying to contact.
GetHuman-250864's review of Lulu.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Lulu.com 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-250864: * persons to talk to to fix my problem. NO phone number. No chat. No support. Zip. This will be my last dealing with this company. Buyer beware. They make the mistake* you get stuck with it with no immediate recourse.
GetHuman: Let's quantify your experience contacting Lulu.com. On a scale of 1 to 5, how easy is it go get help on a Lulu.com problem?
GetHuman-250864: 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?
GetHuman-250864: I'd give them a three out of five on communication.
GetHuman: And what about Lulu.com's ability to quickly and effectively address your problem?
GetHuman-250864: For that I would say two out of five.
GetHuman: And finally- any advice for other Lulu.com customers?
GetHuman-250864: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Lulu.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-250864 taken from his Lulu.com customer service problem that occurred on November 13th, 2017.