Google: I have been on hold over * hours now! I called...
A Google customer review by GetHuman user ~beyond frustrated from November 20th, 2017
Background on ~beyond frustrated's case
GetHuman: ~beyond frustrated - can you tell our other Google customers when your case took place?
~beyond frustrated: Sure. It was afternoon, on November 15th.
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 ~beyond frustrated a list of common Google problems)
~beyond frustrated: "Refund or Suspicious Charges" was why I was trying to call.
~beyond frustrated'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.
~beyond frustrated: I have been on hold over * hours now! I called at **:** Mountain time and its *:**pm now. I have them on speaker phone and am doing my chores. I think they must only have one person working, or no one today.
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?
~beyond frustrated: 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?
~beyond frustrated: I'd give them a three out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
~beyond frustrated: For that I would say two out of five.
GetHuman: And finally- any advice for other Google customers?
~beyond frustrated: 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 ~beyond frustrated taken from his Google customer service problem that occurred on November 15th, 2017.