Bed Bath & Beyond: asked for location,found exactly what I needed...
A Bed Bath & Beyond customer review by GetHuman user GetHuman-355256 from November 11th, 2017
Background on GetHuman-355256's case
GetHuman: GetHuman-355256 - can you tell our other Bed Bath & Beyond customers when your case took place?
GetHuman-355256: Sure. It was late at night, on November 8th.
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 GetHuman-355256 a list of common Bed Bath & Beyond problems)
GetHuman-355256: "Warranty claim" was why I was trying to call.
GetHuman-355256'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.
GetHuman-355256: asked for location,found exactly what I needed..Check out,with no line. Finished shopping within ** minutes.
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?
GetHuman-355256: 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?
GetHuman-355256: I'd give them a five out of five on communication.
GetHuman: And what about Bed Bath & Beyond's ability to quickly and effectively address your problem?
GetHuman-355256: For that I would say two out of five.
GetHuman: And finally- any advice for other Bed Bath & Beyond customers?
GetHuman-355256: 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 GetHuman-355256 taken from his Bed Bath & Beyond customer service problem that occurred on November 8th, 2017.