Straight Talk: Called * times each time on phone tech for ** t...
A Straight Talk customer review by GetHuman user ~Rherring from November 26th, 2017
Background on ~Rherring's case
GetHuman: ~Rherring - can you tell our other Straight Talk customers when your case took place?
~Rherring: Yes. It was afternoon, on November 17th.
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 ~Rherring a list of common Straight Talk problems)
~Rherring: "SIM Card Transfer" was why I was trying to call.
~Rherring'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.
~Rherring: Called * times each time on phone tech for ** to * hour and problem still isn't fixed. I can't connect to internet and after everything the computer tells them to check they tell me they can't replace the phone and then they hang up on me.
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?
~Rherring: I'd give them a three 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?
~Rherring: I'd give them a four out of five on communication.
GetHuman: And what about Straight Talk's ability to quickly and effectively address your problem?
~Rherring: For that I would say one out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
~Rherring: 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 ~Rherring taken from his Straight Talk customer service problem that occurred on November 17th, 2017.