Pandora Radio: I had a Pandora acct that I paid from my bankca...
A Pandora Radio customer review by GetHuman user ~Syssyie from November 22nd, 2017
Background on ~Syssyie's case
GetHuman: ~Syssyie - can you tell our other Pandora Radio customers when your case took place?
~Syssyie: Yes. It was afternoon, on November 19th.
GetHuman: Did you reach out to Pandora Radio, and if so, how?
GetHuman: And which of these common Pandora Radio customer issues best describes the reason you wanted to talk to them?
(Shows ~Syssyie a list of common Pandora Radio problems)
~Syssyie: "Overcharge on Account" was why I was trying to call.
~Syssyie's review of Pandora Radio customer service
GetHuman: So how would you sum up your experience for GetHuman's Pandora Radio 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.
~Syssyie: I had a Pandora acct that I paid from my bankcard monthly,it was on my Nook e-reader.My card was compromised so I ordered new card.Meanwhile,my acct was stopped.Now I want to restart it and your phone* is of NO help.How do I get my music back? HELP!!!
GetHuman: Let's quantify your experience contacting Pandora Radio. On a scale of 1 to 5, how easy is it go get help on a Pandora Radio problem?
~Syssyie: 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?
~Syssyie: I'd give them a one out of five on communication.
GetHuman: And what about Pandora Radio's ability to quickly and effectively address your problem?
~Syssyie: For that I would say two out of five.
GetHuman: And finally- any advice for other Pandora Radio customers?
~Syssyie: Call them early in the day or late. Don't forget any personal or account information you might need for Pandora Radio to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Syssyie taken from his Pandora Radio customer service problem that occurred on November 19th, 2017.