Skip to main content
GullySystem
Automotive

Appointment Scheduling for Taxi operators

Keep future taxi reservations, capacity decisions and later changes visible before dispatch.

Bookings and Appointments

Does this function belong in your operation?

For an operator accepting advance rides against actual vehicle and driver capacity. Immediate ride requests belong to the dispatch workflow.

A passenger or authorised booker requests a taxi for a future pickup.

Use the reservation record for future taxi requests that compete for actual vehicle and driver capacity. Keep the requested pickup separate from the operator’s accepted booking and later dispatch. A driver releasing a job leaves a real allocation gap until another assignment is accepted. Changes to time, location or trip scope need a recorded decision and customer communication. This module does not predict arrival or turn an unanswered message into a confirmed pickup.

Bring the records the workflow depends on.

  • Requested pickup, destination and passenger contact
  • Accepted trip scope, fare basis and payment method
  • Capacity review, booking decision and assigned follow-up owner

Outputs to check

  • Requested and confirmed future ride register
  • Unassigned or conflicting reservation list
  • Change, cancellation and dispatch handoff history

Follow the appointment scheduling 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 future request

    Record pickup location, intended passenger and requested work. A returning rider’s earlier booking is not confirmation of the new destination or fare basis.

  2. 2. Review usable capacity

    Check the actual availability needed for the journey, including preceding work and driver changes. A nominal free slot does not establish a suitable vehicle.

  3. 3. Record the booking decision

    Keep requested and accepted reservations separate. Record what was communicated to the booker without converting a provisional assignment into an arrival promise.

  4. 4. Maintain changes and allocation

    Retain changed time, pickup or trip scope with the decision and contact outcome. A driver releasing a reservation creates an allocation gap until the operator resolves it.

  5. 5. Pass the actual outcome

    Link the accepted reservation to dispatch or its recorded cancellation. Retain any agreed charge review separately from releasing planned capacity.

Who uses the module, and who approves?

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

Reservation clerk

Confirms the current request and communicated booking status.

Dispatcher

Reviews capacity and actual accepted assignments before the pickup.

Operations reviewer

Resolves released bookings, changed scope and conflicting commitments.

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.

Driver releases the future job

Retain the unassigned state and resolve replacement acceptance; do not leave the earlier driver displayed as confirmed.

Previous trip is still in progress

Review actual availability and the customer communication decision without assuming the car is free.

Passenger changes pickup after confirmation

Reassess the journey and retain the accepted revision and any fare decision.

Booking is cancelled after dispatch

Preserve actual operating events and refer any charge to the agreed terms; cancellation does not erase costs already incurred.

Can this work independently?

Reservations can use entered calendars and booking records. Dispatch confirms actual driver and vehicle acceptance; live traffic, routing and notifications require separately verified tools. Appointment status does not prove arrival, passenger collection or payment.

Systems and records it connects with

  • Current passenger request and accepted fare basis.
  • Driver and vehicle capacity review with dispatch reference.
  • Permitted customer communication and separate cancellation-charge decision.

Configure, test and introduce the workflow.

  • Trace a future reservation beside an immediate request without placing both in a generic appointment queue.
  • Test released drivers, overlapping work and changed pickup details.
  • Review a cancellation after dispatch while retaining its actual trip and financial references.

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 submitted request cannot appear as an accepted reservation without the actual decision.
  • Released assignments remain visibly unresolved until replacement acceptance.
  • Cancellation retains operating and charging references.
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.

See the full industry workflow, reports and implementation plan →

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

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.

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. 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.

Industry reports to connect with

  • 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

Questions before implementation.

When should taxi operators consider appointment scheduling?

For an operator accepting advance rides against actual vehicle and driver capacity. Immediate ride requests belong to the dispatch workflow. A passenger or authorised booker requests a taxi for a future pickup.

What should we bring to the requirements discussion?

Bring anonymised examples of Requested pickup, destination and passenger contact; Accepted trip scope, fare basis and payment method; Capacity review, booking decision and assigned follow-up owner. 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 future taxi reservations, capacity decisions and later changes visible before dispatch. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Reservations do not predict arrival, assure a replacement or establish operating permission for a pickup location.

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 submitted request cannot appear as an accepted reservation without the actual decision. Use this check when reviewing the first working version.

Talk to us

Discuss appointment scheduling 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