Best Buy: The agent was calm and helpful. He was nice and...
A Best Buy customer review by GetHuman user GetHuman-141116 from November 15th, 2017
Background on GetHuman-141116's case
GetHuman: GetHuman-141116 - can you tell our other Best Buy customers when your case took place?
GetHuman-141116: Sure. It was evening, on November 6th.
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-141116 a list of common Best Buy problems)
GetHuman-141116: "Dispute a Charge" was why I was trying to call.
GetHuman-141116'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-141116: The agent was calm and helpful. He was nice and transferred me over to a nice woman. Despite the accent which was very slightly hard to understand, she was so nice and helpful. She helped me get a new battery after UPS lost my warranty one.
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-141116: I'd give them a three 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-141116: I'd give them a four out of five on communication.
GetHuman: And what about Best Buy's ability to quickly and effectively address your problem?
GetHuman-141116: For that I would say three out of five.
GetHuman: And finally- any advice for other Best Buy customers?
GetHuman-141116: 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-141116 taken from his Best Buy customer service problem that occurred on November 6th, 2017.