YouTube: I waited about ** minutes after going through a...
A YouTube customer review by GetHuman user ~Cat562 from November 22nd, 2017
Background on ~Cat562's case
GetHuman: ~Cat562 - can you tell our other YouTube customers when your case took place?
~Cat562: Yeah. It was late at night, on November 16th.
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 ~Cat562 a list of common YouTube problems)
~Cat562: "Problem With a Channel" was why I was trying to contact.
~Cat562'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.
~Cat562: I waited about ** minutes after going through an automated recording and pushed "*" to get a human. She basically just walked me through the help center on Google*YouTube which I already did with no luck. She answered my question which didn't resolve my problem but helped me try to resolve my issue through the help center online. Annoying.
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?
~Cat562: 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?
~Cat562: I'd give them a one out of five on communication.
GetHuman: And what about YouTube's ability to quickly and effectively address your problem?
~Cat562: For that I would say two out of five.
GetHuman: And finally- any advice for other YouTube customers?
~Cat562: 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 ~Cat562 taken from his YouTube customer service problem that occurred on November 16th, 2017.