Skip to main content
GullySystem
Automotive

Lead Management for Electric scooter dealers

Connect the scooter rider’s questions with the purchaser, original booking and responsible counter adviser.

CRM

Does this function belong in your operation?

For new scooter retail enquiries where the rider, payer and online booker can be different people.

A walk-in, brand referral or returning contact asks about buying an electric scooter.

The person at the counter may be the rider, a relative paying for the scooter or someone following up a brand booking. Keep those roles distinct and preserve the original enquiry reference. Record the model actually tried and the remaining question about the supplied pack, charger or service contact. A repeated phone number does not prove a duplicate purchase. Qualification records the next decision; it does not establish registration eligibility or a promised range.

Bring the records the workflow depends on.

  • Original contact or brand booking reference and communication permission
  • Intended rider, purchaser, payer and requested model
  • Test-ride outcome, pack or charger question and next responsible action

Outputs to check

  • Enquiry register with rider and purchaser roles
  • Actual test-ride feedback and open product questions
  • Proposal handoff retaining the brand booking reference

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. Find the original enquiry

    Review the brand reference and earlier counter contacts. A shared family phone can represent different riders or purchases; check before merging.

  2. 2. Clarify who is asking

    Identify the intended rider and actual purchaser. A relative collecting information or paying a token does not automatically have authority to change ownership details.

  3. 3. Capture the product question

    Retain the actual variant tried and the unresolved pack, charger or after-sales question. Refer technical answers to approved product information or the relevant specialist.

  4. 4. Record the next decision

    Give the adviser or provider a specific follow-up with permitted contact. Preserve a request to pause contact rather than continuing from another channel.

  5. 5. Hand over the chosen package

    Link the confirmed requirement to the proposal or original booking. Keep questions about purchaser identity or supplied equipment open until their responsible owner responds.

Who uses the module, and who approves?

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

Counter adviser

Maintains rider and purchaser context without merging distinct requests.

Test-ride coordinator

Records the actual model and visit outcome under the dealer’s approved process.

Showroom manager

Resolves brand-versus-counter ownership and unanswered product questions.

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.

Relative booked on behalf of the rider

Retain both roles and follow the actual seller’s purchaser-confirmation process.

Buyer compares fixed and removable batteries

Record the exact models and approved product sources; do not transfer one model’s capability to another.

Same phone appears on separate bookings

Preserve each requested purchase until the responsible adviser confirms the relationship.

Customer asks about road-use exemption

Refer the exact model and question to the competent authority or authorised process; do not mark eligibility from a marketing label.

Can this work independently?

Leads can be entered at the counter or imported with permission. Brand booking and messaging connections require supported access. The adviser needs approved product references; enquiry status does not approve registration, finance or the final supply package.

Systems and records it connects with

  • Original manufacturer booking and authorised correspondence.
  • Test-ride record and selected variant reference.
  • Accepted proposal and unresolved provider question.

Configure, test and introduce the workflow.

  • Trace a walk-in enquiry and a family member following up an online booking.
  • Test repeated phone numbers and a fixed-versus-removable battery comparison.
  • Check that proposal handoff preserves the purchaser question 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.

  • Contact, purchaser and intended rider remain distinguishable.
  • A test-ride outcome identifies the actual model.
  • An unresolved eligibility question cannot become a confirmed product promise.
Electric scooter dealers

How the business operates.

A scooter buyer books through a brand website, a family member pays the token, and the local counter is asked to deliver a different colour with another battery option. The dealer needs the original reference and the accepted revision before treating those requests as one settled sale. This scope covers new electric-scooter retail through the business's actual manufacturer or retail-partner arrangements. It follows rider questions, variant and pack choices, physical scooter and accessory custody, the correct selling entity and handover. Removable packs or a separate battery plan are recorded only for models actually supplied that way. The proposed workflow does not run a battery-swapping network or claim installed GullySystem capability.

Counter enquiries and test rides

Keep the intended rider, purchaser and person making contact distinct. Record which model the rider tried and questions needing a product specialist. A family enquiry or online token does not settle the owner details, permitted road use or final package.

Variant and package confirmation

Identify the scooter variant, colour, supplied pack configuration and charger. Retain accessory and optional service-plan choices separately. When a model offers a battery usage arrangement, record the actual provider terms rather than presenting it as an ordinary included battery.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Brand booking reference, collection channel and verified payment evidence
  • Intended rider, purchaser, payer and authorised recipient
  • Variant, colour, pack configuration and accepted revision
  • Battery-plan provider and agreement reference where applicable

Operational bottlenecks to check

The online booker is not the purchaser

A relative’s contact appears on the booking while another person is meant to own the scooter. Resolve the correct identities through the actual seller’s process before billing; do not overwrite the payment trail.

Same colour, different pack or charger

The counter substitutes a visually similar scooter or charger and loses the accepted specification. Preserve variant and equipment references and obtain the relevant technical and buyer decisions.

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. Connect the counter enquiry

    Find the original brand booking or earlier visit without merging different riders or purchases. Confirm the contact’s role and record the question still preventing a decision.

  2. 2. Record the model experience

    Identify the test scooter and feedback. Refer compatibility, technical or permitted-use questions to the appropriate authority rather than promising that another variant behaves identically.

  3. 3. Agree the exact package

    Record colour, variant, supplied battery arrangement, charger and selected extras. Retain any new revision and the purchaser’s decision before allocation.

  4. 4. Match physical items

    Check the actual scooter and included equipment against the accepted package. Record an absent charger, missing pack reference or held unit separately; a carton count alone cannot prove a complete customer supply.

  5. 5. Complete the retail handoff

    Check the selling entity and applicable external responses. Record the actual recipient and supplied items, preserving outstanding optional accessories or account queries under the agreed terms.

  6. 6. Reconcile money and follow-up

    Match the original booking collection and later receipts without crediting the same token twice. Send unresolved charging, warranty or account questions to their actual provider with the accepted package reference.

Industry reports to connect with

  • Enquiries awaiting rider, purchaser or original-booking clarification
  • Variant or battery-plan revisions awaiting purchaser acceptance
  • Scooters held, available or allocated by actual identity
  • Incomplete charger, pack or accessory supply by order

Questions before implementation.

When should electric scooter dealers consider lead management?

For new scooter retail enquiries where the rider, payer and online booker can be different people. A walk-in, brand referral or returning contact asks about buying an electric scooter.

What should we bring to the requirements discussion?

Bring anonymised examples of Original contact or brand booking reference and communication permission; Intended rider, purchaser, payer and requested model; Test-ride outcome, pack or charger question and next responsible 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. Connect the scooter rider’s questions with the purchaser, original booking and responsible counter adviser. 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 does not promise range, approve riding eligibility or create a confirmed vehicle allocation.

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. Contact, purchaser and intended rider remain distinguishable. 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