Treat CASL B2B cold email as a qualification exercise. Classify the message, verify the organizational relationship, identify the activity it concerns, and choose the consent basis. A company email address does not settle the question. CASL has no blanket business-to-business exemption.1 The B2B route for messages between organizations depends on a relationship between them and the recipient organization's activities.2 If you cannot explain why the route fits, pause the send and use a consent basis.
Use the decision path
Run these checks in order. The first checks establish whether the exemption fits; the later checks confirm that a permitted send meets its own requirements.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Classify | what the message is and where it is going | Does this message encourage commercial activity? |
| Test the relationship | whether a specific organization-to-organization route fits | What relationship connects the organizations? |
| Choose the route | whether consent or an exemption supports the send | What is the basis for sending this message? |
| Check the draft | whether the message is ready for the route you chose | Can the recipient identify the sender and stop future messages? |
| Record the basis | whether you can explain the decision later | Where is the consent or exemption reasoning recorded? |
Answer each question in plain language before moving on. Calling the message "B2B" starts the check; it does not finish it.
Classify the message
Start with the message's content and destination. The recipient's company does not determine the classification by itself.
CASL regulates commercial electronic messages, meaning electronic messages that encourage participation in a commercial activity and are sent to or accessed from a computer system in Canada; a cold sales email falls squarely within that definition.3 Read the draft for its commercial purpose, including whether it invites participation in an activity or promotes an offer.
Ask what the recipient is being invited to do and where the message will be sent or accessed. Describe the message without relying on the fact that the recipient works for a business.
Test the organization-to-organization route
The exemption depends on the relationship between the organizations and the subject of the message. Check both.
The B2B rule covers messages within an organization sent by an employee, representative, consultant, or franchisee to another employee, representative, consultant, or franchisee of that organization in connection with its activities, as well as messages to another organization when the organizations have a relationship and the message concerns the recipient organization's activities.2 Organization-to-organization communications related to the organizations' core activities are described as outside CASL.4
Ask these questions before moving on:
- Is the sender and recipient connection inside one organization, or between separate organizations?
- If the organizations are separate, what relationship connects them?
- What activity of the recipient organization does the message concern?
- How does the message relate to the organizations' core activities?
Write the answers beside the send record. Move on when one supported route is clear and the message subject fits it. If the relationship exists only in your team's description of the account, leave the exemption unresolved.
Check the consent route
An exemption and consent are separate ways to support a send. An existing business relationship needs its own check.
A compliant send requires express or implied consent, or an applicable listed exemption.5 Express consent is a positive, informed opt-in.6 An existing business relationship can create an exception to the consent requirements when it arises from specified activity between the sender and recipient during the two years before the message is sent.7
Ask what permission exists, how it arose, and whether it belongs to this recipient and this type of message. If the answer rests on an existing business relationship, record the activity that created it and the timing. If you cannot establish consent or a precise exemption, stop the send while you resolve the gap.
Check the draft
After choosing a route, inspect the actual email. Classification and message construction are separate checks.
Certain commercial electronic messages are entirely exempt from obtaining consent and from CASL's form and content requirements.8 When your route does not clearly fall within that category, prepare the message against the ordinary requirements.
The message must identify the sender and anyone on whose behalf it is sent, with valid contact information.9 It must also contain a working unsubscribe mechanism.10 Missing one of these three requirements makes the message non-compliant even when the other two are present.11
Check the sender line, the identity of any represented business, the contact details, and the unsubscribe path in the version that will actually go out. Test the unsubscribe path before sending. Move on when each item works in the draft, or when you have established that a full exemption removes those requirements.
Keep proof of the decision
Keep the exemption or consent basis clear enough for someone else to inspect. The record should explain the route, the supporting facts, and the message covered by the decision.
Under CASL, the sender must be able to show permission to email, and the burden of proving that permission sits with the sender if a regulator asks.12 Create a process that records what type of consent you received, how you received it, and when you received it.13
For consent records, capture the initial consent date, upgraded consent date, consent level, and consent source. An IP address is recommended and is not required.14 For an exemption record, use the same discipline: state the relationship, the recipient organization's activity, and why the message fits the route.
What not to do
- Do not send an unconsented commercial message because you assumed the B2B exemption applied.15
- Do not ask every supplier and client for opt-in consent before checking whether a valid exemption applies.16
- Do not send an email asking for consent while assuming that the request sits outside CASL. Asking for consent by email is itself a commercial email covered by CASL.17
Before the next send, write the exemption basis in one sentence, name the relationship, and identify the recipient activity it concerns. If that sentence stays vague, use a documented consent route or stop and review the email program with legal counsel.18 Make the send decision from facts you can produce instead of from the B2B label.