I contacted Google today and spoke with ASHLEY...
A Google customer review by GetHuman user GetHuman-435935 from November 27th, 2017
Background on GetHuman-435935's case
GetHuman: GetHuman-435935 - can you tell our other Google customers when your case took place?
GetHuman-435935: Yes I can. It was afternoon, on November 20th.
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-435935 a list of common Google problems)
GetHuman-435935: "Technical support" was why I was trying to call.
GetHuman-435935'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-435935: I contacted Google today and spoke with ASHLEY in the Google Ads section. She talked over me.... did not listen and try to understand my issue and HANG UP ON ME.**She was HORRIBLE. Not what a Customer Service Rep should be. She had COMPLETE DISREGARD for me as a customer!!!!!!
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-435935: I'd give them a two 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-435935: I'd give them a one out of five on communication.
GetHuman: And what about Google's ability to quickly and effectively address your problem?
GetHuman-435935: For that I would say one out of five.
GetHuman: And finally- any advice for other Google customers?
GetHuman-435935: 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-435935 taken from his Google customer service problem that occurred on November 20th, 2017.