Spiegel: Will not respond to my e-mails. Cannot get thro...
A Spiegel customer review by GetHuman user GetHuman-230947 from November 6th, 2017
Background on GetHuman-230947's case
GetHuman: GetHuman-230947 - can you tell our other Spiegel customers when your case took place?
GetHuman-230947: Yeah. It was morning, on October 28th.
GetHuman: Did you reach out to Spiegel, and if so, how?
GetHuman: And which of these common Spiegel customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-230947 a list of common Spiegel problems)
GetHuman-230947: "Change order" was why I was trying to call.
GetHuman-230947's review of Spiegel customer service
GetHuman: So how would you sum up your experience for GetHuman's Spiegel 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-230947: Will not respond to my e-mails. Cannot get through to them on the phone. Won't answer or the circuits are all used. Can't find an address to write a letter. Would never order from Spiegle again!!!!!!! It could take months before my overcharges are solved.
GetHuman: Let's quantify your experience contacting Spiegel. On a scale of 1 to 5, how easy is it go get help on a Spiegel problem?
GetHuman-230947: 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?
GetHuman-230947: I'd give them a two out of five on communication.
GetHuman: And what about Spiegel's ability to quickly and effectively address your problem?
GetHuman-230947: For that I would say one out of five.
GetHuman: And finally- any advice for other Spiegel customers?
GetHuman-230947: Call them early in the day or late. Don't forget any personal or account information you might need for Spiegel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-230947 taken from his Spiegel customer service problem that occurred on October 28th, 2017.