eLogii allows users to set up branding for Tasks, depending on the number of brands you are collaborating with and the level of customizability you would like to have per brand.

Branding can be defined on the Task level by specifying the brand name, brand logo image, and the color associated with that brand, which will be applied to the tracking page.

This can be set up in Task ⇒ Details ⇒ Edit ⇒ Brand section.

This is an example of how a branded Tracking page can look:

This information can be added through CSV import or API.

Tracking pages can be branded in great detail and adjusted to fit the brand's aesthetic and signature colors.

Users can create tracking page sets associated with each brand they work with and apply them to Tasks associated with that brand.

Each of the branded tracking link sets can be different in terms of stylization, as well as the options it offers. For example, if you work with brands that would like to allow customers to reschedule Tasks, you can enable that option on the tracking page set dedicated to those brands.

Every aspect of the customer experience can be tailored to match each brand’s identity, from logos, status messages, and support details to tracking page colors and visible Task segments. You can also control whether customers are able to download the Proof of Delivery as a PDF, ensuring a fully customized and brand-consistent experience.

Once a tracking page set is set up and created, it can easily be applied to the brand associated Tasks either on API import or through Task rules.

If your account has the Advanced notification system enabled, you can apply specific brand-related notifications and notification rules. Users can choose to have either branded Email notifications or branded SMS/Viber notifications.

For example, if your business works with 5 brands and requires branded notifications to fulfil each of the brands' requirements, eLogii allows you to set that up.

For all event-based notifications, make sure they’re enabled; otherwise, the system won’t send any notifications, regardless of how the rest of the configuration is set up.

Users can now create fully branded email notifications, tailoring both the customer order tracking experience and the rules for when notifications are sent. This gives users the flexibility to define different trigger events, content, and designs for each brand they manage.

Let's look at the following configuration example: Brand A wants to send email notifications to customers that contain:

The setup will be as follows:

Email templates should be created for each trigger condition to ensure all four notification scenarios are fully covered. This means setting up a dedicated template for every event where notifications are required; specifically, Task Created, Route Start, Task Failed, and Task Completed, so each communication is aligned with the context of the event. The notification recipient should be set as the delivery contact.

Below is an example of how one of these templates would appear when tasks are created in the system, providing a clear reference for structure, content, and branding.

In the example, the HTML was edited to include the requested elements, along with the matching branding information. The email should look like the image below when the customer receives it:

The next step is to set up the template application rule for the Task Created trigger event for the Delivery contact. The Template rules should also be adjusted to apply the right template. For example, a rule can be set that will check the brand name associated with the Task, and based on that, decide which brand notification should be sent.

Make sure the correct template is selected for the specific brand you want to target. In this case, the rule is triggered based on the configuration.brand.name field, where a specific brand name is defined, ensuring that the notification is only sent when that exact value is present. Of course, different trigger conditions can be set.

The rule can look something like this:

The user should also ensure that the rule is enabled, so that the defined trigger conditions can correctly activate the appropriate template. This is crucial, especially if multiple rules are set up for different brands.

This process should be repeated for all brands and all notification types the customers should receive (in this example, users should set up templates and template application rules for the following event triggers: Route Start, Task Failed, and Task Completed).

For this specific use case, this setup is sufficient. However, if there are certain types of Tasks you’d like to exclude from customer notifications, you can define send condition rules to control exactly which Tasks should trigger notifications and which should be skipped.

To enable SMS notifications, a few configuration steps are required. Users must first create an account with one of the supported service providers that eLogii integrates with, such as Twilio, Apifon, LinkMobility, or Plivo.

Once the account is set up, users will need to enter the required access credentials into the platform. These credentials vary depending on the provider.

For example, Twilio requires an Account SID, Auth Token, and a phone number, while Apifon only requires a Client ID and API key, allowing the system to securely connect and send SMS notifications through the chosen provider.

Let's look at a use case example for branded SMS notifications: Brand B wants to send SMS notifications to customers when the Task has been scheduled for delivery and when the Driver is En Route to their destination that contain:

As was the case with Email notification templates, SMS templates also need to be created for the following events - Task Scheduled and Task En Route. When creating these templates, ensure that the Delivery contact is selected as the Contact type, SMS is selected for Channel, and the event is either Task Scheduled or Task En route (depending on which template is being made).
​

Template tags are used to indicate which Task elements should be picked up by the notification and sent to the customer. In the example below, we've included all the requested information that should be displayed to the customer.

Users are free to edit the notification text content however they like.

The rest of the template application rule setup is identical to that of the Email notification setup.

For the Task Scheduled event triggered for the Delivery contact, a rule should be set up that tells the system to apply the right template for the right brand. The rule setup should look something like this.

This way, we ensure that the desired template is applied only for Tasks that have this specific Brand name associated with them.