An AI Assistant That Covers the Whole DMS, Not Just Search
Most AI features in dealer software answer questions. They find a car, summarise a report, write a description. They do not run the business. The gap between those two things is coverage: how many parts of the system the assistant can actually operate.
Dilizy's assistant now has its own tools for 26 additional sections of the platform. Before this release it reached 7 sections out of 34. It now reaches 33: inventory and deals, customers and companies, leads and tasks, supply and documents, marketplace publishing, reports, reference data, access rights and settings.
Why coverage is the number that matters
A read-only assistant saves a few seconds of navigation. A write-capable assistant that covers one third of the system saves nothing, because the dealer still has to know which third. The moment a request falls outside the covered area, the person is back in the menus and the habit breaks.
Coverage is what turns a chat box into a way of working. It is also the honest way to compare AI claims across dealer software, because "AI-powered" says nothing about what the AI is allowed to touch.
| Generation | What the AI does | What the dealer still does |
|---|---|---|
| AI as a text tool | Writes descriptions and social posts | Everything else, by hand |
| AI as a search layer | Finds records, answers questions | Every create, edit and publish |
| AI as an operator | Creates, edits, publishes, reports | Approves, decides, handles exceptions |
Dilizy is in the third row for 33 of 34 sections. The background on how chat and external model access work is in AI DMS with chat and MCP and MCP for car dealers.
What the assistant can now operate
Inventory and sales. Vehicle cards, deals, supply, prices, statuses.
Customer side. Customers, companies, leads, tasks, notes, contact channels taken from company settings.
Documents. Generated and attached to a lead or a deal from the dialogue.
Marketplace publishing. Listings for OLX, AutoRia and Otomoto prepared in chat. The assistant offers to fill the data in the conversation or to hand over to the standard form, and the dealer picks. A complex trim is faster in the form. A typical car is faster in chat.
Reports and reference data. Selections, exports, custom fields, sources, task settings.
Administration. Roles, users, permissions and notifications, on read for now.
The limits are the feature
An assistant that can change data needs boundaries that a dealer can state in one sentence. These are ours.
Permissions are inherited, not granted. The assistant cannot do more than the person talking to it. A manager without access to purchase prices does not get them through chat. This is enforced at the tool level, not by asking the model to behave.
Plan limits apply identically. Publishing quotas, VIN lookups and user counts are counted the same way regardless of whether the action came from the interface or the dialogue.
Irreversible actions are confirmed first. Status changes, publishing and deletions are not executed silently. When the data does not add up, the assistant asks instead of guessing.
Sensitive sections are read-only. Billing, roles and access rights are visible to the assistant and editable only by a human. We will open them after watching how real conversations go, not before.
A missing record is never substituted. Previously, a request naming a record that did not exist could resolve to a similar one. That behaviour is gone. The assistant stops and clarifies.
Tool traffic stays hidden. The dealer sees the result, not the internal calls that produced it.
What else shipped
The second half of the sprint was acceptance and cleanup. 66 defects were closed: 40 found while testing the assistant itself, 26 across the platform, marketplaces and the mobile app.
The changes a dealer notices daily:
- The vehicle card used to take more than 12 seconds to load. It now opens immediately.
- Report export no longer breaks on a task with no currency set.
- Disabling an integration now actually disables it, including in the messaging service, where the connection used to keep accepting conversations.
- Instagram leads reach the right instance.
- The activity log holds business events only, and no longer grows without limit.
- Search handles VIN, names in Latin transliteration, and currency in price filters. Cars priced in dollars stopped disappearing from results, and euro and dollar amounts are no longer added into a single inventory value.
On the marketplace side, Otomoto model dictionaries are now requested from the platform at publish time instead of a stored snapshot, so new trims and engine power values are available immediately. After publishing, what was sent is compared against what was accepted: if the platform rejected photos or parameters, the dealer gets a warning rather than a silent loss. The "Published" status is set only once the listing is live and images are uploaded. OLX gained a category for heavy equipment, agricultural machinery and trailers.
What it does not do yet
- No changes to billing, roles or access rights. Read only.
- Storefront catalogue search is still in progress. It should show only makes that are actually in stock.
- Send-versus-accepted verification currently covers Otomoto. Other platforms follow.
- No usage statistics per scenario yet. We do not know which commands dealers reach for most, and we would rather measure than assume before reinforcing them.
Frequently asked questions
Can the assistant do something without the dealer knowing? No. Irreversible actions require confirmation, and the assistant's permissions equal the user's. A section you cannot open is a section it cannot touch.
What happens if it misreads a request? It asks a clarifying question. Where several records share a name, it asks which one before attaching a task or a document.
Does the team need to learn commands? No. The assistant works with names rather than internal record numbers, so a customer or a car is found the way a person would refer to it.
Which language does it reply in? The language of the interface. Confirmation buttons, execution statuses and document type names are localised.
Is it included in every plan? Access depends on the AI token allowance in your plan. Current terms are on the pricing page.
How is this different from connecting ChatGPT to a dealer database? An external model connected over MCP acts through the same tools and the same permission checks. The coverage described here is what those tools expose. Without them, an external assistant can read but not run the dealership.
What comes next
Watch real conversations, then open changes in billing, roles and access step by step. Finish storefront catalogue search. Collect scenario statistics and strengthen the most used paths. Extend send-versus-accepted verification to the remaining marketplaces.
Try it. The assistant lives inside the platform, with nothing to connect separately. A new dealer can run a full cycle during the 30-day trial: add a vehicle, connect marketplaces, take one listing from card to published, and see how much of it closes in a dialogue. A card is added at signup, and cancelling ends access immediately with no charge.
Start your trial → https://dilizy.ai