Bed Bath & Beyond: Very accomodating, saved me a trip through the...
A Bed Bath & Beyond customer review by GetHuman user ~AJGunderson from November 11th, 2017
Background on ~AJGunderson's case
GetHuman: ~AJGunderson - can you tell our other Bed Bath & Beyond customers when your case took place?
~AJGunderson: Yes I can. It was middle of the night, on November 4th.
GetHuman: Did you reach out to Bed Bath & Beyond, and if so, how?
GetHuman: And which of these common Bed Bath & Beyond customer issues best describes the reason you wanted to talk to them?
(Shows ~AJGunderson a list of common Bed Bath & Beyond problems)
~AJGunderson: "Warranty claim" was why I was trying to call.
~AJGunderson's review of Bed Bath & Beyond customer service
GetHuman: So how would you sum up your experience for GetHuman's Bed Bath & Beyond 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.
~AJGunderson: Very accomodating, saved me a trip through the store by helping at desk. "Soda stream refills" were easily found with help of employee.
GetHuman: Let's quantify your experience contacting Bed Bath & Beyond. On a scale of 1 to 5, how easy is it go get help on a Bed Bath & Beyond problem?
~AJGunderson: I'd give them a four 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?
~AJGunderson: I'd give them a three out of five on communication.
GetHuman: And what about Bed Bath & Beyond's ability to quickly and effectively address your problem?
~AJGunderson: For that I would say two out of five.
GetHuman: And finally- any advice for other Bed Bath & Beyond customers?
~AJGunderson: Call them early in the day or late. Don't forget any personal or account information you might need for Bed Bath & Beyond to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~AJGunderson taken from his Bed Bath & Beyond customer service problem that occurred on November 4th, 2017.