SuddenLink: Did NOT work - called at *:** ET (says ** hours...
A SuddenLink customer review by GetHuman user ~Suddenlinkbitesit from November 24th, 2017
Background on ~Suddenlinkbitesit's case
GetHuman: ~Suddenlinkbitesit - can you tell our other SuddenLink customers when your case took place?
~Suddenlinkbitesit: Yeah. It was morning, on November 19th.
GetHuman: Did you reach out to SuddenLink, and if so, how?
GetHuman: And which of these common SuddenLink customer issues best describes the reason you wanted to talk to them?
(Shows ~Suddenlinkbitesit a list of common SuddenLink problems)
~Suddenlinkbitesit: "Transfer Service" was why I was trying to call.
~Suddenlinkbitesit's review of SuddenLink customer service
GetHuman: So how would you sum up your experience for GetHuman's SuddenLink 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.
~Suddenlinkbitesit: Did NOT work - called at *:** ET (says ** hours, guess not). Told me to press zero, then when I did, recorded voice said, "I can't hear anything. We can't help you. Goodbye!" and hung up.
GetHuman: Let's quantify your experience contacting SuddenLink. On a scale of 1 to 5, how easy is it go get help on a SuddenLink problem?
~Suddenlinkbitesit: I'd give them a one 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?
~Suddenlinkbitesit: I'd give them a one out of five on communication.
GetHuman: And what about SuddenLink's ability to quickly and effectively address your problem?
~Suddenlinkbitesit: For that I would say four out of five.
GetHuman: And finally- any advice for other SuddenLink customers?
~Suddenlinkbitesit: Call them early in the day or late. Don't forget any personal or account information you might need for SuddenLink to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Suddenlinkbitesit taken from his SuddenLink customer service problem that occurred on November 19th, 2017.