Family Mobile: Someone posted a payment to their phone bill ov...
A Family Mobile customer review by GetHuman user ~KM from November 24th, 2017
Background on ~KM's case
GetHuman: ~KM - can you tell our other Family Mobile customers when your case took place?
~KM: Yes I can. It was morning, on November 21st.
GetHuman: Did you reach out to Family Mobile, and if so, how?
GetHuman: And which of these common Family Mobile customer issues best describes the reason you wanted to talk to them?
(Shows ~KM a list of common Family Mobile problems)
~KM: "Technical or service issue" was why I was trying to call.
~KM's review of Family Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's Family 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.
~KM: Someone posted a payment to their phone bill over the phone. The problem was they used MY bank information. Family mobile did not verify and are not willing to help at all since they need the account number and phone number to the account. Clearly I don't have it. horrible service, really bad connection.
GetHuman: Let's quantify your experience contacting Family Mobile. On a scale of 1 to 5, how easy is it go get help on a Family Mobile problem?
~KM: 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?
~KM: I'd give them a one out of five on communication.
GetHuman: And what about Family Mobile's ability to quickly and effectively address your problem?
~KM: For that I would say one out of five.
GetHuman: And finally- any advice for other Family Mobile customers?
~KM: Call them early in the day or late. Don't forget any personal or account information you might need for Family Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~KM taken from his Family Mobile customer service problem that occurred on November 21st, 2017.