Bell canada *****! i spent more than an hour to...
A Bell Canada customer review by GetHuman user GetHuman-201125 from November 6th, 2017
Background on GetHuman-201125's case
GetHuman: GetHuman-201125 - can you tell our other Bell Canada customers when your case took place?
GetHuman-201125: Yes I can. It was morning, on October 30th.
GetHuman: Did you reach out to Bell Canada, and if so, how?
GetHuman: And which of these common Bell Canada customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-201125 a list of common Bell Canada problems)
GetHuman-201125: "Setup service" was why I was trying to call.
GetHuman-201125's review of Bell Canada customer service
GetHuman: So how would you sum up your experience for GetHuman's Bell Canada 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-201125: Bell canada *****! i spent more than an hour to get hold of someone from canada. I dont want to talk to somebody from the Philippines, costa rica or india. I am paying a canadian service, give me a canadian!
GetHuman: Let's quantify your experience contacting Bell Canada. On a scale of 1 to 5, how easy is it go get help on a Bell Canada problem?
GetHuman-201125: 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-201125: I'd give them a one out of five on communication.
GetHuman: And what about Bell Canada's ability to quickly and effectively address your problem?
GetHuman-201125: For that I would say one out of five.
GetHuman: And finally- any advice for other Bell Canada customers?
GetHuman-201125: Call them early in the day or late. Don't forget any personal or account information you might need for Bell Canada to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-201125 taken from his Bell Canada customer service problem that occurred on October 30th, 2017.