A Delay and Proof Layer for Phone-Based Dispatch

Vehicle data and freight records are moving into one company

On August 20, 2026, Indian logistics technology company Fleetx.ai announced that it would acquire transport management service Pando.ai. The deal connects Fleetx’s vehicle location, route, driver, and vehicle-status data with Pando’s freight procurement, transport planning, carrier collaboration, and freight-cost verification functions.

The change points toward a single flow spanning transport contracts, actual movement, delivery confirmation, and cost settlement. In Korea, many intermediary logistics contracts are still arranged by phone and much of settlement remains manual.

Pando plans to retain its independent brand and existing management team. The acquisition price and detailed product-integration schedule have not been disclosed, so what is currently confirmed is the direction presented by the two companies, not a completed result.

Fleetx says its service connects more than 515,000 vehicles and tracks more than 200 million kilometres of movement per day. These are operating metrics published by the company, not independently verified figures.

Phone calls and paper still coexist in Korean field operations. In 2023, Yonhap News Agency reported that most intermediary logistics contracts were made by phone and that settlement involved substantial manual work. In a trial at one carrier covered by Electronic Times, processing 200 tax invoices fell from four hours a day to about 48 minutes.

A thin connection may sell before full integration

As large integrated transport systems grow, a small service that connects only delays, proof of delivery, and settlement through one order number—without eliminating existing phone dispatch—may sell sooner. This is the opening when the assumption that every company will move to a new system is wrong.

Consider an example. Mr. Kim, who runs a 12-person food-ingredient transport company in the Seoul metropolitan area, assigns dozens of daily shipments among employees and independent truck drivers. Shippers send orders by email or phone. A dispatcher records them in a spreadsheet, calls drivers, and leaves the results again in a messaging app.

When traffic is heavy or loading is delayed, the driver calls the dispatcher, who then contacts the shipper and delivery destination separately. After unloading, photos of delivery receipts arrive across several messaging-app chats, and a settlement employee downloads them to match against transport records and tax invoices.

The information for one shipment is transferred at least three times: into an order spreadsheet, a chat with the driver, and a settlement file. When the person responsible is away or the driver changes, it takes time to find who changed the arrival time and which photo is the final delivery receipt.

A large integrated service is useful if every shipper and driver uses the same software. But if independent drivers change every day, resist installing an app, and each shipper requires different documents, a proposal to change the entire workflow may fail at the adoption stage.

What is needed then is not a new dispatch marketplace, but a record board placed on top of existing phone dispatch. Once Mr. Kim confirms a dispatch, an order number is created. Without installing an app, a driver uses an SMS link to tap departure, delay, and arrival, and uploads a delivery-receipt photo through the same link.

The shipper views only the required shipment through a web link, while the settlement employee reviews only jobs with complete proof. Rather than storing vehicle location continuously, the service can collect it only from the start to the end of a shipment, making it easier to explain to drivers.

Phone calls will not disappear. People still need to decide responsibility for accidents, damage assessments, freight-rate changes, and disputes between drivers and shippers. The service should focus not on making those decisions, but on keeping the times and evidence around the calls in one place.

Elsewhere, teams started by connecting one problem

Godrej Consumer Products and Pando in India

Indian consumer-goods company Godrej Consumer Products moved the work of finding carriers and comparing quotes across multiple factories and transport legs into Pando. It handled carrier quote requests, condition comparisons, and choices of vehicles and contract arrangements in one place. Contract prices were not disclosed.

The company reported that the number of carriers it could contact doubled. This is a customer case published by Pando, not independently verified performance, but it shows that a product can start with the narrow problem of carrier procurement before vehicle tracking.

SCIENTIA and Track-POD in Australia

Australian pipe manufacturing and distribution company SCIENTIA adopted Track-POD to reduce damage disputes and redelivery costs. Dispatchers planned routes using vehicle capacity and driver schedules, while drivers recorded freight condition and delivery through real-time location tracking and electronic proof of delivery.

Track-POD’s public pricing starts at $49 per driver or vehicle per month on annual billing. SCIENTIA reported a 100% delivery-success rate, a 99% reduction in dispute costs, and a 33% reduction in fuel costs, but all are customer results published by the service provider.

Voyager Express and PCS in the United States

US carrier Voyager Express began with 10 vehicles and then used PCS for dispatch, location confirmation, accounting, and driver document submission. There is no standard public price; customers receive a sales quote based on their configuration.

According to a PCS customer case, Voyager grew to more than 200 vehicles, and more than 75 drivers processed transport documents on mobile phones. It reported a 98% on-time pickup and delivery rate and two to three days from delivery to invoicing. These figures were also presented by the company and service provider.

Four small places to start

1. A delay notification board

• A service that sends the delay reason and revised arrival time selected by a driver to both the shipper and delivery destination, without changing dispatch.
• Used by regional carriers with five to 20 employees that frequently use independent drivers.
• A product that only reduces repeated phone notifications may be easier to adopt than one that changes both location tracking and dispatch.
• The first screen shows shipments by promised time, delayed jobs, the time of the last contact, and a call-now button.

2. A delivery-receipt collection box

• A service that automatically attaches delivery receipts and damage photos uploaded by drivers through an SMS link to the relevant order.
• Used by construction-material and machinery-parts carriers that collect paper delivery receipts by mail or messaging-app photos.
• Photo proof is increasingly a settlement condition, but requiring every new driver to install an app is difficult.
• The first screen has three work queues: no delivery receipt, unclear signature, and damage photo requiring review.

3. A settlement-readiness checker

• A service that compares transport records, delivery receipts, and tax-invoice amounts and order numbers, then identifies missing documents.
• Used by accounting staff at small and medium-sized manufacturers that pay multiple carriers monthly.
• Even when vehicle tracking is accurate, payment is delayed if proof and billed amounts do not match.
• The first screen shows transport-job counts and original photos grouped into ready for payment, amount differs, and proof missing.

4. A location link that opens only during transport

• A service that shares location only from when a driver taps departure until unloading, then ends automatically.
• Used by furniture and industrial-equipment sellers that call for trucks as needed rather than operating dedicated vehicles.
• Many businesses find always-on fleet monitoring burdensome but still need to reduce calls asking when a delivery will arrive.
• The first screen shows a map of three current shipments, estimated arrival times, and the time when location sharing ends.

Why this matters where you are

Check whether transport work in your market still moves the same shipment details between phone calls, spreadsheets, chat threads, and settlement records. Carrier practices, required documents, and pricing will differ, but the reported examples show that one narrow handoff—carrier procurement, delivery proof, or delay updates—can be a useful place to start. Ask operators which handoff forces them to reopen old messages most often.

What to check in 30 minutes today

Call two regional carriers and ask just one question: during the past week, which made them reopen messaging-app chats most often—delay notifications, finding delivery receipts, or settlement matching? If one of the two has the same problem at least five times a week and is willing to show the processing flow for one actual order, that single problem may be worth building as the first service.