Virgin Mobile: Sam was very helpful! She fixed the issue with...
Eine Virgin Mobile Kundenbewertung durch GetHuman-Benutzer GetHuman-44702 von November 22., 2017
Background on GetHuman-44702's case
GetHuman: GetHuman-44702 - can you tell our other Virgin Mobile customers when your case took place?
GetHuman-44702: Yeah. It was middle of the night, on November 21..
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-44702 a list of common Virgin Mobile problems)
GetHuman-44702: "Lower my bill" was why I was trying to call.
GetHuman-44702'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-44702: Sam was very helpful! She fixed the issue with my phone and it only took a few moments. I appreciate her help!!! my issue was I could not send MMS
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-44702: 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?
GetHuman-44702: I'd give them a three out of five on communication.
GetHuman: And what about Virgin Mobile's ability to quickly and effectively address your problem?
GetHuman-44702: For that I would say four out of five.
GetHuman: And finally- any advice for other Virgin Mobile customers?
GetHuman-44702: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Virgin Mobile weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-44702 taken from his Virgin Mobile customer service problem that occurred on November 21., 2017.