Skip across the chapter
Quota Playbook

CASL email opt-outs: 3 checks for sales managers

Quota Playbook Editorial Team · Published · 10 min read

Act on a CASL email opt-out without delay, and no later than 10 business days after receiving it.

Key takeaways

  • Log each request with its received date, action date, deadline and notes.
  • Review the address or page, message content and reply thread.
  • Check open requests for an owner and a recorded action.
  • Escalate uncertain requests to your compliance or legal team.

This post is for front-line managers who review a rep's follow-up emails to Canadian leads. It covers the deadline for acting on an opt-out, what to check in each follow-up, how to keep a record of the time, and what to do when a request is at risk.

A note on sources first. The guidance from Innovation, Science and Economic Development Canada says that "the information below is intended to provide basic background about the legislation, but should not be construed as legal advice" ( ISED, Getting consent to send email). Read this guide the same way. It explains the rules in the official text and turns them into a review routine. It does not replace advice from your compliance or legal team. Where this guide and that advice differ, follow the advice.

How long do you have to act on an opt-out?

The Act says effect must be given to a notice of withdrawal of consent "without delay, but in any event no later than 10 business days after receiving it" ( Department of Justice Canada, full text of the Act). Two parts of that wording matter. "Without delay" comes first, so the ten business days are an outer limit, not a target to plan around.

Your team should use the Act's term, "notice of withdrawal of consent," in its records.

What does "without delay" mean for a rep's queue?

Put stop requests at the front of the queue as soon as they are seen.

A rep who sees a stop request should not hold it for the next batch of follow-ups, and should not wait to see whether the lead writes again. Treat the request as a same-day item. Ask reps to send every stop request to the team log on the day it arrives, so the timing is answered by the record, not by memory.

Think of the queue as two lanes. Normal follow-up work can be scheduled. If a rep has to search three inboxes and two spreadsheets to learn whether a lead asked to stop, the request is already at risk. Keep the path simple: one place to log requests, one owner for the check, and one list of open items.

How long must the address or web page stay working?

The Act says the person who sends a commercial electronic message, and the person on whose behalf it is sent if different, "must ensure that the electronic address or World Wide Web page referred to in paragraph (1)(b) is valid for a minimum of 60 days after the message has been sent" ( Department of Justice Canada, full text of the Act). Both parties carry that duty. The quote points to paragraph (1)(b), so read the full text to see which address or page it describes. Do not guess from this guide.

Keep a short list of every address and page in use, with its owner and the date it was last confirmed.

Does a computer system in Canada have to be involved?

For a contravention of section 6, yes. The Act says a person contravenes section 6 "only if a computer system located in Canada is used to send or access the electronic message" ( Department of Justice Canada, full text of the Act).

"Only if" sets a condition that must be met before a contravention of section 6 can occur. A similar condition applies to section 7, with the words "send, route or access" ( Department of Justice Canada, full text of the Act). Do not stretch either condition into a general test for every email your team sends. Whether a particular message falls within these words is a question for compliance.

When a rep asks whether a follow-up falls under these conditions, send the question to compliance with the message, the recipient's location as far as your records show it, and the systems used to send it. The full picture in one message makes the question easier to answer.

What should you check in a rep's follow-up email?

Check three things on every follow-up: the address or web page it refers to, the content of the message, and whether any stop request in the thread was logged.

  • The address or page. Confirm the address or page referred to in paragraph (1)(b) meets the validity requirement above, and that the check is recent.
  • The content. Confirm the message follows the guidance on what to include in commercial electronic messages. The next section covers where that guidance is.
  • The thread. Read the lead's replies. Look for any reply that asks to stop receiving email, and check that it was logged the day it arrived.

The thread matters because a stop request can sit inside a reply the rep has already answered. A rep may answer the lead's question and never log the stop request. The manager's check is the second look.

Which guidance covers the content of a message?

The guidance from Innovation, Science and Economic Development Canada points to a bulletin for what to include in commercial electronic messages. The page says: "For more information about what to include in the commercial electronic messages your business sends, see the Compliance and Enforcement Information Bulletin CRTC 2012-548: Guidelines on the interpretation of the Electronic Commerce Protection Regulations (CRTC)" ( ISED, Getting consent to send email).

Save a copy in your review folder so every reviewer checks against the same text, and note the date you saved it.

How do you track the ten-business-day deadline?

Record the time each stop request reaches the business, and count ten business days forward from that date.

A shared spreadsheet is a workable start. Give it a column for each of these:

  • The date and time the request was received, and who received it.
  • The date the request was acted on, and who acted on it.
  • The deadline, ten business days after the received date.
  • Notes, such as the channel the request came through and any escalation.

Confirm with your compliance team how your organization counts business days, including whether holidays are excluded. Write that answer at the top of the log so everyone counts the same way. Review the log on a fixed schedule your team can keep, and check open items near their deadline first. Mark an item closed only when the action is recorded, not when the rep says it is done. For related recordkeeping, see timestamped call notes.

Illustrative example: a phone request

A rep receives a stop request by phone on a weekday and writes it down that day. The manager sees it at the next review, and the action is recorded well before the deadline counted from that day. The log makes the timing visible to everyone, which is its purpose. In an illustrative batch of 10 requests, the manager checks each recorded action and finds 0 open items.

Where can stop requests slip through?

They slip through when a request sits inside a reply to a follow-up, when it comes in by phone, or when it reaches a rep who did not send the original message.

A rep who reads a stop request inside a normal reply may treat it as part of the conversation and move on. Ask every rep to forward any message that mentions stopping, unsubscribing, or removal to the team log the day it arrives. A rep who takes a call should write the request down with the date, the time, and the lead's name.

Handoffs are another gap. When a lead is reassigned, the new rep may not know about an open request. A handoff note should list any open stop request, when it was received, and its deadline.

Finally, check any shared inbox your team uses. Route it into the same log, so requests from every channel end up in one place.

What should you do when a request is at risk?

Escalate it to your compliance or legal team the same day, and stop sending follow-ups to that lead until the request is resolved.

Write down who you escalated to and when. That record shows the team what was done and why, and it helps if the timing is questioned later.

Do not settle a question about the law on your own in the middle of a deadline. The compliance team is the right place for questions about what a request means, whether a message is covered, and what to send in reply. Your job is to make sure the question reaches them in time, with the facts written down. Keep the escalation note in the log next to the request, naming the request, the date it was received, the deadline, and the compliance contact who received the escalation.

What does a good review look like?

A good review checks the timing, the address, the content, and the log, and it leaves a short note on each follow-up it covers.

The manager then reads the content against the team's copy of the guidance, opens the thread, and looks for stop requests. Each one is checked against the log. If a request is open, the manager checks its deadline and owner.

A review note should say what was checked, what was found, and what was done. For example: "Address in email matches checked list, check is current. Content matches team copy of guidance. Thread has one stop request, logged the same day it arrived, action recorded before deadline." Short, factual notes are more useful later than a note that says the email looked fine. They also show patterns across reps, which gives you specific examples for coaching.

How do you handle a disagreement about a review?

Settle it against the Act's wording first, and bring it to compliance when the wording does not settle it.

A rep may dispute a finding, such as a finding that a reply was a stop request. Read the reply together and ask whether the lead was asking to stop receiving email. If so, log it and count the deadline from the day it was received. If it remains unclear, escalate it rather than deciding it in the review. Keep the conversation practical. The goal is an accurate log, not a contest over who missed what.

How often should the review happen?

Pick a fixed schedule and keep to it, because a review that happens only when someone remembers will miss requests.

Match the schedule to how often your team sends follow-ups, adjust it as request volume becomes clear, and note each change in the log.

What does the law not settle?

It does not answer every question about a particular message, lead, or sending setup.

When a question goes beyond the text, write it down, label it as an open question, and send it to compliance. Do not fill the gap with a guess that a rep then has to act on.

How do you coach reps on this routine?

Coach reps to bring any doubt about a request to you before they reply to the lead.

Keep coaching short and specific. Show a rep one real example from the log, walk through the three checks, and ask them to run the same checks on their next follow-up. In one-to-one meetings, note which requests were handled on time and which were not, and why. Praise the good catches too, especially when a rep flags a request others missed. Use your sales coaching agenda to keep that discussion focused.

Where to start this week

Today, pick one batch of recent follow-ups to Canadian leads and review it against the three checks above.

Then do three things. Set up the team log with the columns above. Agree with compliance how business days are counted. Once those are in place, the ten-business-day limit becomes a routine check rather than a surprise.

Keep the first review small. A batch you can finish in one sitting is easier to get right than a large one you rush.

Where can you get help with questions?

Start with your compliance or legal team for questions about your team's own messages.

The Office of the Privacy Commissioner of Canada says: "If you have a question, concerns about your privacy or want to file a complaint against an organization, we are here to help" ( Office of the Privacy Commissioner of Canada, Canada's anti-spam legislation).

Sources

  1. Product pricing and deal fields: 9 checks for coaching
  2. Sales text rules: 4 checks before a follow-up
  3. Service-dog questions: the 2 you may ask at the office

More plays