ZANUS AI FOR AUTOMOTIVE — OVERVIEW
Sales calls answered every hour buyers shop. Test drives and service visits booked into real calendars. Window-sticker specs, TSBs and warranty policy books that answer back with sources cited. One AI system for the customer side and the store side — built for dealerships and dealer groups, and equally at home with OEMs, suppliers, captive finance arms and software-defined-vehicle teams.
Private tenant or your own server · unlimited users · GLBA-conscious handling

A real deployment view: customer records, scheduled AI works, the week’s appointments and follow-ups.
The AI answers your sales, service and parts lines 24/7 in your chosen voices — books the test drive, schedules the oil change, checks the part — and hands hot buyers to your people, by your rules.
Window-sticker specs, technical service bulletins, warranty policy books and F&I packets become a library that answers with the source cited — for the advisor, the tech and the F&I office alike.
Captive finance arms and F&I offices run on consumer credit data. Your tenant is isolated, permissions reach the field level — and the same OS runs air-gapped on hardware you own.
The buyer who calls at Saturday 6 PM and hears voicemail buys from the store that answered. The Zanus front office answers every ring — sales, service, parts, trade-in — books into your real calendars, and speaks up to 40 languages.


A Monday-morning warranty-claims review, executed by the AI on schedule, every determination cited to the warranty policy book — that is real scheduled work. TSBs, specs, F&I paperwork and DMS records become a system that answers back.
OEMs, suppliers and captive finance arms handling consumer credit files and pre-release vehicle programs run the identical OS on Zanus hardware inside their walls: air-gap capable, USB updates, unlimited users — the data physically incapable of leaving.

Yes: one tenant with workgroups per rooftop and department, or separate tenants on shared infrastructure. Sales, service, parts and F&I each see exactly what their role allows, enforced server-side.
No. It quotes from your real catalog and inventory at the prices you set, with payable links where you allow — and hands negotiation, appraisal and desking to your salespeople, by your routing rules.
The same platform: OEM and supplier teams use the document libraries, scheduled AI works and automations on engineering and program paperwork; captives apply the field-level permissions and audit trail to consumer finance files. Bring your use case to the demo.
ZANUS AI FOR AUTOMOTIVE — FRONT OFFICE
Every unanswered sales call is a buyer dialing the next dealership on the search results. The Zanus front office answers on your menu, in your voices — sales, service, parts, trade-in — books, confirms and follows up, 24/7, in up to 40 languages.
Private tenant or your own server · unlimited users · GLBA-conscious handling

Sales calls, service bookings, parts questions and follow-ups — one dashboard your GM can read.
A shopper calls at 9 PM about the SUV on your lot. The AI confirms it is in stock, answers the spec questions from the window sticker, and books a test drive for 10 AM — confirmed by text before the shopper hangs up.
Oil changes, brake jobs, diagnostics: the AI checks real service-calendar availability, books the appointment, and sends the reminder that actually gets the car in the bay.
“Do you have the cabin filter for a 2019 crossover?” “What is my sedan worth on trade?” Answered from your inventory data and your appraisal process — instantly, identically, every time.
A buyer calls about a listing; the AI confirms availability, answers trim and option questions, offers real open slots on the sales calendar, books the test drive and logs the whole conversation — while your salespeople stay with the customers on the floor.


Website chat that answers like your best product specialist, web forms for credit applications and service requests worked in minutes, and a transcript of every conversation — lead-to-appointment in minutes, not Monday-morning voicemail triage.
Yes. Your sales, service and parts lines stay; calls route to the AI first, staff first, or any mix per line and per hour — after-hours to the AI, weekday mornings to the BDC, however you run the store.
It quotes from the catalog and inventory data you approve, at your prices. Desking, incentives stacking and finance terms go to your people — the AI books the appointment where those conversations happen.
Inbound recall questions are answered from your approved recall information and booked straight into the service calendar. Outbound recall notices run through Owner Outreach → with approval rules.
ZANUS AI FOR AUTOMOTIVE — BACK OFFICE
Window-sticker specs, technical service bulletins, warranty policy books, F&I packets, DMS records: a dealership is a paperwork operation with cars attached. The Zanus back office turns that archive into a working AI staff — drafting, cross-referencing and answering with sources cited, under your managers’ sign-off.
Private tenant or your own server · unlimited users · GLBA-conscious handling

A real session: warranty claim documentation drafted, policy-book clauses cited, service manager decides.
Warranty-claim drafts, weekly TSB digests for the shop, aged-inventory reports — assigned to the AI like to a staffer, executed on schedule, fully auditable.
“Is this repair covered at 52,000 miles?” The warranty policy book answers in seconds with the clause cited — instead of the service manager digging through PDFs while the customer waits.
Every AI-drafted claim, letter and report lands in Output awaiting review. Nothing reaches a customer, an OEM portal or the DMS without your manager’s decision.
A technician hits an intermittent electrical fault on a 2021 model. Instead of twenty minutes in a portal, the question goes to the AI: the relevant TSB comes back in seconds, cited, with the affected VIN ranges and the repair procedure attached — flag hours saved on every job.


The documents that eat closing time: deal-jacket checklists verified, missing-signature lists drafted, warranty and we-owe follow-up letters written from the deal record. Drafted in minutes, in your templates, filed against the DMS record through connectors.
Your DMS stays the system of record; API connectors move data both ways under your field mapping, with a dry-run preview before anything writes. Bring your DMS to the demo and we map it.
No. It retrieves, drafts and organizes — the TSB, the spec, the claim documentation — with sources cited. The technician diagnoses; the service manager approves.
YOU MIGHT ALSO LIKE
Front Office AI picks up every call and chat — books, quotes, follows up, 24/7 in 40 languages. Watch it run a business like yours, live.
ZANUS AI FOR AUTOMOTIVE — SPECS & TSBS
Window-sticker specs, technical service bulletins, warranty policy books, service manuals, F&I forms, OEM program guides — loaded into curated libraries the AI reads from. Ask in plain language; get the answer with the source cited, at the permission level of whoever asks.
Private tenant or your own server · unlimited users · GLBA-conscious handling

Libraries: current policy books outrank superseded ones, this year’s program guide outranks last year’s — you set the order.
PDFs, scanned deal jackets, window-sticker images, OEM bulletins, media — the ingestion pipeline turns what lands in the store into queryable knowledge.
No source in your library, no claim: the AI cites the TSB, the policy-book clause, the program guide — or says it cannot answer. No improvised warranty promises.
The salesperson asks about towing capacity; the F&I manager asks about the deal file: each gets answers scoped to their role, enforced server-side.
“Which TSBs apply to this VIN range?” “What did the 2022 program guide pay on that model?” “What does our we-owe policy say?” The archive answers in seconds with the documents attached — instead of an advisor’s afternoon lost in portals and binders.

Only roles you authorize. Permissions reach the field level and the server redacts what a user cannot see — a salesperson never stumbles into a credit file.
Never. Your tenant is isolated; your policy books and deal files are yours alone — and the on-premises option keeps them physically inside your building.
ZANUS AI FOR AUTOMOTIVE — AI WORKFORCE
Assign work to the AI the way you assign it to staff: type, records, deadline, priority. Warranty-claim reviews, TSB digests for the shop, aged-inventory reports — executed on schedule, with citations, under review.
Private tenant or your own server · unlimited users · GLBA-conscious handling

Four steps: work type, records and libraries, tags, schedule — the AI takes it from there.
Warranty-claim draft, TSB digest, aged-inventory report, deal-jacket audit: work types molded to your dealership, with default libraries and examples per type.
The AI’s workload is managed like the team’s: one-click views show what is urgent, late, today and tomorrow — the claim deadline never slips silently.
Every work is a full session: reasoning streamed, sources cited, milestones tracked, linked to the customer record and the calendar.
Set “Weekly Warranty Claims Review” once: every Monday the AI checks the week’s claims against the policy book, flags the ones missing documentation, drafts the submissions, and files the packet for the service manager — before the first car rolls into the lane.

Yes — open any session, read the reasoning, redirect it, or stop it. The AI works like staff: visible, accountable, interruptible.
It does not get tired: the constraint is your review capacity, not the AI’s. Configurations size from a single rooftop to a multi-store group or an OEM program office.
ZANUS AI FOR AUTOMOTIVE — SERVICE SOPS
Multi-point inspection sheets, lift-safety rules, loaner-car procedures, delivery checklists, F&I compliance scripts — SOPs only work when people can find them, and the current version at that. In Zanus they are living documents: answerable in chat, attached to work, priority-ordered so the latest version always wins.
Private tenant or your own server · unlimited users · GLBA-conscious handling

SOP upkeep, scheduled like store work: quarterly reviews and expiration checks on the calendar.
Shop safety, road-test procedure, key control, deal-jacket checklist, delivery walk-around: one library, current versions on top, superseded drafts outranked.
“What is the loaner-car procedure for a warranty repair?” — answered in seconds with the document attached, at 7 AM write-up rush or Saturday close.
Work types carry their default SOPs: the AI drafting a delivery checklist reads from the delivery SOP — by construction.
Quarterly SOP reviews, expiration checks on dealer-plate and lift-inspection records, policy-update summaries for the Saturday sales meeting: assign them once as recurring AI work and the binder never goes stale again.

Upload the new version, set it on top: from that moment every answer and every AI work cites the new SOP. Old versions remain archived for audit.
ZANUS AI FOR AUTOMOTIVE — TEAM TRAINING
Service advisors, BDC agents and technicians turn over constantly in this business — the knowledge walking out the door does not have to. New hires learn your procedures from the AI, and every employee has an assistant that answers “how do we…?” instantly.
Private tenant or your own server · unlimited users · GLBA-conscious handling

Training lives inside the software: the AI walks each new hire through the store’s own procedures.
A new service advisor learns your write-up process, loaner policy, phone scripts and DMS workflow through guided training — productive in days, not a lost month of shadowing.
“How do I book a we-owe repair?” — asked to the assistant, answered from the SOP with the source attached, without pulling your best advisor off the lane.
Private chats work on any device with a login — the how-to knowledge follows the tech to the bay, the BDC agent to the desk, the salesperson to the lot.

The tenth “how do I write up a customer-pay diag?” gets the same patient, sourced answer as the first. Product knowledge stays current automatically, because the assistant reads from the same living libraries — new model year in, answers updated.
No — the assistant answers from the live libraries. Load the new spec sheets and SOPs once and every future answer updates with them.
ZANUS AI FOR AUTOMOTIVE — AUTOMATIONS
Describe the job in plain words — “when a recall VIN list arrives, match it to our owner records and draft the notification letters” — and it becomes connected blocks on a canvas, running on its own, with every run visible.
Private tenant or your own server · unlimited users · GLBA-conscious handling

A real flow: inbox trigger, record sources, AI compile, three outputs — drawn from a description.
A recall VIN list arrives → matched against your owner records, notification letters drafted per owner, service slots suggested — queued for approval, every step on the record.
A lease inside 120 days of maturity → the renewal outreach is drafted with the customer’s vehicle and history attached, and the salesperson gets the task — before the competitor’s mailer lands.
A backordered part checks in → the waiting customer is notified in their language and offered real service slots — the car returns, the bay fills, no sticky note involved.
Run states live on the flow: green success, red failure on the exact block. A recall notification that silently failed is a liability, not an inconvenience — here, nothing fails silently, and retry is one click.

Your rules: queue everything for human approval, or auto-send only the categories you designate as safe — recall notices, for instance, can require a manager’s sign-off every time.
ZANUS AI FOR AUTOMOTIVE — OWNER OUTREACH
Recall notices, service-due reminders, lease-end and equity offers, declined-service follow-ups, orphan-owner reactivation — drafted by the AI from your own records, in the owner’s language, queued for your approval. Factory-store marketing power, without exporting your list to anyone.
Private tenant or your own server · unlimited users · GLBA-conscious handling

Campaigns and sequences drafted from the records — recalls, service reminders, lease-end offers — awaiting approval.
Due-for-service, open-recall VINs, lease maturing, declined the brake job 6 months ago: audiences built from your own customer categories and dates — no third-party list broker.
Reminders and offers written the way owners actually read them — plain, direct, in the owner’s own language, with your store’s voice.
Opt-outs and contact preferences are enforced by the system, not by memory. Every send is on the record — which matters most on recall notices.
The audience, the content and the sending all live in the same system as the owner records — nothing leaves your tenant to reach a mailing platform. “Invite every owner with an open recall and no appointment” becomes a drafted, scheduled campaign in minutes.


Every outbound owner communication lands in the approval queue unless you designate the category as auto-send. On recalls especially, the store stays in control of every word — and can prove exactly what was sent, to whom, when.
Every send is on the searchable audit record: content, recipient, timestamp. When the question comes — from the OEM or anyone else — the answer is a search away.
Yes — a canceled slot can trigger the service-due list: the next matching owners are invited to the opening, in their language, by your rules.
ZANUS AI FOR AUTOMOTIVE — DMS & INTEGRATIONS
Your DMS — dealer management system — stays the system of record. Zanus becomes the system of work: API connectors sync customers, deals and documents both ways, inventory feeds keep the AI quoting from real stock, and AI-drafted documents flow back where they belong. No rip and replace.
Private tenant or your own server · unlimited users · GLBA-conscious handling

No rip and replace: the DMS, inventory feeds and calendars stay — the AI layer connects to all of them.
Customers, deals and service history mapped field by field, with a dry-run preview before anything writes — push, pull or two-way, your choice.
The AI quotes and answers from your live inventory feed, and the documents your OEM portals produce — bulletins, program guides, claim responses — route through the intake pipeline to the right library.
A full API for whatever else the store runs: appraisal tools, marketplaces, custom reports — data in, results out, under scoped keys.
The deal lives in the DMS, the vehicle in the inventory feed, the claim response in an OEM portal export — and the AI reads across all of it. “What is outstanding on this customer?” becomes one question with one grounded answer.


The warranty packet the AI drafted, the recall letter, the we-owe follow-up: finished documents return to the customer record in your DMS through the same connectors — reviewed and approved by your managers first.
Connectors are mapped per deployment — bring your DMS to the demo and we walk through the exact integration path for your store or group.
No. The connectors run inside your tenant — or inside your building on the on-premises option. Data moves directly between your systems.
ZANUS AI FOR AUTOMOTIVE — COMPLIANCE
A dealership holds credit applications, license scans from test drives, and a legal duty to prove recall notices went out. That calls for architecture, not promises: admin-created accounts, permissions to the field level, server-side redaction, a searchable audit trail — GLBA-conscious handling of consumer finance data, by construction.
Private tenant or your own server · unlimited users · GLBA-conscious handling

One record per user: role, tags, and granular permissions over every domain of the system.
The server redacts what a role cannot see — a salesperson checking a delivery slot sees the appointment, not the customer’s credit application in the same record.
Every recall notification — drafted, approved, sent — is on the searchable audit record with timestamps. When the OEM or a regulator asks, the answer takes minutes, not a file-cabinet week.
License scans and insurance details from test drives live under field-level permissions with retention you control — not in a photocopy tray behind the sales desk.
When the question comes — from a captive’s auditor, an OEM field rep or your own compliance counsel — the answer is a search away: access records, document trails, send histories, update logs, all in one place. And for captives and OEM programs that cannot let data leave the building, the identical OS runs air-gapped on hardware you own.

The architecture is built for GLBA-conscious handling: isolated tenants, field-level access, server-side redaction, full audit trail — and a fully on-premises option. Compliance specifics are reviewed with your counsel during onboarding.
In your isolated tenant — never training outside models — or fully on-premises on hardware you own, physically incapable of internet exposure.
ZANUS AI FOR AUTOMOTIVE — LIVE DEMO
Big vendors show dealership demos as videos behind a form. Ours is the product itself, configured for automotive: open the chat below-right and try it — book a test drive, ask a parts question, request a demo of the warranty workflow.
The conversation you have with us IS the demo

This screen is watching demos like yours happen: live conversations, outcomes, first response in seconds.
Ask the chat: “I want to test drive the hybrid this Saturday” — watch it qualify, offer slots and confirm like your BDC on its best day.
Ask: “how would you draft a warranty claim packet?” — it walks the workflow it would run in your tenant, grounded, cited, sign-off included.
The full demo loads an automotive tenant with sample records: TSB lookups, recall outreach, service booking — your store’s world, working.
Every link below is a full live-demo page for that specific business — its vocabulary, its calls, its booking rules.
Request the demo and the interactive automotive demo arrives in about two minutes — no sales call, no calendar dance. Watch it, interrupt it with questions, and book the human conversation when YOU are ready.

Yes — the same AI, configured with a sample automotive tenant. What you see is what your staff gets, with your inventory, policy books and owner records instead of the samples.
Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·