Sirius/XM: I talked to first person put on hold & was disc...
A Sirius/XM customer review by GetHuman user GetHuman-343495 from November 26th, 2017
Background on GetHuman-343495's case
GetHuman: GetHuman-343495 - can you tell our other Sirius/XM customers when your case took place?
GetHuman-343495: Yes I can. It was middle of the night, on November 22nd.
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 GetHuman-343495 a list of common Sirius/XM problems)
GetHuman-343495: "Dispute a Charge" was why I was trying to call.
GetHuman-343495'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.
GetHuman-343495: I talked to first person put on hold & was disconnected. This happened with three different people! I believe they digit on purpose.! Icalled back & my issue is still not resolved! Terrible customer care!
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?
GetHuman-343495: 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?
GetHuman-343495: 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?
GetHuman-343495: For that I would say five out of five.
GetHuman: And finally- any advice for other Sirius/XM customers?
GetHuman-343495: 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 GetHuman-343495 taken from his Sirius/XM customer service problem that occurred on November 22nd, 2017.