tracfone sent me a new SIM and I started the process of getting my number transferred l...

GetHuman2111106's customer service issue with Tracfone from March 2019

7 views
 | 
4450 similar
 | 
0 following
Help with my Tracfone issue
How did GetHuman2111106 do it?
Waiting to hear how GetHuman2111106 fixed the problem to share with other customers.
The issue in GetHuman2111106's own words
tracfone sent me a new SIM and I started the process of getting my number transferred last week. Was told to call back in * minutes. tried. tried again. Cannot speak with human, friends cannot call me. Current phone a ZTE Z***VL. Does not receive here in the redwood forest worth a ****. LG worked great! Phone number (***)***-****. Phone I am transferring this phone number to is an LG *** GB, last working ****, number was (***)***-****. You sent new SIM * *** *** *** *** ***. ref* *** *** ****. * Another * *** ***?
GetHuman2111106 did not yet indicate what Tracfone should do to make this right.
I have an issue with Tracfone too
How GetHuman2111106 fixed the problem
We are waiting for GetHuman2111106 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 Tracfone's attention and get better help faster. Tap below to get started.
Having Tracfone 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 GetHuman2111106 fixes it.
This email address isn't valid

Tracfone

Customer service issue
Reported by GetHuman2111106
Mar 12th, 2019 - 5 mons ago
I have an issue with Tracfone too
Fixed
Seen by 7 customers so far
Similar issue to 4450 others
0 customers following this
Follow this issue to see how it gets fixed
Items needed
Account holder name
Serial number of phone
Phone number
Email address
Billing address
Date of Birth
Timeline
GetHuman2111106 started working on this issue
Mar 12th 1:01pm
GetHuman2111106 confirmed the issue is fixed. Hooray!
Mar 12th 1:02pm