Bell Mobility: Overfilled a total of $** in *.* months. * phon...
A Bell Mobility customer review by GetHuman user GetHuman-205622 from November 10th, 2017
Background on GetHuman-205622's case
GetHuman: GetHuman-205622 - can you tell our other Bell Mobility customers when your case took place?
GetHuman-205622: Yeah. It was evening, on November 8th.
GetHuman: Did you reach out to Bell Mobility, and if so, how?
GetHuman: And which of these common Bell Mobility customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-205622 a list of common Bell Mobility problems)
GetHuman-205622: "Update account information" was why I was trying to call.
GetHuman-205622's review of Bell Mobility customer service
GetHuman: So how would you sum up your experience for GetHuman's Bell Mobility 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-205622: Overfilled a total of $** in *.* months. * phone calls to get it fixed. The problem was in no way my fault. No apology, no compensation.... I'm out
GetHuman: Let's quantify your experience contacting Bell Mobility. On a scale of 1 to 5, how easy is it go get help on a Bell Mobility problem?
GetHuman-205622: I'd give them a one 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-205622: I'd give them a one out of five on communication.
GetHuman: And what about Bell Mobility's ability to quickly and effectively address your problem?
GetHuman-205622: For that I would say four out of five.
GetHuman: And finally- any advice for other Bell Mobility customers?
GetHuman-205622: Call them early in the day or late. Don't forget any personal or account information you might need for Bell Mobility to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-205622 taken from his Bell Mobility customer service problem that occurred on November 8th, 2017.