Car Dealership AI & Software Development
Voice agents that book service into Xtime, call back no-shows and unsold leads, and connect to your scheduler and CRM.
What slows you downCalls answered, service booked in Xtime.
For Automotive & Dealerships teams.
We build AI and software for dealer groups and for automotive software vendors that build on dealer platforms: voice agents that answer and place calls, and the integrations that let them read and write the dealership’s scheduler and CRM. Our shipped work here is Innovative AI’s voice agents.
AI receptionists that route service-booking and repair-status calls
On the Innovative AI build, the first voice a customer heard on the store’s line was a receptionist agent. It separated service bookings from questions about a car already in for work, sent anything else to the right place, and looked up and confirmed bookings customers had already made.
Service booking agents wired into Xtime
The booking agent asked for year, make, model and trim, loaded that vehicle’s service menu from Xtime, mapped the caller’s words to an op code and confirmed it, checked open slots and settled drop-off, pickup or mobile service before it booked. Name, vehicle and last service were saved against the phone number, so a returning caller wasn’t asked twice.
No-show and unsold-lead follow-up calls
When the CRM showed a customer had missed an appointment, the agent called the customer already knowing what was booked, and rescheduled or did what the customer asked. Leads who visited but didn’t buy got a message, then a call that learned why, captured their requirements and told them a supervisor would call back.
Integrations with dealer scheduling and CRM APIs
Xtime for service scheduling, VinSolutions for sales follow-up, and the dealership’s CRM for appointment status, all from Cox Automotive. Other dealerships run on other Cox Automotive systems, so we scope access to each system store by store.
In detailWhy service booking is harder than a calendar
On the Innovative AI build, each vehicle’s service menu in Xtime held 100–200 services, and every one carried its own op code. The caller never says an op code. They ask for an oil change, new tires or a look at a warning light, and the agent has to land on the right line of that menu, then read it back for confirmation before it asks for a date.
Op codes are how a dealership categorizes service work and its price. A single code can carry a description, labor hours, parts, fees and the model years it applies to, and one dealer software vendor notes that a dealership can hold thousands of them. Xtime lets each dealership build menus that reflect its own pricing and promotions, so the agent loads the menu for the vehicle on the call, never a generic list. Our guide to AI service scheduling for dealerships follows that call step by step.
Mapping was one source of misses. Of callers who went ahead with booking through the agent, 99% were booked, by our own count. For a service manager, the remaining calls came down to three things: a request no line on the menu fit, a customer’s pronunciation the agent misheard, and a call made from somewhere too loud to hear clearly.
What an Xtime or VinSolutions integration involves
Xtime and VinSolutions are both Cox Automotive products. Xtime is the service scheduler. VinSolutions is the dealership CRM, which its own site describes as “the AI-powered CRM with exclusive Cox Automotive shopper data and integrations with top industry providers”. On the Innovative AI build, service booking runs through the first and sales follow-up through the second. One vendor behind both doesn’t make them one integration: scheduling and CRM are separate products with separate data, so we scope each connection on its own.
Access is the slow part. As of October 2026, a third-party review of Xtime’s API reports that partner access runs through the Cox Automotive developer portal and takes an NDA, a partner agreement, fees, a business review and a certified demo. Each dealership then opts in with an invitation code. The scope covers capacity, available times and creating or canceling appointments by year, make and model or VIN. On the CRM side, VinSolutions’ integrations page points anyone who wants to become an integrated partner to Cox Automotive’s API storefront. Our Xtime API integration guide covers each step and what to build while you wait.
- Service schedulingXtime (Cox Automotive): service menus, open slots, booking and cancellation.
- Sales and CRM dataVinSolutions (Cox Automotive): the dealership CRM behind sales follow-up.
- AccessCox Automotive’s developer programs; for Xtime, an invitation code from every dealership.
The service numbers behind the business case
Service and parts brought in 13.3% of franchised dealers’ sales dollars in 2025, $164.6 billion in total, according to NADA Data 2025, the latest edition as of October 2026. The average dealership sold $9.7 million in service and parts and wrote 16,252 repair orders that year.
Dealers are losing part of that work to competitors. Cox Automotive’s Service Industry Study, published November 11, 2025 from a survey of 1,974 owners, found that dealerships handle 12% fewer service visits than they did in 2018. Only 54% of owners of cars two years old or newer went back to the dealership that sold them the car, down from 72% in 2023. Owners told Cox they want easy scheduling and flexible service options, and Cox recommends after-hours scheduling, pickup and delivery.
A booking agent covers the scheduling half of that list. The other half is the calls that go out: the customer who missed an appointment and the lead who left without buying. Our guide to no-show and unsold-lead follow-up covers those calls and the consent each one needs.
Selected workLive in Automotive & Dealerships.
Phone · Xtime · VinSolutionsInnovative AI: voice agents that book dealership service
Compliance & riskRules for calls, consent and customer data.
A dealership voice agent places regulated calls and handles customer records that can count as financial data. Below is our reading of the rules we design call flows and data handling around. It is not legal advice; your counsel confirms how each rule applies to your stores.
AI voices on outbound calls
The FCC confirmed in February 2024 that AI-generated voices are artificial voices under the TCPA. No-show and lead follow-up calls therefore need the customer’s prior express consent, and written consent when the call markets something, so every outbound number carries a record of where its consent came from.
Source: FCC 24-17: AI-generated voices under the TCPA (February 2024)Identification and calling hours
An artificial-voice call must name the business at the start and give a callback number during or after the message. Telephone solicitations to homes can’t go out before 8 a.m. or after 9 p.m. at the customer’s location, so outbound queues follow the customer’s time zone.
Source: 47 CFR 64.1200: telemarketing and artificial-voice callsCustomer financial data
Under the FTC Safeguards Rule, a dealership that leases cars for terms longer than 90 days is a financial institution for that leasing business. We treat call transcripts and CRM records as customer information either way: encrypted, behind role-based access and logged.
Source: 16 CFR 314.2: FTC Safeguards Rule definitionsAI disclosure for European dealers
From August 2, 2026, the EU AI Act requires telling people they are talking to an AI from the first interaction, unless it is obvious, and the European Commission reads that exception narrowly. A European build opens every call with the disclosure.
Source: European Commission: transparency obligations under Article 50 of the AI ActTypical timeline & budgetPublished prices. Fixed after discovery.
Automotive & Dealerships projects follow the same model as every Apptycoons engagement: a 2-week Discovery Sprint, then a 6–16 week fixed-price build, billed in milestones. A sensible first dealership release is one inbound service-booking flow at one rooftop on its existing scheduler, with every other call routed to staff; no-show and sales follow-up calls and more rooftops follow in later milestones.
Scope, architecture and a fixed quote for the build. The fee is credited to your build.
Your first release, delivered in demoed milestones, with 30 days of support after launch.
A dedicated squad for ongoing roadmap work once the first release is live.
What moves the price for Automotive & Dealerships projects
- Dealer systemsEach scheduler, CRM or DMS adds a connector, and partner access steps such as agreements, a certified demo and dealer opt-in can set the timeline more than the code does.
- Service menus and transportLong vehicle menus need more op-code matching tests, and each transport option (shuttle, loaner, pickup or mobile service) adds questions and rules to the call.
- Outbound callsNo-show and lead follow-up flows need consent records, calling-hour limits and a clean handoff to staff.
- RooftopsStores in one group can run different menus, hours and products, so each new rooftop adds configuration and testing.
When you don’t need a custom build
A single rooftop that needs after-hours answering and standard service booking should buy a product already wired into its scheduler; Xtime Schedule lists a Digital Voice Assistant add-on, powered by Brooke.ai, that answers questions and schedules appointments. Custom pays off for dealer groups and automotive software vendors that need their own call logic across several dealer systems, or want to own the call data and the agent.
FAQCommon questions.
How much does car dealership software development cost?
Builds are quoted at a fixed price within our $25k–$120k range after a $5,000 Discovery Sprint. For car dealership projects, the number of dealer systems the agent reads and writes, the outbound call flows and how many rooftops go live first decide where yours lands.
How long does a dealership voice agent take to launch?
Most projects start with a 2-week Discovery Sprint, then a 6–16 week build for the first release. Scheduler access runs alongside the build. As of October 2026, a third-party review of Xtime’s API reports that partners sign an agreement and pass a certified demo, and each dealership then opts in with an invitation code, so we start those steps during discovery.
Can you integrate with Xtime and VinSolutions?
Yes. For Innovative AI we built voice agents that book service through Xtime, Cox Automotive’s scheduling product, and run sales follow-up through VinSolutions, Cox Automotive’s dealership CRM. The agents are still live in production. Both products are Cox Automotive’s, and as of October 2026 VinSolutions sends would-be integration partners to Cox Automotive’s API storefront.
Does an AI voice agent replace the BDC?
No. It takes the routine calls off the BDC: answering service lines, booking appointments and the first follow-up to a no-show or an unsold lead. On the Innovative AI build, a sales follow-up ended with a handoff: the agent learned why the customer hadn’t bought, noted what they wanted and told them a supervisor would call back.
Should a single rooftop buy an off-the-shelf AI receptionist?
Often, yes. One store that needs after-hours answering and standard bookings is better served by a product already connected to its scheduler. As of October 2026, Xtime Schedule lists a Digital Voice Assistant add-on, powered by Brooke.ai, that answers questions and schedules appointments. Build custom when the call logic has to span several dealer systems or stores.
Which rules apply to outbound follow-up calls?
In our reading, not legal advice: the FCC ruled in February 2024 that AI-generated voices are artificial voices under the TCPA, so these calls need the customer’s prior express consent, and written consent if the call is telemarketing. FCC rules also require the call to name the business at the start and give a callback number, and telephone solicitations to homes can’t go out before 8 a.m. or after 9 p.m. local time.
Do you build for dealers outside the US?
Yes, but the integration we shipped is a US one. European dealers run other scheduling and dealer management systems, so connecting to them is a new integration we scope in discovery. From August 2, 2026, the EU AI Act also requires telling callers they are speaking with an AI from the first interaction, unless that is obvious.
