Big Lots, Inc.: There is a Manager there by the last name of Pi...
A Big Lots, Inc. customer review by GetHuman user ~Shelby from November 6th, 2017
Background on ~Shelby's case
GetHuman: ~Shelby - can you tell our other Big Lots, Inc. customers when your case took place?
~Shelby: Sure. It was middle of the night, on November 5th.
GetHuman: Did you reach out to Big Lots, Inc., and if so, how?
GetHuman: And which of these common Big Lots, Inc. customer issues best describes the reason you wanted to talk to them?
(Shows ~Shelby a list of common Big Lots, Inc. problems)
~Shelby: "Complaint" was why I was trying to call.
~Shelby's review of Big Lots, Inc. customer service
GetHuman: So how would you sum up your experience for GetHuman's Big Lots, Inc. 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.
~Shelby: There is a Manager there by the last name of Pickett who was very rude to me and my family. She was talking to the other employees and did say a word to us when we were checking out so I put my thing down and walked out. I will never go back the again.
GetHuman: Let's quantify your experience contacting Big Lots, Inc.. On a scale of 1 to 5, how easy is it go get help on a Big Lots, Inc. problem?
~Shelby: I'd give them a five 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?
~Shelby: I'd give them a five out of five on communication.
GetHuman: And what about Big Lots, Inc.'s ability to quickly and effectively address your problem?
~Shelby: For that I would say five out of five.
GetHuman: And finally- any advice for other Big Lots, Inc. customers?
~Shelby: Call them early in the day or late. Don't forget any personal or account information you might need for Big Lots, Inc. to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Shelby taken from his Big Lots, Inc. customer service problem that occurred on November 5th, 2017.