Google: they were curtious. had to call * times in one...
Una recensione del cliente Google da parte dell'utente GetHuman ~noreen landowski da novembre 24º, 2017
Background on ~noreen landowski's case
GetHuman: ~noreen landowski - can you tell our other Google customers when your case took place?
~noreen landowski: Yup. It was afternoon, on novembre 16º.
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 ~noreen landowski a list of common Google problems)
~noreen landowski: "Update account information" was why I was trying to call.
~noreen landowski'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.
~noreen landowski: they were curtious. had to call * times in one night. they had me try several steps while on the phone. but i still have the same problem.cant watch the movies i paid for. not happy about that.
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?
~noreen landowski: 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?
~noreen landowski: I'd give them a two out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
~noreen landowski: For that I would say three out of five.
GetHuman: And finally- any advice for other Google customers?
~noreen landowski: 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 ~noreen landowski taken from his Google customer service problem that occurred on novembre 16º, 2017.