Straight Talk: I am trying to switch my number over to a new p...
A Straight Talk customer review by GetHuman user ~Luke Harken from November 21st, 2017
Background on ~Luke Harken's case
GetHuman: ~Luke Harken - can you tell our other Straight Talk customers when your case took place?
~Luke Harken: Sure. It was middle of the night, on November 12th.
GetHuman: Did you reach out to Straight Talk, and if so, how?
GetHuman: And which of these common Straight Talk customer issues best describes the reason you wanted to talk to them?
(Shows ~Luke Harken a list of common Straight Talk problems)
~Luke Harken: "Transfer Phone Number" was why I was trying to call.
~Luke Harken's review of Straight Talk customer service
GetHuman: So how would you sum up your experience for GetHuman's Straight Talk 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.
~Luke Harken: I am trying to switch my number over to a new phone and you guys won't talk to me, I switched it over on friday night and you haven't got back to me and the new phone is still not working.
GetHuman: Let's quantify your experience contacting Straight Talk. On a scale of 1 to 5, how easy is it go get help on a Straight Talk problem?
~Luke Harken: I'd give them a two 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?
~Luke Harken: I'd give them a three out of five on communication.
GetHuman: And what about Straight Talk's ability to quickly and effectively address your problem?
~Luke Harken: For that I would say one out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
~Luke Harken: Call them early in the day or late. Don't forget any personal or account information you might need for Straight Talk to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Luke Harken taken from his Straight Talk customer service problem that occurred on November 12th, 2017.