The main purpose of the Driver App is to serve as a digital Task/Job list for Drivers, to efficiently navigate them to their destinations, and to capture digital Proof of Delivery (POD).
The Delivery app has many use cases, and some of the steps may vary depending on the setup and how you intend to use the app. However, the two most common cases are Delivery and Field Service.
Basic Delivery Use Case
The most common delivery use case consists of the following steps:
Pickup - The Driver goes to the designated location (Usually a Depot or a Store) to pick up Tasks and loads them onto their vehicle.
Delivery - After completing the pickup, the Driver goes to the Task/Job end location, captures Proof of Delivery, and completes the Task.
Practically, the workflow would look something like this:
Step 1 - Logging in
Once the Driver opens the Driver app, they will be required to enter the following information:
Organization ID - This is how eLogii knows where to log in Drivers.
Username
Password
The login credentials are assigned on Driver creation and can be updated and changed anytime.
Once the Driver enters the appropriate organization ID, username, and password, they will be logged into their account in the Driver App.
Step 2 - Starting the Task (Pickup)
Once logged in, the Driver can start their route for today by tapping the Open Next Task button. This will take them to a list of pickups they need to perform.
They can also select their preferred navigation (Yandex, HERE Maps, Waze, or Google Maps) before heading over to the pickup location.
Once the Driver has arrived at the pickup destination, they need to tap the Arrived for X Taks button.
Next, they need to confirm that each Task has been picked up by tapping the Finish button under each Task. If multiple Tasks are at the same location, Drivers can tap the Finish All button to complete the pickup for all Tasks at the same pickup location.
Step 3 - Starting the Delivery
After completing the Pickup, the Driver should tap the Next Task button to start the delivery portion of the Task.
Similarly to the Pickup portion, Drivers can select their preferred navigation and start driving towards their destination.
Step 4 - Finishing the Delivery and Capturing POD
After confirming the arrival, the Driver should capture the required POD to complete the Task. Which POD options you have available and whether they're mandatory will depend on the configuration settings for the Driver app.
This example showcases signature capture, but you can also enable photo capture, barcode scan, confirmation, and more.
Please note that the POD capture step is completely optional, and if your business does not do this, you can skip this step entirely.
Step 5 - Starting the Next Task
After completing the delivery, the Driver can begin the next Task in the queue by tapping the Next Task button.
Basic Field Service Use Case
The biggest difference between the Delivery and Field Service use cases is that the Field Service use cases usually skip the pickup process entirely, as there is no package to pick up in the first place. For this type of use case, we recommend activating the Field Service Mode in eLogii, which automatically adjusts your account for Field Service needs.
Step 1 - Logging in
The Login is the same as it was for the Delivery use case. Once the Agent opens the Driver app, they will be required to enter the following information:
Organization ID - This is how eLogii knows where to log in the Agents.
Username
Password
The login credentials are assigned on Agent creation and can be updated and changed anytime.
Once the Agent enters the appropriate organization ID, username, and password, they will be logged into their account in the Driver App.
Step 2 - Starting the Job
To begin their route, the Agent should tap the Open Next Task button and tap Start to confirm they're on their way to the Job destination. They can also select their preferred navigation (Yandex, HERE Maps, Waze, or Google Maps).
Step 3 - Finishing the Job
Once the Agent arrives at the destination, they should tap the Arrived button to confirm they're on site for the Job.
After they complete the Job, they should capture the POD (if required) and tap Finish to confirm the Job's been completed successfully.
If no POD capture is required, then this step will not exist, and Agents will only be required to confirm they finished the Job.
However, if your business has more complex post-job requirements and Agents (or clients) need to fill out a form, you can fully support this by using eLogii's Form feature and setting it as a POD at the end of each Job.
Step 4 - Starting the Next Job
After completing the job, the Agent can begin the next one in the queue by tapping the Next Task button.
Failing a Task/Job and Reporting Issues
This is an optional step, but if you wish to document any issues with Tasks(either for the pickup or the delivery), you can enable and set up a Task issue Workflow and enable Task failure so that Drivers can fail Tasks.
Failing a Task on Pickup/Delivery for Delivery Use Case
In case a Driver encounters an issue either on the Pickup or Delivery step of the Task, the Driver should:
Tap on the Problem button located in the top right corner of the screen
Select why the Pickup/Delivery will be unsuccessful (or enter a custom reason, if enabled).
Tap the Fail button located in the bottom left corner of the screen.
Please note that the reasons for failure for both pickup and delivery are fully customizable. In addition, if any additional POD needs to be captured alongside the failure reason (for example, the Driver needs to provide their signature to confirm the action), that can also be configured.
Failing a Job for Field Service Use Case
In the case of a Field Service use case, it works the same, only without the pickup aspect of the Task/Job.
In case an Agent encounters an issue and cannot complete the job due to that issue, they should:
Tap on the Problem button located in the top right corner of the screen
Select why the Job could not be completed from a predefined list (or enter a custom reason, if enabled).
Tap the Fail button located in the bottom left corner of the screen.
Driver App Specifics
You can customize these base workflows by incorporating additional steps as needed. Recommendations for each use case type are listed below, but you are not limited to them. If a feature is listed under the Delivery use case but suits your Field Service use case, you are welcome to use it accordingly.
For Delivery Use Cases
Incorporating Items into Tasks - Items represent multiple things that need to be delivered to the same location. A Task may include multiple items, allowing you to track their status (whether they were delivered or not) and capture PODs for each item (if required).
To track item quantities, use the Quantity field when creating an Item. If this field is populated, the quantity will be displayed in the Driver app. If left empty, the quantity will not appear in the app.
Drivers can also mark individual items as failed if there is an issue. This works the same way as failing a Task, allowing them to report problems with specific items when needed.
Partial delivery - If enabled, partial delivery happens organically in eLogii if an Item is marked as failed or if the delivered item quantity is less than originally set for the Task.
For Field Service Use Cases
Start/ End Checklists - Checklists are a great way to help your team stay on track and perform specific actions before starting their routes and/or after completing them. They can be simple and show only a list of things workers need to check to confirm their completion, or they can be elaborate and detailed custom forms.
Editing Task/Job information - Field conditions can change, requiring the Agent to record important details. For example, during a diagnostic visit before the actual work begins, the worker may need to document key information to ensure nothing is omitted.
This additional information is usually stored in Task Custom fields. You can enable Agents to edit these fields for completed or ongoing Jobs.
To do this, they need to:
Tap the Tasks section located in the bottom right corner of the screen
Find the Job they wish to edit custom data for (if the Job has been completed, they need to select Show Completed)
Tap the 3 lines on the Job card and choose Edit custom fields.
Tap Save when they finish editing