Best Buy: First I was connected to a customer rep but I c...
Best Buy Ulasan pelanggan oleh pengguna GetHuman GetHuman-364887 dari November 19, 2017
Background on GetHuman-364887's case
GetHuman: GetHuman-364887 - can you tell our other Best Buy customers when your case took place?
GetHuman-364887: Yeah. It was late at night, on November 10.
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-364887 a list of common Best Buy problems)
GetHuman-364887: "Make a purchase" was why I was trying to call.
GetHuman-364887'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-364887: First I was connected to a customer rep but I couldn't hear her and she was breaking up. The time was **:** pm and Best Buy claims their line is open to midnight but after a second try, the customer service line is closed.
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-364887: 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-364887: 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?
GetHuman-364887: For that I would say two out of five.
GetHuman: And finally- any advice for other Best Buy customers?
GetHuman-364887: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Best Buy mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-364887 taken from his Best Buy customer service problem that occurred on November 10, 2017.