Open Nexus
Booking Notes Module

Notifications

In-portal and email notifications for booking notes.

Notifications

Booking Notes raises notifications when a booking note needs attention or its status changes. They arrive in two places: inside the portal, and by email.

Notifications in the portal

A notification is raised whenever a booking note changes status. They appear in the Notifications module in the left sidebar, and an indicator in the top navigation shows when there is something new.

Each notification is tied to a specific booking note, and selecting it opens that booking note directly. Notifications are marked as read once viewed.

What triggers one

EventWho it matters to
A booking note moves to Pending ReviewThe Freight Forwarder — something needs reviewing
A booking note is ApprovedThe Shipper — the booking is confirmed
A booking note is RejectedThe Shipper — the booking needs redoing

Coming soon — notifications for Changes Requested, once that outcome is available.

Email notifications

Emails are sent for the events most likely to occur while nobody is in the portal:

EventSent to
A booking note is created from an email intakeThe relevant users in the receiving organization
A booking note is approvedThe users associated with the booking note
A booking note is rejectedThe users associated with the booking note

The email for an email-created booking note is the one that keeps the intake channel workable. It signals that something has arrived without anyone needing to watch the Requests list.

What the email contains

Each notification email identifies the booking note and its new status, and includes the details needed to recognize it without opening the portal:

  • Booking note ID and reference
  • Shipper and Consignee
  • Loading Port and Destination Port
  • The new status, with a short explanation of what it means
  • A button linking straight to the booking note

Getting the most from them

As a Freight Forwarder, notifications signal when a booking note arrives, but the Pending Review counter on the Overview page is the more reliable measure of the queue. Notifications are per event; the counter is the current state. See The Overview Page.

As a Shipper, notifications are how a decision is communicated. Because Approved and Rejected are both final, a rejection notification is the point at which to act — the booking note cannot be reopened, so the next step is a corrected new booking note. The fastest route is to duplicate the rejected one. See Using the Requests List.

If nothing is arriving

  • Check the Notifications module directly. In-portal notifications are raised independently of email.
  • Check junk and spam folders for the email notifications.
  • Confirm with an administrator that the account is associated with the relevant booking notes.
Copyright © 2026