Skip to main content
GullySystem
Automotive

Business solutions for Fleet management companies

Explore software for work such as “Customer agreement and subscribed fleet-service scope”. Review each business function below, including when it fits and what to check before implementation.

Fleet management companies

How the business operates.

A fleet management supplier sells tracking software, telematics devices or a monitoring service to a vehicle operator. Its operating record connects the customer agreement, enrolled vehicles, supplied equipment where applicable, activation evidence and support history. A software-only provider has no installation or device-stock stage. The customer retains authority over dispatch, drivers and vehicle use; a supplier reporting an event does not take over those decisions. The following workflow describes requirements to review with the provider, including the boundary of any managed monitoring service.

Customer scope and agreements

Record the fleet use case, subscribed functions, customer administrator, payer and supplier responsibilities. A pilot has its own acceptance conditions; a successful demonstration does not make the entire fleet an approved paid order.

Enrolment and delivery

Match each authorised vehicle reference to the correct customer account and purchased service. Where hardware is supplied, retain its serial, installer assignment and acceptance record. Distinguish equipment delivered from a service that has started reporting.

Support and data review

Handle missing locations, incomplete readings, access issues and device changes against a numbered case. Record the observation time and upstream provider reference so a stale point is not presented as a current vehicle position.

Account service and billing

Compare contracted units with accepted additions, removals and the agreed billing basis. Follow renewal decisions with the customer buyer while support continues to record unresolved problems. Neither inactivity nor an unpaid invoice alone defines the contract decision.

The records that hold the operation together.

  • Customer service agreement, package and authorised administrator
  • Pilot scope, acceptance questions and customer decision
  • Vehicle reference and account mapping, with device serial only where supplied
  • Installation or software activation evidence and unresolved acceptance items
  • Support observation time, last available data and upstream case reference
  • Approved service additions, removals, renewal decision and billing period

Operational bottlenecks to check

A serial is linked to the wrong account

A swapped device can leave an old vehicle name on new data. Historical mappings need effective dates and review before the support team changes a customer-visible record.

A dashboard gap becomes an allegation

Missing data has several possible sources. Retaining the observed gap and investigation result prevents a support note being treated as proof of driver misconduct or fuel loss.

Accepted units and billed units diverge

An installer marks work complete while the customer still disputes activation. Billing needs the agreed trigger and its evidence, rather than a count of equipment boxes sent.

The buyer and daily user differ

Renewal discussions need the customer decision-maker and unresolved user issues. A dispatcher's complaint does not authorise cancellation; a buyer's signature does not resolve a data fault.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Agree the service boundary

    Record whether the sale is software access, equipment plus service or managed monitoring. Identify the contracting customer and the person allowed to approve vehicle additions and data access.

  2. 2. Confirm the delivery instruction

    Create the order from the accepted scope. Separate trial units from paid units and confirm whether equipment supply, fitting or an existing data connection is included.

  3. 3. Enrol and verify

    Create the customer-specific mappings and retain the actual activation result. For a device replacement, preserve the old mapping history; do not move another customer's records to the new serial.

  4. 4. Review acceptance

    Compare delivered functions with the agreed acceptance evidence and record open issues. Customer commercial acceptance and a competent installer's technical checks are separate records.

  5. 5. Handle service events

    Log missing or disputed data with dates, affected units and source status. Coordinate the responsible platform, installer or customer contact without assuming a communication gap proves a vehicle event.

  6. 6. Reconcile and renew

    Match chargeable units and service periods to the agreement. Record the customer's renewal, amendment or closure instruction and any authorised data-access or equipment-return tasks separately.

Roles and responsibility boundaries.

Customer account owner

Confirms the buyer, approved service scope and renewal decision. Records any installer or reseller involvement without assuming that partner is authorised to change the customer agreement.

Implementation coordinator

Maintains account and vehicle references, obtains enrolment permission and checks acceptance evidence. For hardware work, coordinates the competent installer; this role does not prescribe installation methods.

Support analyst

Records the affected account, vehicle, device or software connection and the time range of missing data. Requests only the access and evidence needed for the case and records escalation outcomes.

Customer fleet administrator

Approves authorised users, vehicle enrolment and operational use of reports. Driver instructions, employment decisions and vehicle deployment stay with the fleet operator.

Billing reviewer

Reconciles service periods and approved unit changes against invoices. Keeps reseller charges and end-customer charges attached to the correct contracting party.

Reports your managers need.

  • Ordered, activated and accepted units by customer and service package
  • Unresolved activation issues and responsible party
  • Support cases by affected unit, observation date and upstream dependency
  • Agreed versus billed units and service periods
  • Renewal decisions outstanding with open customer issues

Connections to scope

  • Customer-authorised vehicle and user files, with source and access rules reviewed
  • Platform or device status references where the supplier permits access; connection scope requires validation
  • Installer completion records where hardware fitting is contracted
  • Accounting invoice and receipt references for the correct contracting payer

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Separate business models

Review actual software-only, hardware and monitoring orders. Define which delivery stages apply to each; do not create fictional devices for software accounts.

Validate identities and access

Reconcile customer accounts, authorised contacts and active unit mappings. Test cross-customer access restrictions and preserve historical assignments before importing records.

Test difficult handoffs

Walk through partial activation, duplicate serial, stale readings and a disputed billing start. Confirm which party owns each correction and which customer approval is needed.

Reconcile the first period

Compare the service register with accepted changes and issued invoices. Review support access, unresolved cases and renewal notices with the responsible account staff before wider use.

Limitations to settle before implementation

  • This scope manages a supplier's customer delivery and service records; it does not operate the customer's transport business.
  • Device compatibility, fitting and technical investigation require the responsible specialist and product instructions.
  • A recorded alert or missing data point is not proof of an accident, theft, driver misconduct or vehicle readiness.
  • Platform access, data retention, monitoring authority and third-party connections require explicit agreement; no integration is presumed installed.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Customer agreement and subscribed fleet-service scope
  • Authorised vehicle enrolment and activation acceptance
  • Device delivery and installer coordination where contracted
  • Data-support cases, unit changes and renewal billing
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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