These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Truck Dispatch System
- Frequently asked questions
Questions, answered
Answers about planning, dispatch review, warehouse handoff and delivery evidence.
Truck Dispatch System
10 questions
Can't find it? Write to support@erp.ai.
How do I get started?
Click Get started, then use Proto to configure Truck Dispatch System for your business. Start with a dispatch shift and representative loads whose pickup, delivery and resource evidence your team can reconcile. Prepare active drivers, ready vehicles and the transport partner directory before importing open work.
What does the dispatcher prepare?
Dispatcher prepares the load, original promised delivery and ordered stops, then links the driver and vehicle with a committed start and end. The resource review checks eligibility, readiness and competing assignments before the load reaches Transport Supervisor for release review.
How do we check an assignment conflict?
Compare the complete assignment intervals for the same driver or vehicle, including held, confirmed and dispatched work. A prior job running late needs attention before the next commitment is released. Review the current resource evidence again after a substitution.
Who approves dispatch?
Transport Supervisor independently reviews the current load scope and records an approval, rejection or return with a reason. Dispatcher resolves returned work before seeking another decision. A change to reviewed scope requires a decision on the current revision.
Is an approved loading handoff already completed?
Approval authorizes the reviewed warehouse work. Warehouse Coordinator records the actual handover time and completes the handoff when the driver takes custody. Dispatcher compares that evidence with pickup rather than assuming that approval means the truck has departed.
What delivery proof can we retain?
Keep the proof reference on the delivery stop and attach supporting evidence to the load. Record a useful document title, evidence type and visibility. Agree which source establishes delivery and who checks the document before treating the operational outcome as complete.
How do we measure a late delivery?
Compare actual delivery with the original promised delivery time using the agreed time zone and completion rule. Stop arrival and departure provide context for the delay. Preserve the original promise when a revised estimate is discussed, and investigate delivered records that still lack an actual time.
What happens when an action fails?
Operations Analyst inspects the existing action receipt and linked effects before any repeat attempt. Unresolved discrepancies stay visible for review until the authoritative source confirms the outcome. Transport Supervisor decides the permitted correction, and external work is not repeated by reconciliation.
Can we connect fleet, warehouse and accounting systems?
Yes, as configured connections with agreed record ownership and stable source references. Fleet activity, warehouse inventory movement and carrier settlement each retain their own authority. Use the integration plan to define the evidence exchanged and rehearse uncertain outcomes.
Is there a per-user subscription?
There is no per-user fee. The base account and ordinary manual work in the official interface are free. Machine work, retention beyond included allowances and model usage follow the platform rate card; implementation is priced separately. See pricing for the current policy and credit behavior.
Set up Truck Dispatch System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.