Straight Talk: I have tried *-* different numbers to contact s...
A Straight Talk customer review by GetHuman user ~Nicholas DeClue from November 17th, 2017
Background on ~Nicholas DeClue's case
GetHuman: ~Nicholas DeClue - can you tell our other Straight Talk customers when your case took place?
~Nicholas DeClue: Yeah. It was late at night, on November 13th.
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 ~Nicholas DeClue a list of common Straight Talk problems)
~Nicholas DeClue: "Service problem" was why I was trying to call.
~Nicholas DeClue'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.
~Nicholas DeClue: I have tried *-* different numbers to contact someone and every number I have tried has told me to hang up and call **** which is not straight talk
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?
~Nicholas DeClue: I'd give them a four 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?
~Nicholas DeClue: I'd give them a one out of five on communication.
GetHuman: And what about Straight Talk's ability to quickly and effectively address your problem?
~Nicholas DeClue: For that I would say one out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
~Nicholas DeClue: 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 ~Nicholas DeClue taken from his Straight Talk customer service problem that occurred on November 13th, 2017.