Virgin Mobile: I was charged *x when adding $ for top up minut...
Eine Virgin Mobile Kundenbewertung durch GetHuman-Benutzer ~helshe von November 20., 2017
Background on ~helshe's case
GetHuman: ~helshe - can you tell our other Virgin Mobile customers when your case took place?
~helshe: Yes. It was evening, on November 10..
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 ~helshe a list of common Virgin Mobile problems)
~helshe: "Complaint" was why I was trying to call.
~helshe'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.
~helshe: I was charged *x when adding $ for top up minutes. After waiting ** hours to receive a response from accounting, they have only refunded part of the overcharge. There is no transparency in how they bill or account for extra minutes bought.
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?
~helshe: 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?
~helshe: I'd give them a five out of five on communication.
GetHuman: And what about Virgin Mobile's ability to quickly and effectively address your problem?
~helshe: For that I would say three out of five.
GetHuman: And finally- any advice for other Virgin Mobile customers?
~helshe: 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 ~helshe taken from his Virgin Mobile customer service problem that occurred on November 10., 2017.