SuddenLink: Your phone lin e is horrible, oonce you get to...
A SuddenLink customer review by GetHuman user GetHuman-435571 from November 18th, 2017
Background on GetHuman-435571's case
GetHuman: GetHuman-435571 - can you tell our other SuddenLink customers when your case took place?
GetHuman-435571: Sure. It was middle of the night, on November 14th.
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 GetHuman-435571 a list of common SuddenLink problems)
GetHuman-435571: "Account Access" was why I was trying to call.
GetHuman-435571'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.
GetHuman-435571: Your phone lin e is horrible, oonce you get to where you want to go a busy signal comes on and then drops the call. Never did get a response. Emailing isn't much better So how do I resolve my issue?
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?
GetHuman-435571: 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?
GetHuman-435571: I'd give them a four out of five on communication.
GetHuman: And what about SuddenLink's ability to quickly and effectively address your problem?
GetHuman-435571: For that I would say one out of five.
GetHuman: And finally- any advice for other SuddenLink customers?
GetHuman-435571: 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 GetHuman-435571 taken from his SuddenLink customer service problem that occurred on November 14th, 2017.