Best Buy: Called at * pm on ******* needed to speak to th...
A Best Buy customer review by GetHuman user GetHuman-154768 from November 1st, 2017
Background on GetHuman-154768's case
GetHuman: GetHuman-154768 - can you tell our other Best Buy customers when your case took place?
GetHuman-154768: Yup. It was morning, on October 24th.
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-154768 a list of common Best Buy problems)
GetHuman-154768: "Warranty claim" was why I was trying to call.
GetHuman-154768'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-154768: Called at * pm on ******* needed to speak to the Geek Squad* call was ansered within one minute and connected to the right person within the next minute. Person solved my problem within about * minutes* very, very happy with the situation from my call.
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-154768: I'd give them a one 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-154768: I'd give them a two out of five on communication.
GetHuman: And what about Best Buy's ability to quickly and effectively address your problem?
GetHuman-154768: For that I would say one out of five.
GetHuman: And finally- any advice for other Best Buy customers?
GetHuman-154768: 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-154768 taken from his Best Buy customer service problem that occurred on October 24th, 2017.