Best Buy: this is not a good number to reach a high level...
A Best Buy customer review by GetHuman user ~simplelife from November 4th, 2017
Background on ~simplelife's case
GetHuman: ~simplelife - can you tell our other Best Buy customers when your case took place?
~simplelife: Yup. It was afternoon, on November 2nd.
GetHuman: Did you reach out to Best Buy, and if so, how?
GetHuman: And which of these common Best Buy customer issues best describes the reason you wanted to talk to them?
(Shows ~simplelife a list of common Best Buy problems)
~simplelife: "Geek Squad Support" was why I was trying to call.
~simplelife's review of Best Buy customer service
GetHuman: So how would you sum up your experience for GetHuman's Best Buy 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.
~simplelife: this is not a good number to reach a high level person who can change the way things are done at this store - this is the general *** number only. this company is now asking for your driver's license number to transact any credits or refunds at all. I will never shop at Best Buy again.
GetHuman: Let's quantify your experience contacting Best Buy. On a scale of 1 to 5, how easy is it go get help on a Best Buy problem?
~simplelife: 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?
~simplelife: I'd give them a one out of five on communication.
GetHuman: And what about Best Buy's ability to quickly and effectively address your problem?
~simplelife: For that I would say one out of five.
GetHuman: And finally- any advice for other Best Buy customers?
~simplelife: Call them early in the day or late. Don't forget any personal or account information you might need for Best Buy to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~simplelife taken from his Best Buy customer service problem that occurred on November 2nd, 2017.