Simple Mobile: I called with a simple question, about a routi...
A Simple Mobile customer review by GetHuman user GetHuman-323108 from November 4th, 2017
Background on GetHuman-323108's case
GetHuman: GetHuman-323108 - can you tell our other Simple Mobile customers when your case took place?
GetHuman-323108: Yup. It was morning, on October 28th.
GetHuman: Did you reach out to Simple Mobile, and if so, how?
GetHuman: And which of these common Simple Mobile customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-323108 a list of common Simple Mobile problems)
GetHuman-323108: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-323108's review of Simple Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's Simple Mobile 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-323108: I called with a simple question, about a routine text message announcing service disconnection after I bought minutes. It was just a routine message, all fine.
GetHuman: Let's quantify your experience contacting Simple Mobile. On a scale of 1 to 5, how easy is it go get help on a Simple Mobile problem?
GetHuman-323108: I'd give them a two 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-323108: I'd give them a three out of five on communication.
GetHuman: And what about Simple Mobile's ability to quickly and effectively address your problem?
GetHuman-323108: For that I would say four out of five.
GetHuman: And finally- any advice for other Simple Mobile customers?
GetHuman-323108: Call them early in the day or late. Don't forget any personal or account information you might need for Simple Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-323108 taken from his Simple Mobile customer service problem that occurred on October 28th, 2017.