Sears: I called about my garage door opener remotes no...
A Sears customer review by GetHuman user ~Caroline from November 27th, 2017
Background on ~Caroline's case
GetHuman: ~Caroline - can you tell our other Sears customers when your case took place?
~Caroline: Yes I can. It was late at night, on November 23rd.
GetHuman: Did you reach out to Sears, and if so, how?
GetHuman: And which of these common Sears customer issues best describes the reason you wanted to talk to them?
(Shows ~Caroline a list of common Sears problems)
~Caroline: "Refund a Charge" was why I was trying to call.
~Caroline's review of Sears customer service
GetHuman: So how would you sum up your experience for GetHuman's Sears 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.
~Caroline: I called about my garage door opener remotes not working properly after security system was installed and I was given some info by the first person who answered and then he transferred me to a garage door tech specialist and she answered by questions and gave the info I needed to go back to the Security System people so they can fix the problem
GetHuman: Let's quantify your experience contacting Sears. On a scale of 1 to 5, how easy is it go get help on a Sears problem?
~Caroline: I'd give them a two 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?
~Caroline: I'd give them a five out of five on communication.
GetHuman: And what about Sears's ability to quickly and effectively address your problem?
~Caroline: For that I would say two out of five.
GetHuman: And finally- any advice for other Sears customers?
~Caroline: Call them early in the day or late. Don't forget any personal or account information you might need for Sears to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Caroline taken from his Sears customer service problem that occurred on November 23rd, 2017.