Best Buy: I have called twice and had five different peop...
Eine Best Buy Kundenbewertung durch GetHuman-Benutzer ~Mad in Chattanooga von November 13., 2017
Background on ~Mad in Chattanooga's case
GetHuman: ~Mad in Chattanooga - can you tell our other Best Buy customers when your case took place?
~Mad in Chattanooga: Yes. It was middle of the night, on November 9..
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 ~Mad in Chattanooga a list of common Best Buy problems)
~Mad in Chattanooga: "Change order" was why I was trying to call.
~Mad in Chattanooga'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.
~Mad in Chattanooga: I have called twice and had five different people on the phone only to get disconnected both times trying to resolve an issue with the Reward Zone account.
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?
~Mad in Chattanooga: 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?
~Mad in Chattanooga: 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?
~Mad in Chattanooga: For that I would say one out of five.
GetHuman: And finally- any advice for other Best Buy customers?
~Mad in Chattanooga: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Best Buy weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~Mad in Chattanooga taken from his Best Buy customer service problem that occurred on November 9., 2017.