Virgin Mobile: No wait, completely fixed my device! Definitely...
A Virgin Mobile customer review by GetHuman user GetHuman-49657 from November 24th, 2017
Background on GetHuman-49657's case
GetHuman: GetHuman-49657 - can you tell our other Virgin Mobile customers when your case took place?
GetHuman-49657: Yeah. It was middle of the night, on November 22nd.
GetHuman: Did you reach out to Virgin Mobile, and if so, how?
GetHuman: And which of these common Virgin Mobile customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-49657 a list of common Virgin Mobile problems)
GetHuman-49657: "Complaint" was why I was trying to call.
GetHuman-49657's review of Virgin Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's Virgin Mobile 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-49657: No wait, completely fixed my device! Definitely happy with the service. The only thing it that sometimes it can be a little difficult to understand their customer service's accents.
GetHuman: Let's quantify your experience contacting Virgin Mobile. On a scale of 1 to 5, how easy is it go get help on a Virgin Mobile problem?
GetHuman-49657: 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-49657: I'd give them a two out of five on communication.
GetHuman: And what about Virgin Mobile's ability to quickly and effectively address your problem?
GetHuman-49657: For that I would say one out of five.
GetHuman: And finally- any advice for other Virgin Mobile customers?
GetHuman-49657: Call them early in the day or late. Don't forget any personal or account information you might need for Virgin Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-49657 taken from his Virgin Mobile customer service problem that occurred on November 22nd, 2017.