Skip to main content
GullySystem
Automotive

Lead Management for Car dealers

Give each enquiry an owner, status and next action.

CRM

Does this function belong in your operation?

Use when enquiries arrive through several channels or follow-ups are missed.

A prospective buyer makes contact.

A car enquiry needs the buyer’s requested specification and next decision, not only a telephone number. A family can compare variants, arrange a demonstration and discuss an exchange through different contacts. Keep those conversations related while preserving who requested each action. The consultant’s departure must not remove the dealership’s open follow-ups or the buyer’s stated preferences.

Bring the records the workflow depends on.

  • Buyer and related-contact references with communication permission
  • Requested model, variant, transmission and branch
  • Enquiry source and original external reference
  • Consultant, buying stage and next action

Outputs to check

  • Assigned car-enquiry register
  • Due demonstration, quote and exchange follow-ups
  • Recorded buying outcomes and transfer history

Follow the lead management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Capture the enquiry

    Record the prospect's requirement and source.

  2. 2. Check duplicates

    Review matching contacts while preserving distinct needs.

  3. 3. Assign ownership

    Set the responsible person and next action.

  4. 4. Qualify the requirement

    Record discussions and the reason to progress, pause or close.

  5. 5. Handover to sales

    Create the relevant opportunity or order reference without losing enquiry history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales consultant

Records the requirement and customer response, then identifies the next action and decision owner.

Sales manager

Reviews untouched enquiries and transfers open actions with their history when staff change.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Same family uses several contacts

Link related conversations after review; preserve separate buyers and vehicle requirements.

Manufacturer lead repeats a walk-in

Keep both source references and resolve ownership before merging records.

Consultant leaves with open discussions

Assign each action to a colleague and retain the accepted communication arrangements.

Can this work independently?

Lead tracking can start with manual records and checked imports. Appointments, quotes and orders retain the enquiry reference through later stages. Manufacturer-system or messaging connections need confirmed access and a supported method. A qualified enquiry does not allocate a car, approve finance or create revenue.

Systems and records it connects with

  • Test-drive appointments: requested vehicle and confirmed visit references.
  • Quotations and orders: accepted specifications and decision history.
  • Authorised source imports and messaging: original enquiry identifiers, permissions and delivery outcomes.

Configure, test and introduce the workflow.

  • Map the actual showroom and external enquiry sources and define the minimum specification fields.
  • Test a family enquiry, repeated manufacturer reference and consultant reassignment.
  • Compare a trial follow-up list with open showroom discussions and assign owners before regular use.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • A related contact does not overwrite the original buyer requirement.
  • A reassigned enquiry retains its previous conversations and next action.
  • A test-drive outcome remains distinct from a confirmed vehicle order.
Car dealers

How the business operates.

A car dealership moves a buyer from model enquiry and test drive to an accepted commercial proposal, vehicle allocation and physical handover. The buyer’s requested variant is a specification; the chassis or vehicle identification number identifies the car actually supplied. Keep enquiry, booking payment, confirmed order, allocated unit and delivered vehicle as separate records. This profile centres on new-car retail, including documented exchange and finance handoffs. Used-car acquisition, repair operations and corporate fleet tenders require their own scope.

Sales and demonstration

Capture model, variant, transmission and usage requirements, assign a consultant and retain the next action. Test drives need an available demo, responsible employee and key-custody record.

Commercial and external documentation

Maintain quotations and approved buyer decisions. Track actual lender and registration references, responses and payment evidence. An internal status change does not create external approval.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Buyer enquiry, source, preferred specification, consultant and permitted follow-up
  • Demo vehicle, appointment, check outcome, key release and return
  • Versioned price proposal, optional items, exchange assessment and accepted terms
  • Booking reference, confirmed order and allocated chassis or vehicle identification number

Operational bottlenecks to check

One household has several enquiries

Preserve each buyer and requirement while linking related contacts. A shared phone number alone is insufficient evidence that two requested vehicles are the same sale.

A quoted colour is not an allocated car

Keep model-level availability and a physical chassis allocation separate. Yard transfers or rejected inspection findings must update the allocation before another delivery discussion.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Qualify the enquiry

    Record the requirement and buying stage. Link duplicate contacts without collapsing separate vehicle requests. Decide whether the next action is a visit, test drive, quotation or permitted later follow-up.

  2. 2. Arrange the demonstration

    Reserve the requested demo model and responsible staff. Record the operator’s required checks before key release, then retain return condition and customer feedback. Demo completion does not create a sales commitment.

  3. 3. Agree the commercial proposal

    Show the variant, included and optional items, confirmed charges and assumptions. Keep exchange and finance references separate. Retain the accepted version and unresolved conditions.

  4. 4. Confirm and allocate

    Record the booking’s status under the applicable terms, verified payment and order approval. Allocate an identified unit only when available. A substitution needs a recorded decision and any required customer acceptance.

  5. 5. Review delivery readiness

    Track inspection, accessories, documents, external approvals and payment conditions independently. A requested collection day remains a request until the responsible coordinator confirms the required readiness decisions.

  6. 6. Invoice and hand over

    Reconcile billing and confirmed receipts. Match the physical car to its allocation and documents. Record keys, collection and unfinished obligations with their owners.

Industry reports to connect with

  • Enquiries and overdue actions by consultant, source and model
  • Demo requests, completed drives and unavailable vehicle conflicts
  • Confirmed orders awaiting a physical unit or readiness decision
  • Vehicle age in stock, yard location, allocations and inspection holds

Questions before implementation.

When should car dealers consider lead management?

Use when enquiries arrive through several channels or follow-ups are missed. A prospective buyer makes contact.

What should we bring to the requirements discussion?

Bring anonymised examples of Buyer and related-contact references with communication permission; Requested model, variant, transmission and branch; Enquiry source and original external reference; Consultant, buying stage and next action. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give each enquiry an owner, status and next action. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Lead tracking organises enquiries already received. Demand generation and the buyer’s sales decision remain separate activities.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A related contact does not overwrite the original buyer requirement. Use this check when reviewing the first working version.

Talk to us

Discuss lead management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements