01
Every Reply Was Typed by Hand
Slow work, and it tied up a salesperson on one buyer at a time.
Case Study · Automotive and Fleet
A buyer asks about one used car on mobile.de. Kodexo Labs built the system that turns that message into a private page for that exact car, with an assistant that answers questions about it instantly and hands the conversation to a salesperson when it matters.
Of inquiries answered without a salesperson
Saved on lookups before every reply
More inquiries per support person


01 · Overview
A buyer sends a message about a listing on mobile.de. Seconds later they get a link that belongs to them. It opens a page for that single vehicle: the real photos, the specification tables, the equipment lists, the service record, the delivery options, and the condition report with the dealer's pricing notes taken out.
On the same page sits an assistant that has read everything about that car and nothing about any other. It answers the moment the buyer asks, keeps to CarGentur's own wording on price and damage, and hands the buyer to a real salesperson the moment the question needs one. Nobody at the dealership touches a step in between.


02 · The Problem
A used car sells to whoever answers first. At CarGentur, answering meant opening the file server, finding the right photos, reading a condition report, and typing a reply by hand. The specification named six things that had to change.
01
Slow work, and it tied up a salesperson on one buyer at a time.
02
A buyer who waits for an answer has usually moved on by the time it arrives.
03
Everything sat on the dealer's own file server, connected to nothing a buyer could open.
04
The only record was a scanned report nobody could search.
05
Price and damage were answered from memory, so the wording changed with whoever replied.
06
A serious buyer had no direct way to get from a question to a salesperson.
03 · The Solution
Each part maps to a requirement in the specification. Click through to see the screen it produced.
Page Generation
The mobile.de submission triggers the build. The car is found by its own magicID, its images and description are pulled from CarGentur's file server, and a page for that one vehicle is published on cargentur.de.
Specification 4.1 · Page generation

Reading the Paperwork
When the file server has no description, the condition report is read instead, the details are extracted, and the result is stored in a knowledge base so the same work is never done twice.
Specification 4.2 · File server and OCR

Condition Report
The inspection PDF is cleaned of pricing information before it reaches the page, so buyers get the appraiser's full findings and nothing on the dealer's margin.
Specification 4.4 · Condition report cleanup

The Assistant
Every question is sorted before it is answered: company questions get standard wording, car questions are answered from that vehicle's record alone, price and damage follow CarGentur's approved lines, and off-topic questions get a polite redirect.
Specification 4.3 · AI chatbot routing

Handover
Buyers can end the chat or ask for a person at any point, and the assistant offers the handover itself whenever it is unsure. The escalation notifies CarGentur directly.
Specification 4.6 · End chat and handover

Handoff Email
When a session closes, the team receives the full conversation, a short summary, and the buyer's details, formatted to match the email structure CarGentur already uses.
Specification 4.5 · Automated handoff email

04 · How It Works
Nobody at CarGentur touches any of the steps in the middle. Each step carries the specification section it comes from.
Step 1 · Inquiry · 4.1
A buyer messages about one listing on mobile.de
Step 2 · Find the Car · 4.1
The vehicle's own ID pulls its photos and description from the file server
Step 3 · Fill the Gaps · 4.2
Missing details are read out of the condition report and saved for next time
Step 4 · Publish · 4.1
A page for that car goes live on cargentur.de and the link is sent to the buyer
Step 5 · The Conversation · 4.3
The buyer asks. The assistant sorts the question into one of four kinds before it answers.
Step 6a · Handover · 4.6
Unsure, or asked for a person? The buyer is offered a real agent and sales is notified.
Step 6b · End Chat · 4.6
The session closes with a summary of what was discussed.
Step 7 · Handoff · 4.5
Sales receives the full chat, the summary, and the buyer's details, in the format the team already uses.
A Supervisor Owns the Wording
Approved answers live in a library a supervisor can edit, preview in a sandbox, and publish now or overnight. Every change is logged with who made it and when.
Buyer Data Stays Protected
Traffic between buyers, the pages, and CarGentur's file server is encrypted. Chat records follow GDPR rules for consent, access, and deletion.
Nothing Fails Quietly
A file that will not open, a report that will not read, or an assistant that is down each raise a logged incident, and the buyer is offered a real agent straight away.
Under the Hood
No replacement of the dealer's file server, and no change to how listings reach mobile.de. Six components, each doing one job.
Backend
Receives the inquiry and builds the page for that one vehicle.
Assistant
Answers the buyer, routed by question type.
Knowledge Base
Holds the extracted vehicle text so answers stay on that car.
Document Reading
Reads the scanned PDF when the file server has no description.
Vehicle Media
Stays the source of images and descriptions. Untouched.
In Transit
Every exchange between buyer, page, and file server.
05 · Outcomes
Each figure below traces to a specific part of the build: instant page generation, the four-way answer routing, or the automatic handoff email.
Lookup Time
Saved per inquiry, now that nobody hunts through the file server before replying
First Reply
Of inquiries resolved on the page itself, with no agent involved
Agent Hours
Less time on routine follow-ups and chat write-ups
Capacity
More simultaneous buyer inquiries per support person
Drop-Off
Fewer buyers walking away while they wait to hear back
Conversion
Lift in inquiries that turn into a booked appointment or test drive
FAQ
The questions that come up in almost every first call about automating buyer inquiries.
No. Each page is tied to a single vehicle, and the assistant answers only from that vehicle's record. Questions about other stock get a redirect, not a guess.
Those two topics have approved answers written by CarGentur, and the assistant uses them word for word. A supervisor can rewrite them at any time without a developer.
No. Pricing information is removed from the condition report before the PDF is published on the page, so the buyer gets the inspection detail without the internal figures.
The system reads the vehicle’s condition report and pulls the details out of it. If the read fails twice, the record is flagged for a person to check rather than published half-empty.
Every chat that ends or gets escalated sends the team an email with the full conversation, a summary, and the buyer's details, formatted the way CarGentur's inbox already expects.
Each inquiry runs as its own page and its own session, and the setup spreads load across servers during peak periods. Uptime, response times, and error rates are monitored.
Twenty minutes with the team that built this. Bring the way inquiries reach you today, and leave with a straight answer on what it would take.
Products Shipped
Across 25+ industries
Client Retention
Across every engagement
Rated on Clutch
Elite AI Firm designation
Related work