Industry

New AI-Call Disclosure Rules Are Landing In 2026. The Operators Panicking About Them Have The Problem Backwards.

2026 is the year AI-call disclosure stops being optional for dealerships. Most operators read the new rules as a tax to comply with quietly. That is backwards: early, plain disclosure is a trust and conversion lever, and the real buying question is who controls the disclosure.

S

ScaleVoice

July 30, 2026 · 6 min read

Direct answer

In 2026 several US regimes require dealerships to disclose when a caller is speaking with AI. Texas TRAIGA (HB 149) took effect January 1, Texas SB 140 requires AI disclosure within the first thirty seconds of a call, the FCC (which classified AI-generated voices as artificial under the TCPA in 2024) has proposed a disclosure at the start of every call, and California AB 489 adds its own duties, with penalties in the relevant regimes running $500 to $1,500 per call. Most operators read this as a compliance tax and try to hide the automation, which is backwards. The phone is a dealership's highest-converting channel: dealership data shows phone leads set appointments at roughly 74 percent versus about 40 percent for internet leads and close at around 2.3 times the rate (Foureyes, 2024 to 2025). Callers do not defect because a call is automated; they defect because it wastes their time or pretends to be something it is not and then fails. A confident early disclosure followed by an immediately useful agent outperforms a human-sounding bot the caller resents. Clean, early, logged disclosure is also a legal shield. The real question when buying voice AI is not whether a vendor discloses but who controls how: whether you can set the disclosure script per state and language, capture and prove consent, enforce calling-window rules automatically, and update the rule the day the law changes.

If your dealership makes or answers calls with an AI voice, 2026 is the year the disclosure question stops being optional. Texas's TRAIGA law took effect January 1, requiring covered organizations to disclose AI interactions without dark patterns. Texas SB 140 already requires AI voice to be disclosed inside the first thirty seconds of a call. The FCC, which in 2024 classified AI-generated voices as "artificial" under the TCPA, has proposed rules requiring an AI disclosure at the start of every call. California's AB 489 adds its own duties. Penalties for undisclosed AI calling in the relevant regimes run $500 to $1,500 per call, trebled for willful violations. More states are drafting.

I have watched a lot of operators read those headlines and reach for the wrong conclusion: that disclosure is a tax on AI calling, a line you are forced to read that will make customers hang up, and the goal is to comply with the least friction possible. That instinct is exactly backwards, and getting it backwards will cost more than any fine.

Start with what the phone is worth

In dealership data, phone leads set appointments at roughly 74 percent versus about 40 percent for internet leads, and close at around 2.3 times the rate (Foureyes, 2024 to 2025). The phone is not a cost center you are automating to save money. It is your single highest-converting channel. Anything that erodes trust on that channel is not a compliance problem, it is a revenue problem. Which means the disclosure line is not the threat. Sloppy, evasive, or hidden AI is the threat, because it corrodes exactly the trust that makes the phone convert.

Read the rule as a spec, not a tax

"You are speaking with an AI assistant for [dealership]" at the top of the call is not an apology. It sets an honest expectation, and honest expectations are why people stay on the line. Callers do not defect because a system is automated. They defect because it wastes their time, traps them in a menu, or pretends to be something it is not and then fails. A confident early disclosure followed by an agent that immediately does something useful, checks a real opening, answers the actual question, books the appointment, outperforms a human-sounding bot the customer slowly realizes is a machine and resents.

Disclosure done well is a trust signal, and trust is the whole conversion mechanism. The dealers who win the next two years will not be the ones who hid the AI best.

There is a hard-nosed version of this too. Disclosure that is clean, early, and logged is your legal shield. The dealer who can show that every AI call opened with the required statement, captured consent where it was needed, and respected time-of-day rules is the one who does not lie awake about per-call penalties. The operator hiding the automation is accumulating liability on every single call, at $500 to $1,500 a pop.

The real buying question is who controls the disclosure

If you are evaluating voice AI this year, the question is not "does this vendor disclose." Any serious vendor discloses. The real question is who controls how. That is where good products separate from demos, and it is worth grilling every vendor on it before you sign:

  • Can you set and edit the disclosure script per campaign, per state, and per language, or is it a fixed line buried in the vendor's stack?
  • Does the system capture and store consent, and can it prove disclosure happened on a specific call if a regulator or a customer asks?
  • Can it enforce time-of-day and calling-window rules automatically, and route by state, so a tightening rule in one jurisdiction does not put every call at risk?
  • When the law changes, and it is changing quarterly right now, do you wait for a vendor release or can you update the rule yourself the same day?
  • Does outbound stay inside business hours by policy, not just by capability?

A vendor who answers those crisply has built for the regulatory reality you actually operate in. A vendor who treats disclosure as a checkbox has handed you their liability along with their software.

Read the 2026 laws again, not as a threat, but as a spec for a better phone call. "This is an AI, and it is about to be genuinely useful to you" is not a disclaimer. It is the best first line a dealership phone call has had in years.

Next step

Turn this workflow into a scoped demo.

Bring the call source, booking rules, system destination, and exception path. ScaleVoice will map the first workflow that can produce a measurable booked outcome.

Book a demo

Related pages

FAQ

Questions buyers ask before scoping the workflow

What do the 2026 AI-call disclosure rules require?

Broadly, that you tell a caller when they are interacting with AI. Texas SB 140 requires disclosure within the first thirty seconds; Texas TRAIGA bars dark patterns around AI interaction; the FCC has proposed a disclosure at the start of every call; California AB 489 adds its own duties. Penalties in the relevant regimes run $500 to $1,500 per call. Confirm the exact obligations for your states with counsel, as rules are changing quickly.

Won't disclosing that it is AI make customers hang up?

The evidence points the other way. Customers defect from calls that waste their time or feel deceptive, not from calls that are honestly automated and immediately useful. A clear disclosure followed by a genuinely helpful agent tends to hold the line better than a human-sounding bot the caller resents once they realize.

What should I ask a voice vendor about disclosure?

Ask whether you can edit the disclosure script per state and language, whether the system captures and can prove consent, whether it enforces calling-window and time-of-day rules automatically, whether you can update rules the day the law changes, and whether outbound is constrained to business hours by policy.

Continue exploring

See where ScaleVoice fits your workflow

Review the solution, partner, proof, pricing, and demo pages that match the next step you are evaluating.

Solutions hub

Explore the calls and customer follow-ups ScaleVoice can handle across sales, service, recall, roadside, and EV.

View Solutions hub

Partner programs

See how DMS, marketplace, call platform, and telematics partners can add AI voice booking.

View Partner programs

DMS partner program

See how DMS and workshop software vendors can launch a white-label AI voice module.

View DMS partner program

Customer results

See published dealership results and examples of the outcomes ScaleVoice can help improve.

View Customer results

Integrations

See how ScaleVoice connects with DMS, scheduler, CRM, voice, telematics, webhooks, APIs, and lead files.

View Integrations

Resources

Find guides by dealership, marketplace, DMS, telematics, fleet, roadside, and EV workflow.

View Resources

AI service booking guide

Read the buyer guide for AI service appointment booking, missed-call recovery, scheduler updates, and performance measurement.

View AI service booking guide

AI for car dealerships guide

Use the broad dealership AI guide to learn how AI voice can support service, BDC, lead response, and customer follow-up.

View AI for car dealerships guide

ScaleVoice vs Numa

Compare ScaleVoice and Numa across dealership use cases, integrations, and customer outcomes.

View ScaleVoice vs Numa

Request a demo

Book a demo or send details so we can prepare the right call flow.

View Request a demo

Pricing

Review pricing options for booked appointments, partner programs, and platform resale.

View Pricing

Service bookings

Explore how ScaleVoice books service appointments and recovers missed after-hours demand.

View Service bookings

Missed-call AI

See how missed calls, overflow, voicemail, and after-hours demand turn into booked appointments.

View Missed-call AI

AI BDC

Review how ScaleVoice supports BDC teams with fast follow-up, qualification, booking, and handoff.

View AI BDC

AI for car dealerships

Use AI voice for dealership calls, leads, service booking, campaigns, and customer follow-up.

View AI for car dealerships

Test-drive booking

Learn how digital retail and marketplace leads convert into booked test drives.

View Test-drive booking

Continue reading

More insights from ScaleVoice

All posts