Sirius/XM: Switched service to my new vehicle, took my mon...
A Sirius/XM customer review by GetHuman user ~Will from November 25th, 2017
Background on ~Will's case
GetHuman: ~Will - can you tell our other Sirius/XM customers when your case took place?
~Will: Sure. It was morning, on November 15th.
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 ~Will a list of common Sirius/XM problems)
~Will: "Overcharge/Strange charge" was why I was trying to call.
~Will'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.
~Will: Switched service to my new vehicle, took my money no service. Called back * times, very hard to understand customer service person, still no service. Sent a email requesting someone who spoke English to call me, nothing. Their customer service is a joke. Got their attention when I discussed where they could stick my accounts, cancelled both.
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?
~Will: 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?
~Will: I'd give them a five out of five on communication.
GetHuman: And what about Sirius/XM's ability to quickly and effectively address your problem?
~Will: For that I would say five out of five.
GetHuman: And finally- any advice for other Sirius/XM customers?
~Will: 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 ~Will taken from his Sirius/XM customer service problem that occurred on November 15th, 2017.