Yes, although there could be a gap in the tracking data if the second driver doesn’t already have the app installed.
We unlink the phone number from the shipment, but the phone number and the tracking approval for it is maintained. That way if another shipment is created for the same driver, they don't need to re-approve tracking through the mobile app.
Potential reasons for not receiving a verification code include:
An issue with the mobile carrier system
An issue with the project44 system
Solution: Escalate to p44 support. You can always use 444-444 to verify and get the app running in the meantime.
There are a few potential reasons for why you are not receiving GPS positions of a shipment:
Potential Reason 1: The app does not have the right permissions. DriveView needs to run and collect GPS positions in the background to function properly. For users to provide that in Android 10, they have to adjust their settings for the app to allow location access. We cannot ask for these permissions directly from the app anymore.
Solution: Make sure the driver has set up the app correctly. See these instructional videos:
Potential Reason 2: The app was “killed” on the mobile device either accidentally by the user or the phone/device shut off/restarted.
Solution: Confirm with carrier that the driver has the device ON and the app is running (request a screen-shot if needed).
Potential Reason: the driver is not receiving notifications from the DriveView app is because the user must allow notifications for DriveView.
Solution: Make sure you have allowed notifications for the DriveView app. To do this, follow the steps below depending on the type of phone you have:
For Android: Settings > Notifications > “See all” > Project44 = ON
For iOS: Settings > Notifications > DriveView > Allow Notifications = ON
Extra-large font size is not supported.