Schools Training

Canada’s Anti-Spam Law: Too Tough for Good Business?

1 APR 2014

This week, the Canadian Tourism College blog examines Canada’s new anti-spam legislation, set to become law as of July 1. The law lays out a strict set of rules that will govern how businesses market products and services to contacts. Collecting data on new and prospective clients is central to growing and maintaining a successful business – companies routinely use this information to send out targeted and mass commercial messages, hoping to expand their consumer base and promote their brand. The blog post, Canada’s Anti-Spam Law: Too Tough for Good Business? reflects that over-zealous database building means

 we end up on lists we never signed up for. We’re bombarded by commercial messaging, our email inboxes exploding with undesirable offers – our private time invaded by telemarketing pitches. Following the example of several other countries, Canada has developed new anti-spam legislation intended to crack down on unsolicited electronic promotion. Tough and somewhat convoluted, the policy comes into effect on July 1. We’ll look at how it will impact the travel and tourism industry, how businesses connect with consumers, and how contact data is exploited.

Critics suggest that the anti-spam law is too stringent – that Canada, anxious to keep up with numerous other countries who have already implemented similar legislation, has developed an unfair policy. There is indeed a very long list of dos and don’ts that companies will need to examine in order to prepare themselves for compliance. Some experts suggest hiring an anti-spam professional to vet contacts list and ensure consent has been obtained for various types of electronic commercial messages – this could be everything from a Facebook page, to tweets, emails, newsletters, telephone calls, and even text messages sent out to contacts for promotional purposes.


Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in /home/schoolstraining/public_html/wp-includes/taxonomy.php on line 1531