Google: This is just one reason why I am canceling*goog...
A Google customer review by GetHuman user ~Poorservice from November 24th, 2017
Background on ~Poorservice's case
GetHuman: ~Poorservice - can you tell our other Google customers when your case took place?
~Poorservice: Yes. It was morning, on November 16th.
GetHuman: Did you reach out to Google, and if so, how?
GetHuman: And which of these common Google customer issues best describes the reason you wanted to talk to them?
(Shows ~Poorservice a list of common Google problems)
~Poorservice: "Technical Support" was why I was trying to call.
~Poorservice's review of Google customer service
GetHuman: So how would you sum up your experience for GetHuman's Google 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.
~Poorservice: This is just one reason why I am canceling*google for my business. They hound the **** out of you to join, yet don't answer your call when you need to actually speak to a human. Why list phone numbers that don't work!! Your customer service *****! I will pass on the great service you supply!
GetHuman: Let's quantify your experience contacting Google. On a scale of 1 to 5, how easy is it go get help on a Google problem?
~Poorservice: 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?
~Poorservice: I'd give them a three out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
~Poorservice: For that I would say two out of five.
GetHuman: And finally- any advice for other Google customers?
~Poorservice: Call them early in the day or late. Don't forget any personal or account information you might need for Google to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Poorservice taken from his Google customer service problem that occurred on November 16th, 2017.