Spotify: My office does not allow use of social media. I...
A Spotify customer review by GetHuman user ~SClary from November 20th, 2017
Background on ~SClary's case
GetHuman: ~SClary - can you tell our other Spotify customers when your case took place?
~SClary: Yup. It was evening, on November 11th.
GetHuman: Did you reach out to Spotify, and if so, how?
GetHuman: And which of these common Spotify customer issues best describes the reason you wanted to talk to them?
(Shows ~SClary a list of common Spotify problems)
~SClary: "Refund" was why I was trying to contact.
~SClary's review of Spotify customer service
GetHuman: So how would you sum up your experience for GetHuman's Spotify 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.
~SClary: My office does not allow use of social media. I find myself not able to sign into my Spotify account because I cannot use FB. When I try to contact customer service for Spotify, it requires a signin to my account. Of course, you know I can't do that from work without access to FB. So.... how do I contact customer service with no number or email?
GetHuman: Let's quantify your experience contacting Spotify. On a scale of 1 to 5, how easy is it go get help on a Spotify problem?
~SClary: 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?
~SClary: I'd give them a four out of five on communication.
GetHuman: And what about Spotify's ability to quickly and effectively address your problem?
~SClary: For that I would say one out of five.
GetHuman: And finally- any advice for other Spotify customers?
~SClary: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Spotify to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~SClary taken from his Spotify customer service problem that occurred on November 11th, 2017.