Virgin Mobile: we told the guy to not reset the phone and he d...
नवंबर २६, २०१७ से GetHuman उपयोगकर्ता GetHuman-404476 द्वारा एक Virgin Mobile ग्राहक की समीक्षा
Background on GetHuman-404476's case
GetHuman: GetHuman-404476 - can you tell our other Virgin Mobile customers when your case took place?
GetHuman-404476: Sure. It was middle of the night, on नवंबर १९.
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-404476 a list of common Virgin Mobile problems)
GetHuman-404476: "Setup service" was why I was trying to call.
GetHuman-404476'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-404476: we told the guy to not reset the phone and he does it anyways we lost a lot of stuff that we cant get back because of it.about ready to leave virgin
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-404476: 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-404476: 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-404476: For that I would say four out of five.
GetHuman: And finally- any advice for other Virgin Mobile customers?
GetHuman-404476: उन्हें दिन में या देर से जल्दी बुलाओ। किसी भी व्यक्तिगत या खाता जानकारी को न भूलें जो आपको पता करने के लिए Virgin Mobile की आवश्यकता हो सकती है।
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-404476 taken from his Virgin Mobile customer service problem that occurred on नवंबर १९, २०१७.