Limoges Jewelry: I could barely understand either person I talke...
A Limoges Jewelry customer review by GetHuman user GetHuman-326798 from November 8th, 2017
Background on GetHuman-326798's case
GetHuman: GetHuman-326798 - can you tell our other Limoges Jewelry customers when your case took place?
GetHuman-326798: Yup. It was morning, on November 4th.
GetHuman: Did you reach out to Limoges Jewelry, and if so, how?
GetHuman: And which of these common Limoges Jewelry customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-326798 a list of common Limoges Jewelry problems)
GetHuman-326798: "Cancel order" was why I was trying to call.
GetHuman-326798's review of Limoges Jewelry customer service
GetHuman: So how would you sum up your experience for GetHuman's Limoges Jewelry 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-326798: I could barely understand either person I talked to at this company. They were not helpful and completely cancelled an order of mine without my knowledge.
GetHuman: Let's quantify your experience contacting Limoges Jewelry. On a scale of 1 to 5, how easy is it go get help on a Limoges Jewelry problem?
GetHuman-326798: I'd give them a two 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-326798: I'd give them a one out of five on communication.
GetHuman: And what about Limoges Jewelry's ability to quickly and effectively address your problem?
GetHuman-326798: For that I would say one out of five.
GetHuman: And finally- any advice for other Limoges Jewelry customers?
GetHuman-326798: Call them early in the day or late. Don't forget any personal or account information you might need for Limoges Jewelry to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-326798 taken from his Limoges Jewelry customer service problem that occurred on November 4th, 2017.