Configuration
Carrier, driver, shipment, load, stop, role, and policy setup.
Support
Help for the route, the rule, and the record.
Support covers the transportation process itself: configuration, connected data, role boundaries, workflow controls, and the daily questions that appear once dispatch is moving.
Support that follows the operating trace.
Complex transportation software becomes easier when help uses the same records and vocabulary as the team.
Workflow activation
Checks for carrier credentials, dispatch approval, and safe exception escalation.
Daily use
Guidance for consolidation, routing, driver assignment, events, and recovery.
Process review
Identify recurring disruption patterns and refine responsibility without losing the trace.
Common questions.
The fastest answer starts with the actual operating state, not a generic ticket category.
Can we plan before carrier integration?
Yes. Carrier and load planning can be configured first. External tender stays inactive until the required carrier credentials or messaging connection exists.
Who can release dispatch?
The assigned role and your approved dispatch policy determine release authority. The release remains recorded against the load, driver, and dispatcher.
How are delivery exceptions handled?
Exceptions retain severity, description, source shipment, delivery event, status, and mitigation ownership. High-severity events can trigger an internal escalation.
Where does Proto Agent fit?
Proto Agent helps people work with the application, understand records, and adapt processes within the ERP.ai environment and available usage.