iYogi: *st wait time **-** minutes is rediculas.Second...
A iYogi customer review by GetHuman user ~klopcic8 from November 20th, 2017
Background on ~klopcic8's case
GetHuman: ~klopcic8 - can you tell our other iYogi customers when your case took place?
~klopcic8: Yes I can. It was evening, on November 18th.
GetHuman: Did you reach out to iYogi, and if so, how?
GetHuman: And which of these common iYogi customer issues best describes the reason you wanted to talk to them?
(Shows ~klopcic8 a list of common iYogi problems)
~klopcic8: "None of those really matches why I wanted to call iYogi that day." was why I was trying to call.
~klopcic8's review of iYogi customer service
GetHuman: So how would you sum up your experience for GetHuman's iYogi 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.
~klopcic8: *st wait time **-** minutes is rediculas.Secondly each tech i talk to tells me another story.No competitance as i was down for almost * days as several techs could not resolve the issue.i brought in one of my tech heads & he fixed it all within ** minutes!In my opinionan they should not be in Biz!!!
GetHuman: Let's quantify your experience contacting iYogi. On a scale of 1 to 5, how easy is it go get help on a iYogi problem?
~klopcic8: I'd give them a five 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?
~klopcic8: I'd give them a five out of five on communication.
GetHuman: And what about iYogi's ability to quickly and effectively address your problem?
~klopcic8: For that I would say two out of five.
GetHuman: And finally- any advice for other iYogi customers?
~klopcic8: Call them early in the day or late. Don't forget any personal or account information you might need for iYogi to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~klopcic8 taken from his iYogi customer service problem that occurred on November 18th, 2017.