Sears Delivery: Driver tried to deliver to wrong house then did...
A Sears Delivery customer review by GetHuman user GetHuman-407902 from November 25th, 2017
Background on GetHuman-407902's case
GetHuman: GetHuman-407902 - can you tell our other Sears Delivery customers when your case took place?
GetHuman-407902: Yeah. It was middle of the night, on November 18th.
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 GetHuman-407902 a list of common Sears Delivery problems)
GetHuman-407902: "Track order" was why I was trying to call.
GetHuman-407902'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.
GetHuman-407902: Driver tried to deliver to wrong house then didnt return his phn calls had to reschedule now still waiting * passed mu new reacheduled time. NEVER AGAIN!
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?
GetHuman-407902: 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-407902: I'd give them a one out of five on communication.
GetHuman: And what about Sears Delivery's ability to quickly and effectively address your problem?
GetHuman-407902: For that I would say five out of five.
GetHuman: And finally- any advice for other Sears Delivery customers?
GetHuman-407902: 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 GetHuman-407902 taken from his Sears Delivery customer service problem that occurred on November 18th, 2017.