Google: I have wasted my entire day with ridiculous Goo...
A Google customer review by GetHuman user ~Tim Smyth from November 22nd, 2017
Background on ~Tim Smyth's case
GetHuman: ~Tim Smyth - can you tell our other Google customers when your case took place?
~Tim Smyth: Yeah. It was middle of the night, 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 ~Tim Smyth a list of common Google problems)
~Tim Smyth: "Lost phone" was why I was trying to call.
~Tim Smyth'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.
~Tim Smyth: I have wasted my entire day with ridiculous Google password menu on my cell phone I lost my computer terminal today. What is this nonsense. Call me or I'm suing. Suing big time. I'll do it if no one calls me. Call Tim Smyth *** *** **** NOW. NOW. NOW. If I hear from Google in three or four days you're in big big trouble.
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?
~Tim Smyth: I'd give them a four 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?
~Tim Smyth: I'd give them a five out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
~Tim Smyth: For that I would say one out of five.
GetHuman: And finally- any advice for other Google customers?
~Tim Smyth: 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 ~Tim Smyth taken from his Google customer service problem that occurred on November 19th, 2017.