Alerts in Freightools

Alerts in Freightools

Updated 9/15/2026

Alerts in Freightools

Alerts are automated triggers designed to notify relevant parties when specific operational, financial, or workflow events occur.

They ensure proactive communication and reduce the risk of missed updates.


1️⃣ Types of Alerts

There is a wide catalogue of alert types. They are generally based on:

🔹 SO Stages (Date-Driven)

Triggered when a shipment reaches a specific stage.

Examples:

  • CS in Execution – Departed
  • Arrival stage updates
  • Delivery stage updates

These alerts are typically driven by SO dates and stage progression.


🔹 Process Steps

Triggered when a specific process step is completed.

Examples:

  • P.Steps – Automatic PDF sent by email
  • Invoice issuance (Automatic send invoice PDF via email)

These alerts are linked to a defined Process Step and its Execution Tool.


🔹 Status / Entity / Change-Based Alerts

Triggered by:

  • Status changes
  • Entity creation
  • Data updates
  • System changes

These alerts monitor operational activity beyond shipment stages.


2️⃣ Where to Manage Alerts

Alert configuration is available under:

Business Process → Alerts

To create a new alert:

  1. Click New Alert.

3️⃣ Core Alert Configuration Fields

🔹 Alert Time

Select the alert trigger timing from the dropdown list.

This determines when the alert should be activated.


🔹 Party Entity (Recipient)

Choose who will receive the alert.

Options include:

  • Customer
  • Agent
  • Internal user
  • Other defined entities

You may also:

  • Add a CC party
  • Select Specific Emails (by checking the checkbox) to enter a defined email address manually

🔹 Service Mix & Service Trade

If the alert should apply only to certain operational flows:

  • Limit it to specific Service Mixes
  • Limit it to specific Service Trades

If left unrestricted, the alert applies broadly.


4️⃣ Additional Configuration Based on Alert Type

Depending on the alert logic, additional fields are required.


Alerts Based on Stages (Shipment Dates)

When configuring stage-based alerts:

  • Define the Email Sender
  • Select the Email Template to be sent

These alerts are typically triggered by:

  • Departure
  • Arrival
  • Delivery
  • Schedule changes

Alerts Based on Process Steps

For step-based alerts, configuration must include:

  • Step Name
  • Execution Tool

This ensures the alert is triggered only when that specific step (and its execution action) is completed.


5️⃣ Email vs Notification Alerts

Alerts can be configured as:

🔹 Email Alerts

  • Email checkbox must be checked.
  • Requires email template selection.

🔹 System Notifications

  • Notification checkbox must be checked.
  • Only a notification text is required.
  • The notification text is based on Standard Text.

Notifications appear within the system rather than being sent externally.


6️⃣ Practical Logic of Alerts

Alerts can:

  • Inform customers automatically when cargo departs
  • Notify finance when invoice is issued
  • Trigger document sending without manual intervention
  • Alert operations of schedule changes

Because alerts can be tied to stages, process steps, statuses, or system events, they create a fully automated communication layer.


Structural Overview

Trigger Event

Alert Configuration (Time + Recipient + Conditions)

Delivery Method (Email or Notification)

Template / Standard Text Execution

Proper configuration ensures accurate and controlled automation.

Still stuck?

Send us the screen you are on and what you expected to happen, and a person will pick it up.

Contact support