Illustrative workflow. Example participants. Permitted records and actions are agreed during setup; this is not a permissions specification.
Office team
Drivers
Customers
Example participants. Permitted records and actions are agreed during setup; this is not a permissions specification.
01
Train around each role
Use the configured workflow to explain what office users, drivers and other participants need to do. Walk through a representative shipment from start to finish.
02
Make the handover practical
Identify the records the team maintains and the actions needed when information is missing. Agree who owns operational questions after rollout.
03
Confirm the support arrangement
Set out the support channels, hours, languages and responsibilities in the agreed scope. Training inclusions and service levels should be explicit.
Practical questions
Who should attend training?
The people responsible for the configured office, driver and partner workflow.
Are support hours fixed on this website?
No. Hours, channels, languages and service levels are agreed in scope.
What should the handover cover?
Daily actions, record ownership, missing-information follow-up and the agreed support route.