Virgin Mobile: great customer service. if you dont push button...
Una recensione del cliente Virgin Mobile da parte dell'utente GetHuman GetHuman-424524 da novembre 21º, 2017
Background on GetHuman-424524's case
GetHuman: GetHuman-424524 - can you tell our other Virgin Mobile customers when your case took place?
GetHuman-424524: Yes. It was afternoon, on novembre 14º.
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-424524 a list of common Virgin Mobile problems)
GetHuman-424524: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-424524'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-424524: great customer service. if you dont push buttons past a certain point they send you straight to a person. mila was wonderful.
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-424524: I'd give them a four 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-424524: I'd give them a one out of five on communication.
GetHuman: And what about Virgin Mobile's ability to quickly and effectively address your problem?
GetHuman-424524: For that I would say four out of five.
GetHuman: And finally- any advice for other Virgin Mobile customers?
GetHuman-424524: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Virgin Mobile sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-424524 taken from his Virgin Mobile customer service problem that occurred on novembre 14º, 2017.