I've lost ***** emails because Google won't ans...
Una recensione del cliente Google da parte dell'utente GetHuman ~Randy O. Bowling da novembre 28º, 2017
Background on ~Randy O. Bowling's case
GetHuman: ~Randy O. Bowling - can you tell our other Google customers when your case took place?
~Randy O. Bowling: Yup. It was evening, on novembre 19º.
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 ~Randy O. Bowling a list of common Google problems)
~Randy O. Bowling: "Recover Account" was why I was trying to call.
~Randy O. Bowling'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.
~Randy O. Bowling: I've lost ***** emails because Google won't answer with a human. WHY. If I could get on the internet, WHY would I need to contact them. Contact us via the internet is run around. Hope Google goes bankrupt. It's RICO rip off!!!
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?
~Randy O. Bowling: 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?
~Randy O. Bowling: I'd give them a one out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
~Randy O. Bowling: For that I would say two out of five.
GetHuman: And finally- any advice for other Google customers?
~Randy O. Bowling: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Google sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~Randy O. Bowling taken from his Google customer service problem that occurred on novembre 19º, 2017.