The Advanced eLogii notification system enables users to configure notifications for a wide range of scenarios, along with templates that are automatically applied when specific conditions are met.
The advanced notifications can be accessed through Configuration ⇒ Email/SMS/Push notifications. If the Advanced notification system isn’t available in your view and you’re still seeing the default version, please contact your Customer Success Manager or reach out to the eLogii support team for further assistance.
Notifications
In this section, users have an overview of all the notifications created under each notification category.
Overview and Options
The notification categories users can create are Delivery Location Contact, Pickup Location Contact, Depot Contact, Driver, and Custom. These categories represent the recipient of the notification. This means that if a notification is set up under the Delivery Location Contact, it will be sent to the email address or phone number specified in the Task’s delivery contact details.
If you are looking for a specific notification, you can look it up by typing its name in the search bar above the category segments, as well as filter the notification based on channel, contact type, and trigger event.
The number next to the category name shows the number of notifications that have been created for each category. This number accounts for both enabled and disabled notifications.
Users can enable/disable any of the configured notifications they have, as well as edit or delete the notification.
Creating Notifications
Notifications can be created by clicking the Create Notification Button, and a pop-up screen will appear where users can configure the notification.
Users are required to specify the following information:
Contact type - This refers to the recipient of the notification, or in other words, the contact who will receive it once the trigger conditions are met. Delivery Location Contact, Pickup Location Contact, Depot Contact, Driver, or Custom can be chosen. If Custom is selected. Additional options will appear, which allow users to either manually enter recipient emails as comma-separated values (example1@example.com, example2@example.com, etc.) or specify which Task field the recipient information will be sourced from.
Channel - Users also must specify the channel through which the recepient will receive the notification. They can choose to either send an Email, SMS, or Viber notification. This will also change the message preview, depending on which option is selected.
Event - This will determine which event the message will be sent after. This is the trigger condition of the message. Users can select any of the Task State-related trigger conditions (for example, Task Created, which will notify the recipient when the Task is created in eLogii, or Task En route, which will notify the recipient as soon as the Task state is changed to En route). Users can also choose Route-related trigger conditions, which can send notifications to recipients exactly when the Driver has started their route or ended it. Lastly, Customer-related trigger conditions can also be set up, whose trigger conditions are when the customer changes the address on the tracking page, or when they reschedule the Task.
Template - Here, users need to specify which template to use for the message body. The message body and the HTML (in case of Email notifications only) can be edited by selecting the Edit template option.
When editing the template, specifically the message content for both Email and SMS, you can utilize various template tags eLogii offers.
There are additional options that can be configured when creating a notification. Users can configure rules around Send conditions and Template rules.
Configuring Send Conditions
By default, if no conditions are set, the notification is always sent when the trigger event occurs. If specific conditions are set, the notification is sent only if all set conditions pass the check.
To add a Send condition, click the Add send condition button. A pop-up will appear where you can configure the trigger condition. The interface is similar to the Task rule designer, and the same logic applies, including condition relationships (AND, OR), logical operators (=, >, is null, etc.), as well as element grouping and how groups relate to one another.
This example introduces additional conditions that must be met for a notification to be sent. While the rule is triggered upon Task creation, the notification will only be sent if the Task has a specific tag and is linked to a customer with a designated reference. Only Tasks that meet all defined conditions will trigger notifications to the intended recipients.
Users can define multiple send conditions for a single notification, and each one can be enabled or disabled, edited, deleted, or reordered at any time
Configuring Template rules
These rules determine which template will be used for the notification. This is especially useful when you have multiple templates and want to apply different ones based on specific conditions.
For example, if one of your customers requested to show specific Task information that is not necessary to the rest of your customer base, you can configure a template for their specific case and set a template application rule that will apply only if the Task is tied to.
To add a Template rule, click the Add rule button. A pop-up will appear where you can configure the trigger condition. The interface is similar to the Task rule designer, and the same logic applies, including condition relationships (AND, OR), logical operators (=, >, is null, etc.), as well as element grouping and how groups relate to one another.
Once template rules have been defined, users can select which template should be used when the conditions are met and click Save to apply changes.
The template rule can be adjusted or deleted.
Templates
Templates enable users to design various notification formats that can be applied to specific scenarios.
Overview and Options
If you are looking for a specific template, you can search for it by typing its name in the search bar above the category segments, as well as filter notifications based on channel, contact type, and trigger event, as well as origin type (system or custom).
The templates can be disabled/enabled, as well as edited, duplicated, or deleted.
Creating Templates
Templates can be created by clicking the Create template button, which opens a pop-up window where users can design a notification template to use when setting up notifications. These template presets will be applied when selecting them for the custom notification creation.
The following actions can be performed:
Name - Users are required to name the template for easier navigation and categorization.
Description - Optional field. allows users to specify more details around the use of the notification template.
Contact type - This is a required field that determines who will receive the notification. Available options include Delivery Location Contact, Pickup Location Contact, Depot Contact, Driver, or Custom. If Custom is selected, additional options will appear, allowing users to either manually enter recipient emails as comma-separated values (e.g., example1@example.com, example2@example.com) or choose a Task field from which the recipient information will be pulled.
Channel - Users also must specify the channel through which the recepient will receive the notification. They can choose to either send an Email, SMS, or Viber notification. This will also change the message preview, depending on which option is selected.
Event - For template creation, this is an optional field. This will determine which event the message will be sent after. This is the trigger condition of the message. Users can select any of the Task State-related trigger conditions
When it comes to adjusting the content of the template message if Email is selected, users can do the following:
Based on - This is an optional field that provides users with a template they can use as a starting point when composing the notification content. These are system default messages that can be used as is or adjusted in the message editor.
Form - This field contains the message content, where you define what information the recipient will receive. For example, if a technician visit is scheduled, you can include details such as the date and time of the visit, as well as the technician’s name. This information, or any other Task-related information, can be dynamically inserted using template tags. The QR code can also be included in the message.
Additionally, to ensure customer inquiries and concerns reach the right team, you can include relevant contact information within the notification message, preferably in the Bottom contents section. For example, if you’re working with multiple brands and handling package pickups, you can reference Task fields that store each brand’s contact details (likely the pickup contact fields) so they’re automatically included in the notification.
Any changes made to the template content are instantly reflected in the message preview. The preview updates in real time as edits and adjustments are made.
HTML - The HTML editor allows users to completely change any aspect of the message, which includes fonts, colors, images, etc... The whole look of the message
When it comes to editing SMS or Viber message content, it looks a bit different.
In the Based on field, users can select a system default notification to use as-is or customize it by modifying the content in the Message content field. Below this field, users can choose from commonly used template tags. While only select placeholders are listed, all Task fields are available for use.
Make sure to click Save once you're done creating the template.
The selected trigger event for a template is important. For example, if you choose Failed Task as the trigger, the template can only be used for Failed Task notifications and cannot be reused for other event types.
Logs
This section provides an overview of the message delivery status. Here, users can see which messages were sent successfully, the channel they were sent through, the event that triggered them, and the associated Task, as well as who the recipient was.
The messages can also be searched for and filtered using the following options:
Date range - The date duration for which you want to check notification statuses.
Channel - Email. SMS, Viber, or Push. Users can select and filter multiple channels.
Status - The status of the message. This can be either Sent, Failed, Skipped, or Pending. Multiple statuses can be selected at once.
Contact type - Users can filter based on the recipient. They can choose from Delivery contact, Pickup contact, Depot, Driver, or Custom. Multiple options can be selected at once.
It's also possible to export these logs.
Configuration
This section allows you to set up different service providers if you do not want to use eLogii's default service provider.
Alternative Email Service Providers
For Emails, you can choose between SendGrid or Resend. You must have accounts created with them to use their services. To configure any of these services, simply provide eLogii with the appropriate API key. You can also send a test email to ensure your configuration is working properly.
For alternative email services, please note that additional costs may apply and are outside of eLogii’s control. While eLogii does not charge for using these services, users are fully responsible for managing any invoices and fees directly with the third-party providers.
SMS and Viber Message Service Providers
eLogii allows users to choose between four SMS service providers: Twilio, Plivo, LinkMobility, and Apifon. The setup process may vary between providers, as each requires different credentials, such as codes and access tokens. Users must have an account with their chosen provider and connect it to eLogii to be able to send SMS and Viber notifications.
Please note that additional costs may apply and are outside of eLogii’s control. While eLogii does not charge for using these services, users are fully responsible for managing any invoices and fees directly with the third-party SMS providers.
Users can also use the Sender ID field to replace the phone number with their company name. For example, when a customer receives an SMS about their delivery, the sender will appear as the company name instead of a phone number.
Alphanumeric Sender ID Limitations
This feature isn’t supported in all countries. When sending messages to unsupported regions, the system will automatically fall back to your configured phone number.
This feature is not supported in countries such as the USA, Canada, Australia, China, India, Brazil, South Korea, New Zealand, Argentina, Chile, and Colombia, among others. Recipients in these locations will see your phone number instead.