Barnes & Noble: I called * different times in one day b*c i got...
A Barnes & Noble customer review by GetHuman user GetHuman-388678 from November 3rd, 2017
Background on GetHuman-388678's case
GetHuman: GetHuman-388678 - can you tell our other Barnes & Noble customers when your case took place?
GetHuman-388678: Yup. It was afternoon, on November 1st.
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 GetHuman-388678 a list of common Barnes & Noble problems)
GetHuman-388678: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-388678'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.
GetHuman-388678: I called * different times in one day b*c i got tired of holding!! My total hold time was * hrs and ** minutes! and they STILL DIDN'T HELP ME!!!
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?
GetHuman-388678: 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?
GetHuman-388678: I'd give them a one out of five on communication.
GetHuman: And what about Barnes & Noble's ability to quickly and effectively address your problem?
GetHuman-388678: For that I would say four out of five.
GetHuman: And finally- any advice for other Barnes & Noble customers?
GetHuman-388678: 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 GetHuman-388678 taken from his Barnes & Noble customer service problem that occurred on November 1st, 2017.