Lead management for a car dealership
The lead arrived from a portal and from the site, the test drive was set by phone, and the car was already sold when another salesperson booked it. After the drive there is no record of what the customer rejected.
Who it is for
For a dealership with several salespeople on the same stock. A poor fit for a one-person lot with no test drives and no leads from several sources.
Problems this page addresses
Two leads on the same car
Interest is logged on the customer’s name without a link to the car. Two salespeople promise the same vehicle.
A test drive with no summary
The customer drove and left. Nobody wrote whether the issue was price, color, or a trade-in, so the next call starts from zero.
Stock that does not know about an open deal
The car is marked available because the contract is unsigned, but an offer is waiting on financing.
What you get
A lead tied to a car
Each inquiry points at a car in stock, or at a type if there is no unit yet. A drive cannot be booked on a car that is already held.
A test-drive summary
After the drive you log what fit, what was rejected, and the next step: an offer, a trade-in, or releasing the car.
A stock state
Available, held for an offer, out on a drive, sold. A salesperson sees the state before calling the next customer.
Common questions
How do you choose between this and the lot’s current system?
If the current system already ties a lead to a car and a test drive, and the team works in it, there is nothing to build. Build when stock is in one system and leads are in WhatsApp, and the two never meet.
Can a reminder go out after a test drive on its own?
Yes, once there is a summary. A reminder without the summary only annoys the customer. It names the car and what stayed open, not a generic message.
What about a car coming in as a trade-in?
It becomes a stock item only after the deal is approved. Until then it is a note on the lead, not a car you can promise to someone else.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
Automations and AI agents that do not send on their own
A repeated request should not be written from scratch, and it should not go out before a person has read it. We attach classification and a draft to the system that already holds the case, with a clear rule for what stops for approval.
Client management for a brokerage
The listing lives on a portal, the buyer lives in WhatsApp, and the exclusive lives in the head of the agent who met the seller. After the viewing there is no single record of who came, what was rejected, and who should call back.