Earthlink: I was able to get through quickly, called about...
A Earthlink customer review by GetHuman user ~LR from November 20th, 2017
Background on ~LR's case
GetHuman: ~LR - can you tell our other Earthlink customers when your case took place?
~LR: Yes. It was morning, on November 12th.
GetHuman: Did you reach out to Earthlink, and if so, how?
GetHuman: And which of these common Earthlink customer issues best describes the reason you wanted to talk to them?
(Shows ~LR a list of common Earthlink problems)
~LR: "Cancel service" was why I was trying to call.
~LR's review of Earthlink customer service
GetHuman: So how would you sum up your experience for GetHuman's Earthlink 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.
~LR: I was able to get through quickly, called about * pm on a Friday. The representative was pleasant but somewhat difficult to understand. I called to cancel my service because my DSL was slow and over-priced at $**. I have set up DSL service with Sonic.Net and get full phone service for the same price. It was interesting that he made several offers to upgrade my service for a lower price.
GetHuman: Let's quantify your experience contacting Earthlink. On a scale of 1 to 5, how easy is it go get help on a Earthlink problem?
~LR: 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?
~LR: I'd give them a one out of five on communication.
GetHuman: And what about Earthlink's ability to quickly and effectively address your problem?
~LR: For that I would say four out of five.
GetHuman: And finally- any advice for other Earthlink customers?
~LR: Call them early in the day or late. Don't forget any personal or account information you might need for Earthlink to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~LR taken from his Earthlink customer service problem that occurred on November 12th, 2017.