Sears: The person who answered the phone couldn't hear...
A Sears customer review by GetHuman user ~Dissatisfied customer from November 22nd, 2017
Background on ~Dissatisfied customer's case
GetHuman: ~Dissatisfied customer - can you tell our other Sears customers when your case took place?
~Dissatisfied customer: Yes I can. It was middle of the night, on November 18th.
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 ~Dissatisfied customer a list of common Sears problems)
~Dissatisfied customer: "Complaint" was why I was trying to call.
~Dissatisfied customer'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.
~Dissatisfied customer: The person who answered the phone couldn't hear or articulate clearly, couldn't find my information. It seems to me sears is more about making money than satisfied customers
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?
~Dissatisfied customer: I'd give them a three 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?
~Dissatisfied customer: I'd give them a one out of five on communication.
GetHuman: And what about Sears's ability to quickly and effectively address your problem?
~Dissatisfied customer: For that I would say three out of five.
GetHuman: And finally- any advice for other Sears customers?
~Dissatisfied customer: 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 ~Dissatisfied customer taken from his Sears customer service problem that occurred on November 18th, 2017.