This feature allows users to set custom POD titles to better fit their business needs. By default, how the names of POD actions are displayed in the Driver app mirrors the actual action names from configuration. For example, Capturing the photo will always be displayed as "Photo" in the Driver app, since the name of this action in Configuration is "Photo" as well.

To change how the POD action name is displayed in the Driver app Navigate to Configuration ⇒ Task Actions (POD) and enter the desired name for any configured action in the box under it.

Once you've set everything up, click Save. After saving your settings, POD action names will be changed and it will look something like this:

It is also possible to have multiple POD action of the same type. For example, if you would like to have the option to add multiple Comment types of POD actions, you are able to do so by selecting the same action.

You can use these two features in tandem with each other, which is ideal if your workers need to document specific things after completing the Task.

For example, if they need to document whether the package was received and if the customer took the invoice, you can configure two Yes/No options. One could be for "Package received" and the other one for "Invoice taken".

Alternatively, if your workers need to write a report after completing their Task, you can have multiple comment actions whose titles specify which information workers need to write down.

As is the case with regular POD actions, these ones will be stored in eLogii within Task History.

Custom POD forms let you create PODs from scratch. For this feature to be available to you, you need to have Custom fields enabled on your plan, because Task custom data is used for creating custom POD forms.

To set up custom POD forms you need to go to Configuration ⇒ Custom Fields ⇒ Task fields. You are free to specify which type of POD field you would like this to be. For example, if you decide when the next visit to the customer will be on the spot, Driver can enter that date in the appropriate field once they finish working with the customer. In this case you would want to set up a Date custom field like in the example below.

Next, you need to navigate to Configuration ⇒ Task Actions (POD) and select Form from the dropdown and select the form you want to use. You can select multiple forms at once. Make sure that your Form name is changed to match how you would like the action to be called, otherwise, it will keep the default name and Drivers will see it as Form. Once you're happy with the setup click Save.

It should look something like this in the Driver app.

If you include multiple custom fields in one form they will all appear in it once the Driver selects the form. For example, if you would like Drivers to add comments to the Next appointment i.e. notes for what to bring next time, they can do that if you attach a text field to the form. To achieve this, create a custom field whose Field type is Text / Number

and Value(s) type is Text. Once you save it, add it to the form and this is how it would appear on the Driver app:

It's also possible to do this on a Task level, so if you have a Task with different POD requirements, once you create it in eLogii you can configure it in Task ⇒ Actions (POD) and specify the Custom POD form for the Task. Click Save once you're happy with the setup. This will override the general settings for Task actions, i.e. settings from Configuration, for this specific Task.

You can also configure this on a Customer level and specify unique POD requirements if it's specific for a customer. To do this go to Customer ⇒ Task defaults and under Task actions (POD) select the toggle next to Actions to use from System to Override. Once you toggle this, you will be able to make adjustments. These presets will apply exclusively to Tasks associated with this specific customer and the setup from Configuration will be overridden by this one.

In addition to all this you can set some custom fields to be read-only, and have others customizable by your Drivers. This is especially useful for cases when you want to have some information visible to the Drivers, but not have them alter it.

To set this up, go to Configuration ⇒ Driver App

You can find 2 options:

It's important to note that, even though custom PODs are set up from the Custom fields section, and then through the Task Action section, once they are added as PODs and populated by Drivers from the Driver app, they will be treated as all standard PODs. This means that you will be able to view them in Task History, and in case you want to create, for example, a Recurring Task from a completed Task which has POD data collected, the documented information will not be transferred to the Recurring Task (because documented POD data is not transferred). Instead, the Task in its default state will be created as a template.

​