CenturyLink: Century link cut a water line in a mobile home...
A CenturyLink customer review by GetHuman user ~ewd67 from November 24th, 2017
Background on ~ewd67's case
GetHuman: ~ewd67 - can you tell our other CenturyLink customers when your case took place?
~ewd67: Yup. It was afternoon, on November 17th.
GetHuman: Did you reach out to CenturyLink, and if so, how?
GetHuman: And which of these common CenturyLink customer issues best describes the reason you wanted to talk to them?
(Shows ~ewd67 a list of common CenturyLink problems)
~ewd67: "Technical Support" was why I was trying to call.
~ewd67's review of CenturyLink customer service
GetHuman: So how would you sum up your experience for GetHuman's CenturyLink 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.
~ewd67: Century link cut a water line in a mobile home park and could not guide me to any help in getting repair done while park was FLOODING. The worst organization ever....nothing was done with the first ELEVEN CALLS (**). Finally, a gracious lady named Terry said she would make an honest effort. Here's hoping
GetHuman: Let's quantify your experience contacting CenturyLink. On a scale of 1 to 5, how easy is it go get help on a CenturyLink problem?
~ewd67: I'd give them a three 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?
~ewd67: I'd give them a four out of five on communication.
GetHuman: And what about CenturyLink's ability to quickly and effectively address your problem?
~ewd67: For that I would say three out of five.
GetHuman: And finally- any advice for other CenturyLink customers?
~ewd67: Call them early in the day or late. Don't forget any personal or account information you might need for CenturyLink to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ewd67 taken from his CenturyLink customer service problem that occurred on November 17th, 2017.