Skip to main content

Bell Canada: A study in bad business practices, or Kafka lives.

I had an account with Bell Canada for more than 10 years, both phone and internet. I endured some pretty steep prices, un-requested changes of service with price hikes, and endlessly irritating calls to their automated machines.

I'm currently on hold trying to unravel their latest, truly, incredibly, bad business practice.

It started earlier this year, when I tried to combine my bills that had been up until then separated. I didn't care too much except that I would get these irritating advertisements for cheap internet and when I phoned them up, they'd tell me I wasn't eligible since I was already a customer.

After combining my bills (that was the only way they could give me a cheaper service), it got worse and the last straw was when they charged me $.20/minute for a call to Spain. Apparently not covered with my normal long-distance plan to which I'd enrolled, they decided they could just charge any old extorsionist rate... But even aside from that, they had made several other errors, and after sorting them all out, I was transferred to collections who told me I had to pay up right away or get disconnected.

Anyway, I go tired of it all, so I switched both services to TekSavvy (who use Bell's infrastructure) and have been very happy since.

Unfortunately, even after paying off the existing bill (unhappily), the story wasn't over. A month after quitting, I got a bill saying they owed me some money. Then I got another one saying we were even. They another month later I got one saying I owned them $30. I ignored it like a bad dream, assuming I would get another random bill the next month.

Unfortunately, if you ignore your bill at Bell, it goes to collections. That means I started getting calls to pay my bill. When I explained the situation, they told me they couldn't help me, I had to call back and ask for billing. When I did that, I followed the various prompts and ended up again at collections. The friendly guy there explained that in order to get to billing, I had to ignore all the voice prompts and just keep pressing 0 (presumably special treatment because I had cancelled my service?). I explained that this was all a little too much like Kafka and gave up in rage for the day.

Since then I've had a number of further calls from collections, all to the same effect - they can only ask me for money and can't even tell me why I'm being billed.

Finally last week I got a collections notice and today I decided I'd better just deal with it.

So today I phone up and didn't follow the voice prompts. I did tell them it was for internet, since that's what the collections person I talked to had told me. I talked to one nice person for half an hour before she told me she couldn't do anything, so she put me through to Lavinia, who is a supervisor there. After explaining all over again, she decided that the charge was actually for the phone, not for the internet, and therefore couldn't help me either, and I'm now waiting on hold for a phone service billing supervisor.

Ah, now Lisa's got the ball. She's just taken another 15 minutes of time to get up to speed and has put me on hold again. Don't you hate when they put you on hold and blast music at you? This one's a quiet hold, but the first one I talked to today apologized because she couldn't mute the music when she put me on hold, and it was twice as loud as her voice. Poor Lisa's going to go through all the bills again and try and figure out if that $30 is valid (from her accounting perspective). I can only write my blog in the interim as a kind of therapy so I don't ruin my day completely.

A few minutes later ... a final update. Lisa is back on the line and tells me the charge was for an early termination fee and that she would waive it. Now I appreciate that, but that's a nice fiction between the two of us. The truth is that this story should never have happened, but unless someone at Bell is paying attention, it'll all happen over again, again again.

Thanks Lisa and Lavinia!

Popular posts from this blog

The Tyee: Bricolage and Drupal Integration

The Tyee is a site I've been involved with since 2006 when I wrote the first, 4.7 version of a Drupal module to integrate Drupal content into a static site that was being generated from bricolage. About a year ago, I met with Dawn Buie and Phillip Smith and we mapped out a number of ways to improve the Drupal integration on the site, including upgrading the Drupal to version 5 from 4.7. Various parts of that grand plan have been slowly incorporated into the site, but as of next week, there'll be a big leap forward that coincides with a new design [implemented in Bricolage by David Wheeler who wrote and maintains Bricolage] as well as a new Drupal release of the Bricolage integration module . Plans Application integration is tricky, and my first time round had quite a few issues. Here's a list of the improvements in the latest version: File space separation. Before, Drupal was installed in the apache document root, which is where bricolage was publishing it's co...

A Strange Passion for Security

I'm not a computer security expert, but it's been part of my work for many years, in different forms.  A very long time ago, a friend hired me to write up a primer for internet security, and ever since then it's been a theme that's sat in the background and pops up every now and then . But lately, it's started to feel like more than a theme, and but indeed a passion. You may consider computer and internet security to be a dry subject, or maybe you imagine feelings of smugness or righteousness, but "passion" is the right word for what I'm feeling. Here's google's definition: Passion: 1. a strong and barely controllable emotion. 2. the suffering and death of Jesus. Okay, let's just go with number 1. for now. If you followed my link above to other posts about security, you'll notice one from eight years ago where I mused on the possibility of the discovery of a flaw in how https works. Weirdly enough, a flaw in https was discovered shortly...

Orchestrating Drupal + CiviCRM containers into a working site: describing the challenge

In my previous posts, I've provided my rationale for making use of Docker and the microservices model for a boutique-sized Drupal + CiviCRM hosting service. I've also described how to build and maintain images that could be used for the web server (micro) service part of such a service. The other essential microservice for a Drupal + CiviCRM website is a database, and fortunately, that's reasonably standard. Here's a project that minimally tweaks the canonical Mariadb container by adding some small configuration bits:  https://github.com/BlackflySolutions/mariadb That leaves us now with the problem of "orchestration", i.e. how would you launch a collection of such containers that would serve a bunch of Drupal + CiviCRM sites. More interestingly, can we serve them in the real world, over time, in a way that is sustainable? i.e. handle code updates, OS updates, backups, monitoring, etc? Not to mention the various crons that need to run, and how about things ...