Straight Talk: they took my minutes away before they ran out...
A Straight Talk customer review by GetHuman user ~tyler huckabey from November 20th, 2017
Background on ~tyler huckabey's case
GetHuman: ~tyler huckabey - can you tell our other Straight Talk customers when your case took place?
~tyler huckabey: Yes I can. It was evening, on November 15th.
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 ~tyler huckabey a list of common Straight Talk problems)
~tyler huckabey: "Account access" was why I was trying to call.
~tyler huckabey'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.
~tyler huckabey: they took my minutes away before they ran out. whats the deal with that?!?! im tired of getting poor cell service, when i have perfectly good signal where i live.
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?
~tyler huckabey: 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?
~tyler huckabey: I'd give them a two out of five on communication.
GetHuman: And what about Straight Talk's ability to quickly and effectively address your problem?
~tyler huckabey: For that I would say five out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
~tyler huckabey: 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 ~tyler huckabey taken from his Straight Talk customer service problem that occurred on November 15th, 2017.