Best Buy: I have been a reward zone member for three year...
A Best Buy customer review by GetHuman user GetHuman-330473 from October 28th, 2017
Background on GetHuman-330473's case
GetHuman: GetHuman-330473 - can you tell our other Best Buy customers when your case took place?
GetHuman-330473: Yup. It was evening, on October 26th.
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 GetHuman-330473 a list of common Best Buy problems)
GetHuman-330473: "Complaint" was why I was trying to call.
GetHuman-330473'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.
GetHuman-330473: I have been a reward zone member for three years and still have not been able to get them to get my account information correct, get me login information for the site, or send me a card. Worst customer service I have ever experienced in my life.
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?
GetHuman-330473: I'd give them a two 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-330473: I'd give them a five out of five on communication.
GetHuman: And what about Best Buy's ability to quickly and effectively address your problem?
GetHuman-330473: For that I would say four out of five.
GetHuman: And finally- any advice for other Best Buy customers?
GetHuman-330473: 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 GetHuman-330473 taken from his Best Buy customer service problem that occurred on October 26th, 2017.