GoDaddy: You people ****!!!! I spent ** minutes on the p...
A GoDaddy customer review by GetHuman user ~scribe8491 from November 23rd, 2017
Background on ~scribe8491's case
GetHuman: ~scribe8491 - can you tell our other GoDaddy customers when your case took place?
~scribe8491: Yup. It was afternoon, on November 14th.
GetHuman: Did you reach out to GoDaddy, and if so, how?
GetHuman: And which of these common GoDaddy customer issues best describes the reason you wanted to talk to them?
(Shows ~scribe8491 a list of common GoDaddy problems)
~scribe8491: "Lower my bill" was why I was trying to call.
~scribe8491's review of GoDaddy customer service
GetHuman: So how would you sum up your experience for GetHuman's GoDaddy 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.
~scribe8491: You people ****!!!! I spent ** minutes on the phone with your rep to stop auto-renewal. We wet through the process step-by-step and I was assured the process had been copleted. Now you people have the BALLS to send me another auto renewal notice!! And do you think I can get in touch with you??? **** no!!!!
GetHuman: Let's quantify your experience contacting GoDaddy. On a scale of 1 to 5, how easy is it go get help on a GoDaddy problem?
~scribe8491: 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?
~scribe8491: I'd give them a one out of five on communication.
GetHuman: And what about GoDaddy's ability to quickly and effectively address your problem?
~scribe8491: For that I would say five out of five.
GetHuman: And finally- any advice for other GoDaddy customers?
~scribe8491: Call them early in the day or late. Don't forget any personal or account information you might need for GoDaddy to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~scribe8491 taken from his GoDaddy customer service problem that occurred on November 14th, 2017.