YouTube: I am Happy to know I am Not the only one who Kn...
A YouTube customer review by GetHuman user ~skipitxd9 from November 18th, 2017
Background on ~skipitxd9's case
GetHuman: ~skipitxd9 - can you tell our other YouTube customers when your case took place?
~skipitxd9: Yup. It was middle of the night, on November 9th.
GetHuman: Did you reach out to YouTube, and if so, how?
GetHuman: And which of these common YouTube customer issues best describes the reason you wanted to talk to them?
(Shows ~skipitxd9 a list of common YouTube problems)
~skipitxd9: "Setup service" was why I was trying to contact.
~skipitxd9's review of YouTube customer service
GetHuman: So how would you sum up your experience for GetHuman's YouTube 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.
~skipitxd9: I am Happy to know I am Not the only one who Knows it is Impossible to find a Human to Help with Google and Youtube Problems. All I ever got was emails with information that caused me to Loose Even the Shortcut to see my Old channel, So Never again will I be able to chat with my subscribers on skipitxd**
GetHuman: Let's quantify your experience contacting YouTube. On a scale of 1 to 5, how easy is it go get help on a YouTube problem?
~skipitxd9: I'd give them a one 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?
~skipitxd9: I'd give them a four out of five on communication.
GetHuman: And what about YouTube's ability to quickly and effectively address your problem?
~skipitxd9: For that I would say one out of five.
GetHuman: And finally- any advice for other YouTube customers?
~skipitxd9: Call them early in the day or late. Don't forget any personal or account information you might need for YouTube to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~skipitxd9 taken from his YouTube customer service problem that occurred on November 9th, 2017.