Sears Delivery: Time window of *-*. When I called Sears. They s...
A Sears Delivery customer review by GetHuman user ~djones from November 14th, 2017
Background on ~djones's case
GetHuman: ~djones - can you tell our other Sears Delivery customers when your case took place?
~djones: Yes. It was morning, on November 12th.
GetHuman: Did you reach out to Sears Delivery, and if so, how?
GetHuman: And which of these common Sears Delivery customer issues best describes the reason you wanted to talk to them?
(Shows ~djones a list of common Sears Delivery problems)
~djones: "Change Delivery" was why I was trying to call.
~djones's review of Sears Delivery customer service
GetHuman: So how would you sum up your experience for GetHuman's Sears Delivery 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.
~djones: Time window of *-*. When I called Sears. They said "they attempted delivery" ...well they did BUT they were on the wrong street! Some how Sears thinks it is my fault! Horrible! Customer service is rude! STORE SERVICE IS EXCELLENT. DELIVERY SERVICE IS EMBARRASSING
GetHuman: Let's quantify your experience contacting Sears Delivery. On a scale of 1 to 5, how easy is it go get help on a Sears Delivery problem?
~djones: 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?
~djones: I'd give them a four out of five on communication.
GetHuman: And what about Sears Delivery's ability to quickly and effectively address your problem?
~djones: For that I would say three out of five.
GetHuman: And finally- any advice for other Sears Delivery customers?
~djones: Call them early in the day or late. Don't forget any personal or account information you might need for Sears Delivery to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~djones taken from his Sears Delivery customer service problem that occurred on November 12th, 2017.