The Automotive AI Summit 2026 agenda is a one-day working sequence for dealer principals, GMs, fixed ops leaders, and automotive retail operators making decisions about technician productivity, AI ROI, security, customer experience, dealership data, and team adoption. The event runs September 24, 2026, at the MIT Museum in Cambridge, Massachusetts. Registration opens at 8:00 AM, the program begins at 9:00 AM, and the evening reception runs through 8:00 PM.
The useful way to read the agenda is not as a list of presentations. It is a decision path: where can AI create operating capacity, how should a dealership prove the economics, what could go wrong, what data makes the system useful, and what human leadership is required to make the change last?
| Essential detail | Automotive AI Summit 2026 |
|---|---|
| Date | Thursday, September 24, 2026 |
| Registration | 8:00–9:00 AM |
| Program | 9:00 AM–6:00 PM |
| Reception | 6:00–8:00 PM |
| Venue | MIT Museum — Gambrill Center, 314 Main Street, Cambridge, MA |
| Audience | Dealer principals, owners, GMs, fixed ops leaders, and automotive retail operators |
| Room | Capped at 300 operators |
The live 2026 agenda is the source of truth and may change as session details are finalized.
The first decision: where can AI create real dealership capacity?
The morning moves quickly from the opening keynote into technician productivity. That order matters. A dealer does not need another broad statement about AI capability; the operating question is whether a system can remove friction from skilled work without introducing new errors, rework, or customer confusion.
For fixed operations, productive capacity might mean fewer administrative steps for technicians, better appointment recovery, faster access to repair information, or cleaner handoffs between the service BDC, advisor, parts, and technician. The baseline should exist before the product demo. Useful measures include productive hours, cycle time, show rate, recovered repair orders, advisor time returned, and exception volume.
Our fixed ops AI deployment checklist explains how to map one workflow, its data sources, its human handoff, and its expansion or stop conditions before automation goes live.
The second decision: can the dealership prove AI ROI?
“Show Me the Money: A Dealer’s Guide to AI ROI” sits at the center of the day because every other AI conversation eventually reaches the same question: did the dealership create measurable value after counting the full cost?
The strongest ROI case connects one workflow to one primary economic outcome. It does not use message volume, summaries generated, or recommendations delivered as a substitute for value. It includes platform costs, implementation, integration, team time, data work, quality review, exception handling, compliance, and the cost of incorrect actions.
Dealers preparing for the session should bring a real candidate workflow and three numbers:
- the current baseline result;
- the full monthly cost of the proposed process;
- the outcome that would justify expansion after 90 days.
Use the interactive worksheet in our dealership AI ROI guide to pressure-test the assumptions before bringing them into the room.
The third decision: what security risks move with faster building?
The agenda’s security session focuses on vibe coding—the use of natural-language AI tools to generate software, automations, or integrations—and the risks to watch. The concern is not that dealership teams should stop experimenting. It is that generated code can move from idea to a system connection faster than traditional review, access, logging, and change-control processes.
That matters in an environment where customer records, finance and lease information, CRM activity, DMS data, call recordings, employee access, and third-party systems can intersect. The FTC’s automobile dealer Safeguards Rule guidance describes requirements around written risk assessment, access controls, encryption, multifactor authentication, monitoring, personnel training, service-provider oversight, incident response, and breach notification for covered customer information.
The practical agenda question is simple: can the dealership explain what data the AI can access, what it can change, who approves the change, where activity is logged, and how quickly the workflow can be stopped?
Our AI security guide for car dealerships turns that question into a pre-launch control checklist.
The fourth decision: who owns the customer layer?
The afternoon panel on the customer layer expands the conversation beyond a single chatbot, scheduler, or CRM feature. A customer can move through search, a website, chat, text, phone, sales, finance, service, and follow-up. AI may touch several of those moments, but the customer experiences one dealership.
Operators should listen for answers to four questions:
- Which system is the source of truth at each moment?
- When two systems disagree, which one wins?
- When does a human receive the conversation, and what context follows?
- Can the dealership see the complete action history after a complaint or mistake?
Customer experience deteriorates when automation improves one channel while breaking the handoff to another. The system should be evaluated on resolution, accuracy, escalation, opt-outs, repeat contacts, and recovery—not only response speed.
The fifth decision: what human skills make AI adoption work?
“Hardcore Soft Skills for Teams in the Age of AI” is not separate from implementation. It is implementation.
AI changes who makes a decision, who reviews an exception, how managers coach, and how employees understand the purpose of the workflow. A technically sound tool can still fail when the team sees it as surveillance, receives no explanation of the new handoff, or is measured on an outcome it cannot control.
Before the event, identify the operating owner, technical owner, and executive sponsor for the workflow you are considering. During the session, listen for practical ways to build judgment, feedback, accountability, and psychological safety into the rollout. A team should be able to flag a bad AI action without being treated as the reason automation “failed.”
The sixth decision: is dealership data ready to carry the decision?
The data panel and featured sessions bring the day toward the underlying dependency: AI output can only be as operationally useful as the data, permissions, definitions, and system connections supporting it.
Dealers do not need perfect data before beginning. They do need to know:
- which system owns customer, vehicle, appointment, pricing, inventory, and service-history facts;
- whether the AI reads live, synchronized, or exported data;
- how quickly corrections reach the workflow;
- which fields are incomplete or inconsistently defined across stores;
- whether the system writes back, and who can reverse an action;
- how access is removed when an employee or provider relationship changes.
This is the difference between an impressive answer and a dependable operating workflow.
How each dealership role should use the agenda
Dealer principal or owner
Focus on capital allocation, risk ownership, operating accountability, and the conditions required to scale across stores. Bring one AI investment that is under consideration and define what evidence would cause you to approve, revise, or stop it.
General manager
Track cross-department handoffs. An AI workflow rarely stays inside one org chart box. Ask which manager owns the exceptions, how the scorecard will be reviewed, and what behavior must change after launch.
Fixed ops director
Bring one constrained service workflow, its current baseline, and examples of the failure paths. Use the technician productivity, ROI, customer, and data sessions together rather than treating them as separate topics.
Technology, marketing, or data leader
Map systems, permissions, freshness, vendor dependencies, change control, and logging. Ask speakers and partners to demonstrate a failure and recovery path—not only the clean demo.
A 30-minute preparation plan before the Summit
The value of the agenda increases when the attendee arrives with a live operating question.
- Choose one constraint. Write the dealership problem in one sentence.
- Capture the baseline. Record the current outcome, volume, labor input, and error or escalation rate.
- Map the systems. List what the workflow reads, writes, and hands to a person.
- Name the risk. Identify the action or data exposure the dealership cannot accept.
- Set the decision. Define what you need to learn in the room to expand, revise, or reject the approach.
That preparation turns a conference conversation into an operating decision.
What happens after the final session?
The formal program concludes at 6:00 PM, followed by a reception at the MIT Museum through 8:00 PM. Use that time to compare implementation details with other operators: what the workflow looked like before the tool, what broke during rollout, which metric actually moved, and who owns the exceptions now.
The Automotive AI Summit is designed around one standard: the conversation should change what a dealership can do on Monday morning.
Plan your day: Review the current agenda, take the Dealership AI Operational Depth self-assessment, or get your ticket.