Vodafone (UK): An appalling service. Would never again go with...
A Vodafone (UK) customer review by GetHuman user ~Unhappy customer from October 27th, 2017
Background on ~Unhappy customer's case
GetHuman: ~Unhappy customer - can you tell our other Vodafone (UK) customers when your case took place?
~Unhappy customer: Yup. It was evening, on October 21st.
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 ~Unhappy customer a list of common Vodafone (UK) problems)
~Unhappy customer: "Technical support" was why I was trying to call.
~Unhappy customer'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.
~Unhappy customer: An appalling service. Would never again go with VooDooFone. Customer services should be abolished. Worse than useless. To be avoided at all costs!
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?
~Unhappy customer: 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?
~Unhappy customer: I'd give them a two out of five on communication.
GetHuman: And what about Vodafone (UK)'s ability to quickly and effectively address your problem?
~Unhappy customer: For that I would say one out of five.
GetHuman: And finally- any advice for other Vodafone (UK) customers?
~Unhappy customer: 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 ~Unhappy customer taken from his Vodafone (UK) customer service problem that occurred on October 21st, 2017.