Vodafone (Germany): I was trying to connect someone in vodafone tha...
A Vodafone (Germany) customer review by GetHuman user ~Ce from November 23rd, 2017
Background on ~Ce's case
GetHuman: ~Ce - can you tell our other Vodafone (Germany) customers when your case took place?
~Ce: Yup. It was middle of the night, on November 20th.
GetHuman: Did you reach out to Vodafone (Germany), and if so, how?
GetHuman: And which of these common Vodafone (Germany) customer issues best describes the reason you wanted to talk to them?
(Shows ~Ce a list of common Vodafone (Germany) problems)
~Ce: "Cancel service" was why I was trying to call.
~Ce's review of Vodafone (Germany) customer service
GetHuman: So how would you sum up your experience for GetHuman's Vodafone (Germany) 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.
~Ce: I was trying to connect someone in vodafone that speaks english and no one does (like, for real). Then I called this number and they told me that they only see problems with mobile contracts, but nothing about DSL connections or other stuff.
GetHuman: Let's quantify your experience contacting Vodafone (Germany). On a scale of 1 to 5, how easy is it go get help on a Vodafone (Germany) problem?
~Ce: 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?
~Ce: I'd give them a one out of five on communication.
GetHuman: And what about Vodafone (Germany)'s ability to quickly and effectively address your problem?
~Ce: For that I would say three out of five.
GetHuman: And finally- any advice for other Vodafone (Germany) customers?
~Ce: Call them early in the day or late. Don't forget any personal or account information you might need for Vodafone (Germany) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ce taken from his Vodafone (Germany) customer service problem that occurred on November 20th, 2017.