Skullcandy: I called about my Astro Gaming headset and they...
A Skullcandy customer review by GetHuman user GetHuman-181371 from November 18th, 2017
Background on GetHuman-181371's case
GetHuman: GetHuman-181371 - can you tell our other Skullcandy customers when your case took place?
GetHuman-181371: Sure. It was middle of the night, on November 10th.
GetHuman: Did you reach out to Skullcandy, and if so, how?
GetHuman: And which of these common Skullcandy customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-181371 a list of common Skullcandy problems)
GetHuman-181371: "Where to buy" was why I was trying to call.
GetHuman-181371's review of Skullcandy customer service
GetHuman: So how would you sum up your experience for GetHuman's Skullcandy 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-181371: I called about my Astro Gaming headset and they helped me and gave me some tips.**Great customer service lady was very nice to me, was dumbfounded when I mentioned how I was handled by an email support rep.
GetHuman: Let's quantify your experience contacting Skullcandy. On a scale of 1 to 5, how easy is it go get help on a Skullcandy problem?
GetHuman-181371: I'd give them a five 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-181371: I'd give them a five out of five on communication.
GetHuman: And what about Skullcandy's ability to quickly and effectively address your problem?
GetHuman-181371: For that I would say three out of five.
GetHuman: And finally- any advice for other Skullcandy customers?
GetHuman-181371: Call them early in the day or late. Don't forget any personal or account information you might need for Skullcandy to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-181371 taken from his Skullcandy customer service problem that occurred on November 10th, 2017.