CenturyLink: having an awful time after a botched move, stil...
CenturyLink Ulasan pelanggan oleh pengguna GetHuman ~josiejaymkay dari November 28, 2017
Background on ~josiejaymkay's case
GetHuman: ~josiejaymkay - can you tell our other CenturyLink customers when your case took place?
~josiejaymkay: Yes. It was afternoon, on November 25.
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 ~josiejaymkay a list of common CenturyLink problems)
~josiejaymkay: "Service problem" was why I was trying to call.
~josiejaymkay'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.
~josiejaymkay: having an awful time after a botched move, still trying to get all my payments to where they're supposed to be. my service got cancelled when I moved and it has been a nightmare months later trying to get this right.
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?
~josiejaymkay: 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?
~josiejaymkay: I'd give them a one out of five on communication.
GetHuman: And what about CenturyLink's ability to quickly and effectively address your problem?
~josiejaymkay: For that I would say four out of five.
GetHuman: And finally- any advice for other CenturyLink customers?
~josiejaymkay: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk CenturyLink mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~josiejaymkay taken from his CenturyLink customer service problem that occurred on November 25, 2017.