The vehicle has to fit the load
Goods type, weight, handling needs and vehicle class belong in the booking decision—not in a last-minute call at the loading bay.
Concept · discovery
Mazboot / on-demand truck booking
Freight, from booking to proof.
A concept for shippers, drivers and fleets that keeps vehicle selection, loading, live execution, exceptions, delivery evidence and settlement connected to one job.
For India and the Middle East · initial shipper vertical and corridor under validation
Concept experience · illustrative synthetic dataDispatch & fleet console
The buyer problem
A booking is only the beginning.
The service earns trust in the physical handoffs: choosing suitable capacity, coordinating loading, responding to exceptions and closing the delivery record.
Exceptions need an owner
A delay, detour or failed delivery needs a visible status, a person responsible and a next action. A map pin alone does not resolve it.
Delivery is not finished at the gate
Loading evidence, milestone records, proof of delivery and settlement documents need to remain attached to the same job.
The operating flow
One job record. Eight accountable moments.
From load details to settlement, the concept keeps the operational story together instead of scattering it across calls, chats and documents.
- 01
Describe
Goods, weight, handling and locations
- 02
Select
Recommended vehicle class
- 03
Quote
Clear terms before acceptance
- 04
Match
Driver or fleet accepts the job
- 05
Load
Checklist and photo evidence
- 06
Track
ETA and geofenced milestones
- 07
Deliver
Photo and signature placeholder
- 08
Settle
Invoice and payment status
Proposed capabilities
Built around the work, not just the map.
Each capability is part of the discovery concept. Scope, accuracy and operating procedures would be validated in a bounded pilot.
01Shipper app
Load-aware booking
Capture goods type, weight, locations and handling requirements before suggesting a vehicle class.
02Booking flow
Quote and driver matching
Present an illustrative quote, then coordinate acceptance with a suitable driver or fleet.
03Tracking
Execution visibility
Follow the assigned vehicle, ETA and geofenced milestones through one shared job record.
04Dispatch console
Dispatch exception queue
Bring delay, detour and failed-delivery scenarios into a focused queue for review and action.
05Evidence chain
Proof that stays with the job
Connect loading checklist photos, delivery photos and a signature placeholder to the delivery record.
06Finance handoff
Settlement context
Keep invoice and payment status alongside the agreed terms and delivery evidence for reconciliation.
Value by role
The same delivery, seen differently.
Shipper
Confidence that the requested vehicle fits, the delivery is progressing and the evidence is retrievable.
Driver
A legible job, loading instructions, navigation handoff, delivery steps and visible settlement status.
Fleet & dispatch
A jobs board, fleet map, exception queue and programme measures such as utilisation and on-time performance.
Finance & support
The agreed quote, delivery evidence and payment state in one record for reconciliation and dispute handling.
Safety, trust & evidence
The evidence travels with the freight.
A shared record can make handoffs clearer. It does not replace physical checks, professional review or an accountable operator.
Designed to support operational control; no compliance or certification claim is made.
01
Known participants
Identity, driver and vehicle document checks are intended requirements. Verification methods and eligibility rules need market validation.
02
A recorded loading handoff
Checklist responses and photos create a shared record of what was loaded and its stated condition.
03
Meaningful milestones
Geofenced arrival and departure events are designed to add context to location tracking, not replace operator judgement.
04
Delivery evidence
Photo and signature placeholders keep the proposed proof-of-delivery step explicit without implying a legally validated process.
Honest validation roadmap
Prove the operation before scaling the marketplace.
Mazboot has no public service availability to announce. Discovery starts narrow, and each stage depends on evidence from the one before it.
DiscoverCurrent focus
Choose one freight problem worth solving
Interview shippers, drivers, fleet operators and finance teams. Select a narrow shipper vertical or corridor and document the real exception paths.
Corridor hypothesis · job and exception maps · baseline measuresPilotEvidence required
Operate the smallest complete job loop
Test booking through settlement with explicit operational support, agreed measures and a go / no-go review. Automation follows learning, not the other way around.
Vehicle fit · matching reliability · exception workload · delivery evidenceReadyBefore any launch
Prove obligations and economics
Review transport, insurance, payments, tax, privacy and document requirements for the selected jurisdiction; validate supply and unit economics.
Reviewed procedures · support model · sustainable operating caseFrequently asked questions
Clear about what exists—and what does not.
01Can I book a truck with Mazboot now?+
No. Mazboot is a Concept · discovery product. The screens and jobs shown here use illustrative synthetic data and do not connect to vehicles, drivers, payments or a live dispatch service.
02What kind of freight is the concept for?+
The concept is for on-demand truck booking, but the first shipper vertical, goods types and corridor have not been selected. Discovery will test where a focused operating model can address a specific reliability problem.
03How would vehicle recommendations work?+
The proposed booking flow uses goods type, weight, handling requirements and locations to suggest a vehicle class. The rules and their operational accuracy would need validation with shippers and fleet operators before use.
04Does live tracking resolve delivery exceptions automatically?+
No. Tracking provides context. The concept gives delays, detours and failed deliveries a visible exception queue so an operator can review the situation and own the next action.
05Are proof of delivery and settlement already supported?+
They are represented in the concept as required steps in the job record. Legal acceptance, invoice requirements, payment providers, reconciliation and dispute procedures all require market-specific design and validation.
06How can a shipper or fleet contribute?+
Bring a recurring booking or delivery problem, the corridor where it happens and the current evidence you use to resolve it. We are seeking grounded discovery conversations in India and the Middle East.
Explore the concept
Follow one job all the way through.
Step through the shipper, driver and dispatch experience, then bring us the corridor and delivery problem you know best.