Best Buy: The worst. We are seventies. Not computer liter...
A Best Buy customer review by GetHuman user ~Almaglin from November 19th, 2017
Background on ~Almaglin's case
GetHuman: ~Almaglin - can you tell our other Best Buy customers when your case took place?
~Almaglin: Yes I can. It was afternoon, on November 12th.
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 ~Almaglin a list of common Best Buy problems)
~Almaglin: "Complaint" was why I was trying to call.
~Almaglin'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.
~Almaglin: The worst. We are seventies. Not computer literate. Sold everything.. Don't really know what we bought. Ask for demonstration . Ignored. Sent home with computer. Have no idea what to do, how to put together with printer And router. Your company should be ashamed of itself. Cut off * times from customer service
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?
~Almaglin: 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?
~Almaglin: I'd give them a three out of five on communication.
GetHuman: And what about Best Buy's ability to quickly and effectively address your problem?
~Almaglin: For that I would say four out of five.
GetHuman: And finally- any advice for other Best Buy customers?
~Almaglin: 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 ~Almaglin taken from his Best Buy customer service problem that occurred on November 12th, 2017.