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

What to do in the age of Trump?

Well, that's the question of the day. If you're part of an organization that does advocacy work, rather than waiting to see what happens first, might as well get yourself ready, even if the details are sketchy still. Here's one opportunity that's ready for you now, message courtesy of Steve Anderson of OpenMedia.

OpenMedia, David Suzuki Foundation, SumOfUs and a range of other organizations are supporting a new shared set of civic engagement tools.

Vancity Community Foundation is providing some support to subsidize some of the cost of the tools to select values-aligned organizations that sign up before February 28th.

Interested? You can learn more or book a demo from here:

Here's some live examples of the tools you can take a look at:

1. Click to Call:

Check out this video of David Suzuki's d…

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…

CiviCRM's invoice_id field and why you should love the hash

I've been banging my head against a distracted cabal of developers who seem to think that a particular CiviCRM core design, which I'm invested in via my contributed code, is bad, and that it's okay to break it.

This post is my attempt to explain why it was a good idea in the first place.

The design in question is the use of a hash function to populate a field called 'invoice_id' in CiviCRM's contribution table. The complaint was that this string is illegible to humans, and not necessary. So a few years ago some code was added to core, that ignores the current value of invoice_id and will overwrite it, when a human-readable invoice is generated.

The complaint about human-readability of course is valid, and the label on the field is misleading, but the solution is terrible for several reasons I've already written about.

In this post, I'd like to explain why the use of the hash value in the invoice_id field is actually a brilliant idea and should be embrac…