Pottery Barn: Fought with them over three months via e-mail a...
A Pottery Barn customer review by GetHuman user ~Woo Pig Sooie from November 21st, 2017
Background on ~Woo Pig Sooie's case
GetHuman: ~Woo Pig Sooie - can you tell our other Pottery Barn customers when your case took place?
~Woo Pig Sooie: Yeah. It was middle of the night, on November 14th.
GetHuman: Did you reach out to Pottery Barn, and if so, how?
GetHuman: And which of these common Pottery Barn customer issues best describes the reason you wanted to talk to them?
(Shows ~Woo Pig Sooie a list of common Pottery Barn problems)
~Woo Pig Sooie: "Cancel order" was why I was trying to call.
~Woo Pig Sooie's review of Pottery Barn customer service
GetHuman: So how would you sum up your experience for GetHuman's Pottery Barn 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.
~Woo Pig Sooie: Fought with them over three months via e-mail and phone about product missing parts. Did not want to give me a refund. Finally got one after wasting hours of time holding on the line.
GetHuman: Let's quantify your experience contacting Pottery Barn. On a scale of 1 to 5, how easy is it go get help on a Pottery Barn problem?
~Woo Pig Sooie: 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?
~Woo Pig Sooie: I'd give them a two out of five on communication.
GetHuman: And what about Pottery Barn's ability to quickly and effectively address your problem?
~Woo Pig Sooie: For that I would say one out of five.
GetHuman: And finally- any advice for other Pottery Barn customers?
~Woo Pig Sooie: Call them early in the day or late. Don't forget any personal or account information you might need for Pottery Barn to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Woo Pig Sooie taken from his Pottery Barn customer service problem that occurred on November 14th, 2017.