AI Dealership Calls & CASL/TCPA Compliance: What GMs Need to Know

If you Googled this topic, you're probably staring down one of two scenarios: either your dealer principal just heard something scary about AI calls and compliance at a 20 Group meeting, or your legal counsel raised a flag and now you're trying to figure out if an AI answering service is going to land your store in front of a regulator.

Let me give you the straight answer before we go deep: inbound AI-answered calls at a dealership are the lowest-risk category under both CASL and TCPA. The rules that trip people up — and that generate the big fines — are about outbound solicitation, not about answering a phone that a customer picked up and dialed themselves.

That said, 'lowest risk' doesn't mean 'no risk.' There are specific things you still need to get right, and I'll walk through all of them.

Why Most CASL and TCPA Fears About AI Calls Are Pointed at the Wrong Thing

CARL and TCPA are often lumped together in dealership compliance conversations, but they govern different channels and different countries. Getting them confused leads to either over-engineering your compliance setup or — worse — ignoring the rules that actually do apply to you.

TCPA (Telephone Consumer Protection Act) is U.S. federal law. It restricts autodialed or pre-recorded calls and texts to cell phones without prior express consent. The keyword there is autodialed — meaning your system is initiating contact with someone who didn't ask to be called. If a customer calls your store, picks up the phone, dials your number, and your AI agent answers, TCPA's most punishing provisions simply don't apply. That's an inbound call. The customer initiated it.

CASL (Canada's Anti-Spam Legislation) is often misread as a phone law. It's primarily an electronic messaging law — email, SMS, and certain software installations. CASL does not regulate live or AI-assisted voice calls the same way it regulates commercial electronic messages. Voice calls to consumers in Canada are governed instead by the CRTC's Unsolicited Telecommunications Rules and the National Do Not Call List (DNCL), neither of which apply to inbound calls your dealership receives.

So when a GM tells me they're worried that their AI phone agent is going to create a CASL liability, the honest answer is: not from inbound calls, no. The liability lives on the outbound side — specifically in follow-up texts or emails your CRM sends after that call.

What TCPA Actually Requires When an AI Answers an Inbound Dealership Call

Even on inbound calls, there are two things TCPA and related FCC guidance want you to think about.

First, if your AI agent uses a pre-recorded voice (not a live-sounding conversational AI, but a literal recording playing back scripted lines), some state-level laws and certain FCC interpretations require disclosure that the caller has reached an automated system. The practical fix is simple: your AI agent should identify itself as an AI at the start of the call or immediately upon request. Something like 'Hi, you've reached [Dealership], I'm an AI assistant — how can I help you today?' clears the disclosure bar in virtually every jurisdiction.

Second, if the call transitions into any kind of follow-up — your AI books a test drive and then your system auto-texts a confirmation — that text message is now subject to TCPA's express consent requirements if it's going to a cell phone. You need either express written consent collected at some prior point (a web form opt-in, for example) or the customer to have voluntarily provided their cell number in the context of an existing business relationship. Most CRM platforms prompt this; the gap is that dealerships don't always audit whether those consent records are actually being captured and stored.

The Three CASL Rules That Do Apply to Your Dealership's AI Workflow

For Canadian stores, here's where CASL genuinely touches your AI-assisted process. These are the places I've seen dealers get sloppy:

1. Post-call email follow-ups. If your AI books a test drive and your CRM automatically fires a confirmation email, that email is a commercial electronic message under CASL. You need either express or implied consent. Implied consent exists if the customer initiated contact — which they did, by calling you — and the email is directly related to that interaction. You're fine, but you need to make sure your unsubscribe mechanism works and is included in every email.

2. Subsequent marketing emails. The implied consent from an inbound call does not give you a blank cheque to market to that person forever. Under CASL, implied consent from a business inquiry lasts two years. If you're mailing that customer after two years without refreshed consent, you're offside.

3. SMS confirmations and follow-ups. Text messages are treated as commercial electronic messages under CASL. Same rules apply as email. If your AI-to-CRM workflow triggers a text, you need consent on record. If the customer texted your store first or provided their number explicitly for follow-up, you're likely covered under implied consent — but document it.

The through-line here is that the AI call itself is not the compliance problem. It's the automated follow-up chain that gets triggered after the call where most dealers have gaps.

How to Actually Audit Your Dealership's Compliance Before Turning on AI

Before you go live with any AI-assisted call handling, here's what I'd recommend walking through with your operations manager or outside counsel:

1. Map every automated touchpoint triggered by an inbound call. Write out what happens in your CRM after a call is logged — every email, every text, every task. Most dealers have never done this and are surprised by what fires automatically.

2. Confirm your consent capture is working and being stored. Your DMS or CRM should be logging when and how consent was obtained. If a regulator asks, 'this customer filled out a web form' is not enough — you need to show the form, the timestamp, the IP address if available, and the language of the consent.

3. Add AI disclosure language to your call greeting. One sentence. 'You've reached an AI assistant at [Dealership].' Done. This covers you under FCC guidance and any analogous provincial requirements.

4. Verify your unsubscribe mechanism is functional. Under CASL you have 10 business days to honor an unsubscribe request. Most CRMs handle this, but if you have custom workflows or third-party tools stitched together, test it manually.

5. Check your DNCL scrubbing for any outbound campaigns. If your BDC runs outbound call campaigns — conquest lists, service reminders to non-customers — you must be scrubbing against the National DNCL every 31 days in Canada, and the Federal DNC list in the U.S. AI doesn't change this requirement, but it does mean if you're using AI for outbound calling, the scrubbing obligation is still fully yours.

What an AI BDC Handles Versus What Your Store Still Owns

This is the part of the conversation I think is most important to have honestly, because I see vendors — including in our space — oversell what an AI system takes off your plate from a compliance standpoint.

An AI answering agent handles the voice interaction. It answers the call, qualifies the lead, books the appointment, and logs the outcome. What it does not do is own your compliance obligations. Those stay with the dealer.

What a well-built AI BDC should do is make compliance easier to maintain. According to Cox Automotive's 2024 Car Buyer Journey Study, 64% of car buyers say they'd buy from a dealership again if the experience was easier — and a big part of 'easier' from an operations standpoint is having clean, auditable records of every customer interaction. An AI system that logs every call, timestamps every booking, and passes structured data into your CRM gives you a better compliance paper trail than a BDC team writing notes into a shared spreadsheet.

At AutoVox, we built the inbound call handling layer specifically for dealerships. Every call is logged, transcribed, and passed to your CRM with a timestamp. That documentation is actually useful if you ever face a consumer complaint, because you have a complete record of what was said, when, and what action was taken. You can see the full breakdown of how our call handling integrates with your sales workflow at autovox.vernallc.com/stacks/sales.

What we don't do is manage your email consent database, scrub your outbound lists, or replace your legal counsel. We're the inbound call layer. You still own the downstream compliance on whatever your CRM does with the lead after we hand it off.

That's the honest version of the pitch: AI handles the call, documents everything cleanly, and gives your compliance posture better raw material to work with. But it doesn't replace the need for a compliant CRM workflow and a review of your follow-up sequences.

If you're a GM in Canada especially, the practical checklist is short: get your post-call email and SMS workflows audited against CASL's implied consent window, make sure your unsubscribe links work, add one line of AI disclosure to your call greeting, and document your consent capture. That's it. None of that is specific to AI — it's the same standard you're already supposed to be meeting for your BDC team.

The dealers I've talked to who are most nervous about AI and compliance are usually the ones who haven't done this audit for their existing BDC either. Turning on an AI agent is actually a good forcing function to finally map the whole workflow.

---

Don't take my word for it. Call our live AI agent right now at +1 (604) 229-7496 and try to buy a car from it.