Sirius/XM: Can not cancel.. Tried for * months now. Have d...
A Sirius/XM customer review by GetHuman user ~Hwarren951@aol.com from November 20th, 2017
Background on ~Hwarren951@aol.com's case
GetHuman: ~Hwarren951@aol.com - can you tell our other Sirius/XM customers when your case took place?
~Hwarren951@aol.com: Yup. It was middle of the night, on November 10th.
GetHuman: Did you reach out to Sirius/XM, and if so, how?
GetHuman: And which of these common Sirius/XM customer issues best describes the reason you wanted to talk to them?
(Shows ~Hwarren951@aol.com a list of common Sirius/XM problems)
~Hwarren951@aol.com: "Recover Account" was why I was trying to call.
~Hwarren951@aol.com's review of Sirius/XM customer service
GetHuman: So how would you sum up your experience for GetHuman's Sirius/XM 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.
~Hwarren951@aol.com: Can not cancel.. Tried for * months now. Have disputed on credit card and get a credit then they re bill me. Can't get a rep on phone without getting cut off.
GetHuman: Let's quantify your experience contacting Sirius/XM. On a scale of 1 to 5, how easy is it go get help on a Sirius/XM problem?
~Hwarren951@aol.com: 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?
~Hwarren951@aol.com: I'd give them a two out of five on communication.
GetHuman: And what about Sirius/XM's ability to quickly and effectively address your problem?
~Hwarren951@aol.com: For that I would say five out of five.
GetHuman: And finally- any advice for other Sirius/XM customers?
~Hwarren951@aol.com: Call them early in the day or late. Don't forget any personal or account information you might need for Sirius/XM to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Hwarren951@aol.com taken from his Sirius/XM customer service problem that occurred on November 10th, 2017.