Sears Delivery: Third time calling about the same issue that ha...
A Sears Delivery customer review by GetHuman user ~LizH from November 23rd, 2017
Background on ~LizH's case
GetHuman: ~LizH - can you tell our other Sears Delivery customers when your case took place?
~LizH: Yes. It was evening, on November 14th.
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 ~LizH a list of common Sears Delivery problems)
~LizH: "Update Account Info" was why I was trying to call.
~LizH'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.
~LizH: Third time calling about the same issue that has not been resolved, waited for ** minutes to get a person, then when i did after giving her all of my information, i was put on hold for ** minutes before being sent back to the main menu without anyone ever coming back on the line.
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?
~LizH: 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?
~LizH: 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?
~LizH: For that I would say five out of five.
GetHuman: And finally- any advice for other Sears Delivery customers?
~LizH: 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 ~LizH taken from his Sears Delivery customer service problem that occurred on November 14th, 2017.