my Qlink phone was droppin calls and wont turn on anymore after march** ****. the fcc...

GetHuman634638's customer service issue with Q Link Wireless from April 2018

2 views
 | 
5137 similar
 | 
0 following
Help with my Q Link Wireless issue
First: share to improve GetHuman634638's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman634638 may need:
PIN on Account, Name of Account Holder, Phone Number, Email on Account, Billing Address, and Last 4 of Social Security
GetHuman634638's next move: talk to Q Link Wireless when they open.
Q Link Wireless's call center is closed now. We will send GetHuman634638 a reminder to call them when they open. Nothing to do for now but wait!
The issue in GetHuman634638's own words
my Qlink phone was droppin calls and wont turn on anymore after march** ****. the fcc Id: srq-zten***, s*n: is ************ and phone number is ***-***-****. mailing address is *** s. buchannan street fremont, ohio
GetHuman634638 did not yet indicate what Q Link Wireless should do to make this right.
I have an issue with Q Link Wireless too
How GetHuman634638 fixed the problem
We are waiting for GetHuman634638 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get Q Link Wireless's attention and get better help faster. Tap below to get started.
Having Q Link Wireless issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Q Link Wireless email you?
This email address isn't valid
Follow this issue
See how GetHuman634638 fixes it.
This email address isn't valid

Q Link Wireless

Customer service issue
Reported by GetHuman634638
Apr 27th, 2018 - 5 mons ago
I have an issue with Q Link Wireless too
Not resolved
Seen by 2 customers so far
Similar issue to 5137 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman634638 started working on this issue
Apr 27th 4:12pm