Slow speeds on fast connection. Not acceptable for how much I pay.

GetHuman690022's customer service issue with SuddenLink from May 2018

10 views
 | 
329 similar
 | 
0 following
Help with my SuddenLink issue
First: share to improve GetHuman690022's odds
Strength in numbers! Companies respond better when others are watching.
Next: our robot will wait on hold for GetHuman690022 to get a SuddenLink rep on the line!
Always use the GetHuman Phone tocall SuddenLink. We wait on hold and get a rep on the line for you faster and for free!
Before contacting them, items GetHuman690022 may need:
Account holder name, Account number, Billing address, Account phone number, and Last 4 digits of Social Security number
The issue in GetHuman690022's own words
The problem: Slow speeds on fast connection. Not acceptable for how much I pay.
GetHuman690022 did not yet indicate what SuddenLink should do to make this right.
I have an issue with SuddenLink too
How GetHuman690022 fixed the problem
We are waiting for GetHuman690022 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Prefer a step by step guide?
We've taken the time to write instructions for how to solve some of the most common SuddenLink customer problems.
How Do I Get Device Support from Suddenlink?How Do I Recover My Account Access to Suddenlink?
Do you have a customer issue as well?
We can help you get SuddenLink's attention and get better help faster. Tap below to get started.
Having SuddenLink issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid
Follow this issue
See how GetHuman690022 fixes it.
This email address isn't valid

SuddenLink

Customer service issue
Reported by GetHuman690022
May 16th, 2018 - a yr ago
I have an issue with SuddenLink too
Not resolved
Seen by 10 customers so far
Similar issue to 329 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman690022 started working on this issue
May 16th, 2018 4:07pm