Customer
Know who is asking.
Contact details, lead state, consent, recent topics, and bookings can inform the answer.
An automotive AI chatbot answers dealership questions with the customer and vehicle in view. When the conversation moves to another supported channel or to a person, the same history can move with it.
Last updated
The shopper asks while browsing. The dealership sees the same customer, car, and next step.

The chat stays on the dealer page and shows stock from connected inventory.

The conversation becomes a visible lead, booking, and summary for the dealership team.

An authorized operator sees the conversation and its booked test drive before taking over.
A useful answer needs the customer, vehicle, and recent conversation, not just the latest message.
Customer
Contact details, lead state, consent, recent topics, and bookings can inform the answer.
Vehicle
Vehicle interest, test-drive requests, and trade-in details stay with the customer.
The dealership decides what chat may complete and when a person should join.
Book or request
Book a test drive when the details and schedule are available. Otherwise, send the request to the team.
Handover
Keep the conversation, customer, and vehicle together when a team member takes over.
Simple questions may only need simple chat. Customer history, vehicle context, and approved actions need a deeper connection.
Use it for website answers and lead capture when the conversation can end there.
Cronus connects customer and vehicle details to approved actions, supported channels, and a clear team handover.
It is a dealership chat assistant built for vehicle, lead, booking, and service questions. It can use the customer and vehicle details available to it, then move the conversation to an approved next step.
Yes. It can gather contact details, vehicle interest, timing, trade-in information, and the customer's requested next step. The resulting lead and conversation remain visible to the team.
It can book or reschedule a test drive and submit a service appointment request when the required details, schedule access, and permissions are available. Otherwise it can hand the request to the team.
It is designed to work alongside them. The first rollout connects only the customer details and approved actions needed for the chosen journey, using the access those systems provide.
Basic chat may be enough for website questions or lead capture. More connected chat helps when the conversation must remember the customer and vehicle, continue on another supported channel, or complete an approved action.
We map the customer path, the AI role, and the team handover.