Anonymised, illustrative composite. A CRM “win-back” automation had no field for when implied consent expires — so it kept sending long after CASL's own clock had run out on part of the list.
At a glance
A team automated a quarterly “we miss you” email campaign against its full CRM database, segmenting on "no closed deal or open file in the last two years." The tool pulled 412 contacts and sent on a schedule, no human review of the list before each send — it had run the same way for three quarters without incident.
A post-send compliance spot-check, prompted by an unrelated unsubscribe complaint, pulled the actual consent dates against the send date of September 8, 2026:
The rule that actually decided which 61 contacts were the problem is the expiry itself, not the existence of the relationship. Express consent, by contrast, doesn't expire on its own — the the CRTC FAQ confirms the recipient must affirmatively withdraw it. Implied consent is different: it has a built-in shelf life, and the automation's segment logic had been built around when a relationship started, not when the implied-consent clock on it ran out. Those are not the same date, and only one of them is what s.6(1) actually tests against.
Worth flagging separately: the National DNCL's own existing-business-relationship exemption, for phone and ADAD-style calling, runs 18 months from a purchase and 6 months from an inquiry — different numbers again from CASL's 24 and 6. A 27-month-old purchase is outside both clocks by any channel; a contact between 18 and 24 months out is a live CASL email and a dead DNCL phone call at the same time. The two regimes do not share one number, and this team's tool wasn't built to check either.
No formal CRTC complaint was filed — the unsubscribe that triggered the review was just that, an unsubscribe. The team pulled all 61 stale contacts from the automated segment immediately, re-tagged them as requiring express consent before any further commercial message, and added a consent-expiry field to the CRM so the two clocks are tracked going forward rather than inferred from a relationship-start date.
CASL s.20(4) sets the ceiling on an administrative monetary penalty at $1,000,000 for an individual and $10,000,000 for "any other person" — a brokerage. That is a maximum a court or the CRTC could order, not a figure that was assessed here; nothing about this file suggests the full ceiling was ever in play for a first, self-corrected miss on 61 stale contacts. But the ceiling is the reason a quiet fix beats an ignored complaint — the same automation, left running unaudited for another few quarters, keeps adding more contacts past their consent window every quarter the CRM's relationship-start segmentation goes unreviewed.
The tell was the segment filter's own wording: "no closed deal in the last two years" is a description of a relationship's start, phrased as though it answers a question about the relationship's consent status. Any automated list-building rule that reads like a description of the client relationship, rather than a countdown from a specific dated event, is answering the wrong question — and CASL's s.10 windows are entirely about the dated event, not the relationship. The fix ended up looking a lot like moving stale contacts onto an express-consent basis rather than continuing to rely on an implied window that had already run out, and the team's marketing lead also flagged the segment against the National DNCL's own registration list before the next quarter's phone-based follow-up went out.
A 30-minute call is enough to tell you whether AI pays for itself here.