Skip to main content
GullySystem
Automotive

Business solutions for Taxi operators

Explore software for work such as “Direct ride requests and future taxi reservations”. Review each business function below, including when it fits and what to check before implementation.

Taxi operators

How the business operates.

The dispatcher takes a telephone booking while another driver reports a stand pickup. Both rides need a trip record, but only one passed through the reservation desk. A taxi operator must reconcile those operating records with what each driver collected and what reached the office. This scope covers directly managed taxi journeys from calls, a stand or permitted digital requests, including future reservations and accepted outstation work. It focuses on dispatch decisions, actual ride outcomes and shift collection records. App-origin work remains a separate source when the operator actually handles it. The workflow is a requirements proposal, not a claim that automated dispatch, live maps or payment processing are installed.

Booking and reservation desk

Record pickup details, intended passenger, fare basis and agreed payment method. Distinguish immediate requests from future reservations. A request is not a confirmed pickup until the operator has made and communicated its actual booking decision.

Dispatch and shift control

Keep driver availability, current assignment and vehicle identity aligned with reported events. Record an accepted dispatch separately from an offer or message. If a driver releases a future job or a ride runs beyond the planned end, review the next commitment instead of assuming capacity.

Trip completion and fare review

Retain the actual journey outcome, authorised changes and supporting toll or waiting records under the agreed fare basis. A cancelled ride, passenger not found and completed journey are different events. The dispatcher does not invent a completed fare to clear a driver from the queue.

Collections and driver reconciliation

Separate customer cash collected by a driver, money paid directly to the office and account fares not yet collected. Reconcile the driver’s handover with the underlying trip references. Driver remuneration, hire charges or other agreed balances need their own supported treatment.

The records that hold the operation together.

  • Booking source, passenger contact and pickup or destination details
  • Requested time, confirmation and later change history
  • Agreed fare basis, inclusions and payment method
  • Driver shift, vehicle identity and accepted dispatch
  • Stand or direct-driver pickup linked to the operating record
  • Actual trip outcome and supporting charge evidence
  • Cash, office payment or account-charge reference per trip
  • Driver handover, verified office receipt and shift difference
  • Bill or receipt correction with authorised refund outcome

Operational bottlenecks to check

A future booking loses its driver

The assigned driver releases the job but no replacement accepts. Retain the unassigned state and customer communication decision instead of keeping a confirmed driver name from the earlier plan.

One ride produces two payment claims

A driver reports cash while the passenger says the office was paid. Compare the actual evidence and collector before changing either record or charging again.

Fare extras were not agreed

The passenger disputes waiting or a changed route. Preserve the original basis, actual event and decision on the contested charge rather than modifying the starting quote.

Shift closure conceals a cash difference

A completed trip list does not prove money was handed over. Separate driver collection, retained amounts under agreement and actual office receipt, with each discrepancy owned for review.

Follow the work across teams.

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

  1. 1. Capture the ride request

    Record the pickup and destination with the agreed fare basis. A regular rider’s history is context; confirm the current journey instead of silently repeating an old destination.

  2. 2. Make the booking decision

    Check capacity for the requested work and communicate the actual decision. Future reservations remain subject to active allocation review; no message alone proves a driver has accepted.

  3. 3. Record the assigned trip

    Link driver, vehicle and source booking. Add direct-driver or stand pickups through the operator’s actual process so they do not disappear from shift reconciliation.

  4. 4. Preserve the actual outcome

    Record pickup, completion, cancellation or unsuccessful collection with the source evidence. Retain changed destinations and disputed additions separately from the original fare agreement.

  5. 5. Reconcile customer money

    Identify who collected the payment and how it was verified. Keep an account fare outstanding when nothing was collected, rather than requiring the driver to report cash that never changed hands.

  6. 6. Close the shift record

    Compare recorded trips, collections and actual office handover. Leave unexplained differences assigned for review; ending a shift does not settle driver pay, customer credit or a pending refund.

Roles and responsibility boundaries.

Booking clerk

Confirms the passenger request, fare basis and contact permission, then passes the accepted booking and later changes to dispatch.

Dispatcher

Allocates actual capacity and retains rejected, changed and cancelled assignments.

Driver

Reports actual ride events and collections with the agreed supporting references.

Cashier or collection reviewer

Verifies customer receipts and driver-to-office transfers without recording the same money twice.

Operations manager

Resolves trip and shift discrepancies while preserving the original reports.

Reports your managers need.

  • Requested rides awaiting a booking or dispatch decision
  • Future reservations with released or conflicting assignments
  • Completed, cancelled and passenger-not-found trip outcomes
  • Trip charges awaiting evidence or dispute review
  • Cash held by collectors and verified office handovers
  • Driver shift differences and unmatched customer payments

Connections to scope

  • Phone, messaging or web requests can be entered with their original references. Notifications and booking imports require supported access; message delivery does not confirm a ride.
  • Driver-reported trip events and fare evidence can be recorded directly. Meter, navigation, location or platform feeds require separate verified scope.
  • Accounts and payment-provider statements support receipt verification. Platform settlements and driver remuneration are separate reconciliations where applicable.

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.

Rebuild a mixed booking period

Compare desk bookings, a stand pickup and future reservations using actual operator records. Identify which events establish acceptance and which only record a request.

Test dispatch exceptions

Review a released future job, changed destination and unsuccessful pickup. Preserve the original assignment and actual outcome without inventing a replacement or arrival time.

Reconcile a driver handover

Trace customer cash, direct office payment and account fares through the shift. Test a duplicate payment claim and a refund awaiting execution before treating balances as settled.

Limitations to settle before implementation

  • School transport, scheduled employee routes, patient transport, self-drive hire and specialist accessibility services require separately confirmed scope.
  • Vehicle and driver eligibility, local tariff requirements and permission for particular pickup locations remain the operator’s responsibility with the relevant authority.
  • A record does not establish arrival, vehicle availability, the route taken, earnings or passenger-safety outcomes.
  • A trip status does not prove physical location, passenger collection, bank settlement or the correct treatment of driver remuneration.

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.

  • Direct ride requests and future taxi reservations
  • Accepted dispatch and actual journey outcomes
  • Stand and direct-driver trip records
  • Fare evidence and customer billing review
  • Driver cash handover and shift reconciliation
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