FreedomPop: Waited on hold for ** mins, went through the pr...
A FreedomPop customer review by GetHuman user ~Devolved from November 24th, 2017
Background on ~Devolved's case
GetHuman: ~Devolved - can you tell our other FreedomPop customers when your case took place?
~Devolved: Yup. It was middle of the night, on November 20th.
GetHuman: Did you reach out to FreedomPop, and if so, how?
GetHuman: And which of these common FreedomPop customer issues best describes the reason you wanted to talk to them?
(Shows ~Devolved a list of common FreedomPop problems)
~Devolved: "Dispute a Charge" was why I was trying to call.
~Devolved's review of FreedomPop customer service
GetHuman: So how would you sum up your experience for GetHuman's FreedomPop 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.
~Devolved: Waited on hold for ** mins, went through the process of collecting all my information, and then told that I needed to be transferred to another department and my hold time would only be * mins. I was on hold for over **mins before I decided that I was just going to hang up.
GetHuman: Let's quantify your experience contacting FreedomPop. On a scale of 1 to 5, how easy is it go get help on a FreedomPop problem?
~Devolved: 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?
~Devolved: I'd give them a three out of five on communication.
GetHuman: And what about FreedomPop's ability to quickly and effectively address your problem?
~Devolved: For that I would say four out of five.
GetHuman: And finally- any advice for other FreedomPop customers?
~Devolved: Call them early in the day or late. Don't forget any personal or account information you might need for FreedomPop to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Devolved taken from his FreedomPop customer service problem that occurred on November 20th, 2017.