Barnes & Noble: No response, no communication, no service. Hav...
A Barnes & Noble customer review by GetHuman user ~NoNooke here from November 3rd, 2017
Background on ~NoNooke here's case
GetHuman: ~NoNooke here - can you tell our other Barnes & Noble customers when your case took place?
~NoNooke here: Yup. It was evening, on October 28th.
GetHuman: Did you reach out to Barnes & Noble, and if so, how?
GetHuman: And which of these common Barnes & Noble customer issues best describes the reason you wanted to talk to them?
(Shows ~NoNooke here a list of common Barnes & Noble problems)
~NoNooke here: "Track order" was why I was trying to call.
~NoNooke here's review of Barnes & Noble customer service
GetHuman: So how would you sum up your experience for GetHuman's Barnes & Noble 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.
~NoNooke here: No response, no communication, no service. Haven't been successful in getting to a live person. Call automatically disconnected after **-** minute waits. Customer service is non-existent
GetHuman: Let's quantify your experience contacting Barnes & Noble. On a scale of 1 to 5, how easy is it go get help on a Barnes & Noble problem?
~NoNooke here: 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?
~NoNooke here: I'd give them a three out of five on communication.
GetHuman: And what about Barnes & Noble's ability to quickly and effectively address your problem?
~NoNooke here: For that I would say five out of five.
GetHuman: And finally- any advice for other Barnes & Noble customers?
~NoNooke here: Call them early in the day or late. Don't forget any personal or account information you might need for Barnes & Noble to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~NoNooke here taken from his Barnes & Noble customer service problem that occurred on October 28th, 2017.