Bell Canada: The man had a French accent but I had no troubl...
A Bell Canada customer review by GetHuman user ~Scott from October 30th, 2017
Background on ~Scott's case
GetHuman: ~Scott - can you tell our other Bell Canada customers when your case took place?
~Scott: Yeah. It was middle of the night, on October 25th.
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 ~Scott a list of common Bell Canada problems)
~Scott: "Cancel service" was why I was trying to call.
~Scott'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.
~Scott: The man had a French accent but I had no trouble and gave me a direct answer to my question. Bell Canada will give no direct contact * for their corporate office but he at least was able to provide me with an email address for them which is more than I had before I called and the gentleman was most courteous.
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?
~Scott: 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?
~Scott: I'd give them a five out of five on communication.
GetHuman: And what about Bell Canada's ability to quickly and effectively address your problem?
~Scott: For that I would say four out of five.
GetHuman: And finally- any advice for other Bell Canada customers?
~Scott: 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 ~Scott taken from his Bell Canada customer service problem that occurred on October 25th, 2017.