Straight Talk: Rep Luis from Honduras was rude and unprofessio...
A Straight Talk customer review by GetHuman user GetHuman-427500 from November 22nd, 2017
Background on GetHuman-427500's case
GetHuman: GetHuman-427500 - can you tell our other Straight Talk customers when your case took place?
GetHuman-427500: Yes I can. 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 GetHuman-427500 a list of common Straight Talk problems)
GetHuman-427500: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-427500'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.
GetHuman-427500: Rep Luis from Honduras was rude and unprofessional. Refused to give me US corporate credentials. Couldn't resolve simple problem. HOOORRRIIIBBBLLLEEE!!!!!
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?
GetHuman-427500: 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?
GetHuman-427500: 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?
GetHuman-427500: For that I would say three out of five.
GetHuman: And finally- any advice for other Straight Talk customers?
GetHuman-427500: 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 GetHuman-427500 taken from his Straight Talk customer service problem that occurred on November 17th, 2017.