Hayneedle: The customer service rep I spoke to was Amy and...
A Hayneedle customer review by GetHuman user ~BeeZee from November 22nd, 2017
Background on ~BeeZee's case
GetHuman: ~BeeZee - can you tell our other Hayneedle customers when your case took place?
~BeeZee: Yeah. It was morning, on November 20th.
GetHuman: Did you reach out to Hayneedle, and if so, how?
GetHuman: And which of these common Hayneedle customer issues best describes the reason you wanted to talk to them?
(Shows ~BeeZee a list of common Hayneedle problems)
~BeeZee: "Returns" was why I was trying to call.
~BeeZee's review of Hayneedle customer service
GetHuman: So how would you sum up your experience for GetHuman's Hayneedle 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.
~BeeZee: The customer service rep I spoke to was Amy and she was courteous and most helpful. I was provided a most satisfactory solution to the disappointing problem I encountered. That a company encounters problems is part of life* I am very pleased that Hayneedle resolved this issue in such a positive and satisfactory manner. Thanks to all.
GetHuman: Let's quantify your experience contacting Hayneedle. On a scale of 1 to 5, how easy is it go get help on a Hayneedle problem?
~BeeZee: 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?
~BeeZee: I'd give them a one out of five on communication.
GetHuman: And what about Hayneedle's ability to quickly and effectively address your problem?
~BeeZee: For that I would say one out of five.
GetHuman: And finally- any advice for other Hayneedle customers?
~BeeZee: Call them early in the day or late. Don't forget any personal or account information you might need for Hayneedle to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~BeeZee taken from his Hayneedle customer service problem that occurred on November 20th, 2017.