Barnes & Noble: Times *-*, poor. Bad-speaking rep never could h...
A Barnes & Noble customer review by GetHuman user ~ticked from November 22nd, 2017
Background on ~ticked's case
GetHuman: ~ticked - can you tell our other Barnes & Noble customers when your case took place?
~ticked: Yup. It was morning, on November 18th.
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 ~ticked a list of common Barnes & Noble problems)
~ticked: "Complaint" was why I was trying to call.
~ticked'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.
~ticked: Times *-*, poor. Bad-speaking rep never could help and it took twice the time as with someone in the US. Time * *, I could understand her, but still didn't get the issue solved on a lost number for an E-gift card. Never again will I do business with B & Noble!
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?
~ticked: 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?
~ticked: I'd give them a four out of five on communication.
GetHuman: And what about Barnes & Noble's ability to quickly and effectively address your problem?
~ticked: For that I would say three out of five.
GetHuman: And finally- any advice for other Barnes & Noble customers?
~ticked: 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 ~ticked taken from his Barnes & Noble customer service problem that occurred on November 18th, 2017.