Straight Talk: I've been waiting two weeks for them to change...
A Straight Talk customer review by GetHuman user ~darian barr from November 24th, 2017
Background on ~darian barr's case
GetHuman: ~darian barr - can you tell our other Straight Talk customers when your case took place?
~darian barr: Yes I can. It was morning, on November 19th.
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 ~darian barr a list of common Straight Talk problems)
~darian barr: "Overcharge/Strange charge" was why I was trying to call.
~darian barr'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.
~darian barr: I've been waiting two weeks for them to change my number and it still hasn't happened every time I get the same answer and my phone still isn't working this is the most awful customer service
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?
~darian barr: I'd give them a one 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?
~darian barr: 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?
~darian barr: For that I would say three out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
~darian barr: 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 ~darian barr taken from his Straight Talk customer service problem that occurred on November 19th, 2017.