Barnes & Noble: Calling for * days* this number does not workan...
A Barnes & Noble customer review by GetHuman user ~dizzillusionist from November 21st, 2017
Background on ~dizzillusionist's case
GetHuman: ~dizzillusionist - can you tell our other Barnes & Noble customers when your case took place?
~dizzillusionist: Sure. It was middle of the night, on November 13th.
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 ~dizzillusionist a list of common Barnes & Noble problems)
~dizzillusionist: "Returns" was why I was trying to call.
~dizzillusionist'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.
~dizzillusionist: Calling for * days* this number does not workand *** *** **** cust svc gives ans machine but not call back, lucy widget does not work
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?
~dizzillusionist: 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?
~dizzillusionist: I'd give them a two out of five on communication.
GetHuman: And what about Barnes & Noble's ability to quickly and effectively address your problem?
~dizzillusionist: For that I would say five out of five.
GetHuman: And finally- any advice for other Barnes & Noble customers?
~dizzillusionist: 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 ~dizzillusionist taken from his Barnes & Noble customer service problem that occurred on November 13th, 2017.