Lead Management for Electric car dealerships
Keep EV purchase questions, demonstration outcomes and the next responsible decision together.
Does this function belong in your operation?
For new battery-electric car enquiries, including company buyers with separate procurement and driver contacts.
A prospective buyer asks about a new electric car or an existing brand enquiry reaches the dealership.
An EV enquiry can stall on a charging question rather than on the vehicle itself. Record the intended driver, buyer and the source of the enquiry, then assign the unresolved issue to the adviser or relevant external specialist. Keep demonstration feedback alongside the actual model discussed. A manufacturer booking reference is useful context, but it does not prove a local allocation, a signed battery agreement or a confirmed charger installation.
Bring the records the workflow depends on.
- Original enquiry source, contact permission and prior brand reference
- Buyer, intended driver, payer and model under discussion
- Charging-access question, demonstration request and assigned next action
Outputs to check
- Assigned enquiries with buyer and driver roles
- Demonstration feedback and unanswered technical questions
- Proposal handoff with original source and outstanding dependencies
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.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
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.
Can this work independently?
Enquiries can be entered directly or imported with permission. Manufacturer portals and communications require supported access. Product and charging explanations need their actual qualified sources; the lead record does not supply technical advice or create confirmed stock.
Systems and records it connects with
- Manufacturer enquiry reference and authorised correspondence.
- Demonstration record and accepted proposal version.
- External charging question with buyer-approved sharing.
Configure, test and introduce the workflow.
- Trace a walk-in enquiry and a brand-origin enquiry about the same purchase.
- Test a company driver request and a pending apartment-charging decision.
- Check that proposal handoff preserves open questions and contact restrictions.
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.
- The intended driver and buying authority remain distinguishable.
- Demonstration feedback names the model actually used.
- A charging referral remains open until its actual response is recorded.
How the business operates.
An electric-car buyer agrees on a vehicle but still needs a decision about apartment charging and a clear explanation of the battery agreement. The showroom must keep these questions open even after a booking payment arrives. This requirements model covers new battery-electric cars sold through a dealership's actual retail arrangements. It connects buyer discussions, the accepted vehicle and battery terms, identified stock, external charging referrals and the physical handover. A battery supplied with the car, separately financed or provided under another documented arrangement needs the corresponding contract references; the programme name alone does not establish ownership. These are proposed business records, not verified GullySystem features.
The records that hold the operation together.
- Buyer, intended driver, payer and consented contact details
- Selected vehicle variant and source product-information revision
- Demonstration vehicle identity and recorded outcome
- Battery supply, finance or usage agreement with provider and accepted version
Operational bottlenecks to check
A battery programme is described as a simple discount
The buyer accepts a headline vehicle amount without the separate obligation. Preserve the actual programme document, provider and buyer decision so later staff can explain what was agreed.
Charging referral is mistaken for installation
The buyer expects a working home charger because the showroom sent a request. Track referral, survey response and provider completion evidence separately, without letting the dealer record certify electrical work.
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. Understand the purchase
Record who will buy and drive the car, the intended use and unresolved charging questions. Keep an information enquiry separate from a requested demonstration or an accepted sale.
2. Retain the demonstration outcome
Identify the car used and the buyer feedback. Route unanswered technical questions to the proper owner; a drive does not prove the buyer will achieve a particular range.
3. Agree the commercial package
Version the vehicle configuration and battery terms alongside equipment and accessories. Identify which obligations belong to the dealer and which require another provider agreement.
4. Allocate the actual unit
Link an available vehicle only after the allocation decision. Check a changed unit against the accepted specification and preserve any buyer-approved amendment.
5. Resolve handover dependencies
Review preparation evidence, buyer details and external responses under the actual sale terms. Keep an open charging-site referral visible even if another part of the order is ready.
6. Deliver and reconcile
Record the vehicle, supplied items and recipient at handover. Retain any agreed outstanding item and its owner; reconcile the dealer bill independently of battery-provider or installer accounts.
Industry reports to connect with
- Buyer questions awaiting manufacturer or charging-provider response
- Accepted packages awaiting battery-agreement confirmation
- Vehicles allocated, held for preparation or used as demonstrators
- Orders with unresolved external dependencies by responsible party
Questions before implementation.
When should electric car dealerships consider lead management?
For new battery-electric car enquiries, including company buyers with separate procurement and driver contacts. A prospective buyer asks about a new electric car or an existing brand enquiry reaches the dealership.
What should we bring to the requirements discussion?
Bring anonymised examples of Original enquiry source, contact permission and prior brand reference; Buyer, intended driver, payer and model under discussion; Charging-access question, demonstration request and assigned 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. Keep EV purchase questions, demonstration outcomes and the next responsible decision together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
No demand-generation result, range forecast, finance eligibility or charging suitability is established by lead status.
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. The intended driver and buying authority remain distinguishable. Use this check when reviewing the first working version.
Related functions for electric car dealerships.
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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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