1 Sale a Day: There is no answer because they are too busy ag...
A 1 Sale a Day customer review by GetHuman user ~Michelle from November 20th, 2017
Background on ~Michelle's case
GetHuman: ~Michelle - can you tell our other 1 Sale a Day customers when your case took place?
~Michelle: Yes I can. It was morning, on November 10th.
GetHuman: Did you reach out to 1 Sale a Day, and if so, how?
GetHuman: And which of these common 1 Sale a Day customer issues best describes the reason you wanted to talk to them?
(Shows ~Michelle a list of common 1 Sale a Day problems)
~Michelle: "Change order" was why I was trying to call.
~Michelle's review of 1 Sale a Day customer service
GetHuman: So how would you sum up your experience for GetHuman's 1 Sale a Day 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.
~Michelle: There is no answer because they are too busy again. and then I try to connect via web for faster service and there is a picture of a microphone that did nothing for me. I just want my item I ordered at Christmas and I have an exchange the slippers were too small.
GetHuman: Let's quantify your experience contacting 1 Sale a Day. On a scale of 1 to 5, how easy is it go get help on a 1 Sale a Day problem?
~Michelle: I'd give them a five 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?
~Michelle: I'd give them a five out of five on communication.
GetHuman: And what about 1 Sale a Day's ability to quickly and effectively address your problem?
~Michelle: For that I would say three out of five.
GetHuman: And finally- any advice for other 1 Sale a Day customers?
~Michelle: Call them early in the day or late. Don't forget any personal or account information you might need for 1 Sale a Day to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Michelle taken from his 1 Sale a Day customer service problem that occurred on November 10th, 2017.