Una recensione del cliente Google da parte dell'utente GetHuman GetHuman-amsanto da novembre 30º, 2017
Background on GetHuman-amsanto's case
GetHuman: GetHuman-amsanto - can you tell our other Google customers when your case took place?
GetHuman-amsanto: Sure. It was morning, on novembre 26º.
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 GetHuman-amsanto a list of common Google problems)
GetHuman-amsanto: "Technical Support" was why I was trying to contact.
GetHuman-amsanto'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.
GetHuman: Can you tell the rest of us a bit more from what happened on 11/26/17?
GetHuman-amsanto: When I call someone on your google hangouts, they do not get a name on their phone. I would prefer if you could change how that worked by putting their name on the caller ID. This would help very much!
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?
GetHuman-amsanto: 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?
GetHuman-amsanto: 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?
GetHuman-amsanto: For that I would say three out of five.
GetHuman: And finally- any advice for other Google customers?
GetHuman-amsanto: 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 GetHuman-amsanto taken from his Google customer service problem that occurred on novembre 26º, 2017.