Virgin Media has extremely poor Customer Servic...
A Virgin Media customer review by GetHuman user ~hera from October 28th, 2017
Background on ~hera's case
GetHuman: ~hera - can you tell our other Virgin Media customers when your case took place?
~hera: Yup. It was middle of the night, on October 20th.
GetHuman: Did you reach out to Virgin Media, and if so, how?
GetHuman: And which of these common Virgin Media customer issues best describes the reason you wanted to talk to them?
(Shows ~hera a list of common Virgin Media problems)
~hera: "Complaint" was why I was trying to call.
~hera's review of Virgin Media customer service
GetHuman: So how would you sum up your experience for GetHuman's Virgin Media 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.
~hera: Virgin Media has extremely poor Customer Services with staff who often give false information or who cannot understand English, especially local terminology. I have never waited less than ** minutes to be connected. They also use an **** number as their main number which costs *p per minute from a Virgin Media phone.
GetHuman: Let's quantify your experience contacting Virgin Media. On a scale of 1 to 5, how easy is it go get help on a Virgin Media problem?
~hera: 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?
~hera: I'd give them a three out of five on communication.
GetHuman: And what about Virgin Media's ability to quickly and effectively address your problem?
~hera: For that I would say four out of five.
GetHuman: And finally- any advice for other Virgin Media customers?
~hera: Call them early in the day or late. Don't forget any personal or account information you might need for Virgin Media to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~hera taken from his Virgin Media customer service problem that occurred on October 20th, 2017.