Driver App Connectivity
- 1. Inviting a Driver to the App
- 2. Driver List States
- 3. Driver App + Carrier TMS - Integrated Functionality
Carrier TMS connects with the Zuum Driver App. When connected, drivers who are assigned to a load receive information about that load, can update their status through the app, can be tracked, can log issues, and can upload documents related to the load.
1. Inviting a Driver to the App
Drivers are invited to install the mobile Driver application in several ways.
A. New Driver Creation
When a new driver is created, the Admin enters that driver’s mobile phone number. The system uses the driver’s mobile phone number to send the driver an SMS with a link to download the app.
B. Resend from Driver’s List
When a new Driver is created, a button appears in the driver’s list that allows the dispatcher to “Invite to App”. This button sends the SMS with the link to download the app.
When a driver successfully downloads and logs into the app, the button should disappear.
C. Driver Assigned to Load
When a driver is assigned to a load,
IF the driver has not yet downloaded and logged into the app, the system should send the driver an SMS with the link to download the application.
ELSE the system should push the load info to the Driver’s app.
Invitation SMS Text:
Please see instructions below for Zuum App Tracking1st step:
Download app from here:
Log in with your phone number (you do not need to “sign up”).
Insert the code you’ve received through SMS into the app.
Go to the jobs tab and click to see your load
Scroll all the way down and click “en route to pick up”
2. Driver List States
New driver added, app not installed
When a driver has been added, but has not yet installed and logged into the Driver app, the driver’s “On Mobile” light should be red, and the “Invite to App” button should be visible.
Note: The “Status” column refers to whether the driver is “Active” or “Not Active”. This is not related to the app.
New driver installs app and logs in
When a driver installs the application and logs in, the “On Mobile” light turns green, and the “invite to app” button disappears.
3. Driver App + Carrier TMS - Integrated Functionality
When a driver that was invited by the Carrier TMS has successfully installed the application, and logs in with the mobile phone number that was associated with the driver’s user account on the Carrier TMS, that driver’s account should be able to send and receive data from that carrier.
With this connection in place, the following functionality is possible:
A. Shared Load Data
When the connected driver is assigned to a load, some load information should be sent to the driver’s mobile application. The load information should be limited to the same data that is sent to drivers who are connected to carrier web.
Drivers should not see any information about the load financials.
General information sent to drivers should include
A summary of each load that has been assigned to a driver should show up in the “Jobs” list in the driver app, subject to existing App functionality and UI.
When the driver taps on a load summary, the complete details of the load that were sent from the Carrier TMS should display.
B. Load Status Updates
When the connected driver is assigned to a load, the driver should be able to update the status of the load, subject to the Driver app’s existing logic. When the status is updated on the Driver’s app, the changes should be reflected on the Carrier TMS load details page.
When the connected driver is assigned to a load, location data from the mobile app should be used to update the driver’s location in the Load Details map. The location icon should reposition on the map to reflect the driver’s real world location.
The “Driver Online” light should be green.
If the user presses the “Refresh Driver Location” button, it should get the driver’s location at that time.
D. Uploading Proof of Delivery (POD)
The driver should be able to upload documents, such as the Proof of Delivery. When this is done (subject to the app’s existing logic), the POD should be saved in that load’s “Docs & Images” section, and should reflect that it was uploaded by the driver.
After the driver uploads a POD, the load’s status should automatically be updated to “POD Uploaded”.