Google: there was no response, and i'm very, very furi...
A Google customer review by GetHuman user GetHuman-432642 from November 24th, 2017
Background on GetHuman-432642's case
GetHuman: GetHuman-432642 - can you tell our other Google customers when your case took place?
GetHuman-432642: Yeah. It was morning, on November 19th.
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-432642 a list of common Google problems)
GetHuman-432642: "Complaint" was why I was trying to call.
GetHuman-432642'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-432642: there was no response, and i'm very, very furious. the system doesn't let me to access my google account, and i can't write a note to google, and can't contact to them. its so unfair.. i just want my account back. it is a huge deal, or something?! somebody do something!
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-432642: 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?
GetHuman-432642: 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-432642: For that I would say five out of five.
GetHuman: And finally- any advice for other Google customers?
GetHuman-432642: 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 GetHuman-432642 taken from his Google customer service problem that occurred on November 19th, 2017.