Freedom Mobile: Can no longer reach customer service reps using...
A Freedom Mobile customer review by GetHuman user ~anonymous from November 28th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Freedom Mobile customers when your case took place?
~anonymous: Sure. It was late at night, on November 23rd.
GetHuman: Did you reach out to Freedom Mobile, and if so, how?
GetHuman: And which of these common Freedom Mobile customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Freedom Mobile problems)
~anonymous: "Update account information" was why I was trying to call.
~anonymous's review of Freedom Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's Freedom 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.
~anonymous: Can no longer reach customer service reps using *-*-*. Just goes into IVR ****. They used to be a good company but now they ****. Leaving for Rogers (who ***** less - if that is possible)
GetHuman: Let's quantify your experience contacting Freedom Mobile. On a scale of 1 to 5, how easy is it go get help on a Freedom Mobile problem?
~anonymous: 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?
~anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Freedom Mobile's ability to quickly and effectively address your problem?
~anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Freedom Mobile customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Freedom Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Freedom Mobile customer service problem that occurred on November 23rd, 2017.