Vodafone (UK): After about ** minutes of trying various option...
A Vodafone (UK) customer review by GetHuman user ~Nick W from November 23rd, 2017
Background on ~Nick W's case
GetHuman: ~Nick W - can you tell our other Vodafone (UK) customers when your case took place?
~Nick W: Yes I can. It was late at night, on November 19th.
GetHuman: Did you reach out to Vodafone (UK), and if so, how?
GetHuman: And which of these common Vodafone (UK) customer issues best describes the reason you wanted to talk to them?
(Shows ~Nick W a list of common Vodafone (UK) problems)
~Nick W: "Complaint" was why I was trying to call.
~Nick W's review of Vodafone (UK) customer service
GetHuman: So how would you sum up your experience for GetHuman's Vodafone (UK) 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.
~Nick W: After about ** minutes of trying various options the support person realised they'd turned off an email service when upgrading my contract. TRied to charge me ***£* * month to add it. As i was their fault i refudes and git it for free after threatinging to return the phone.
GetHuman: Let's quantify your experience contacting Vodafone (UK). On a scale of 1 to 5, how easy is it go get help on a Vodafone (UK) problem?
~Nick W: 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?
~Nick W: I'd give them a five out of five on communication.
GetHuman: And what about Vodafone (UK)'s ability to quickly and effectively address your problem?
~Nick W: For that I would say one out of five.
GetHuman: And finally- any advice for other Vodafone (UK) customers?
~Nick W: Call them early in the day or late. Don't forget any personal or account information you might need for Vodafone (UK) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Nick W taken from his Vodafone (UK) customer service problem that occurred on November 19th, 2017.