22.7: There’s an Alert for That

Parcel overage notification

Status event alerts are an important feature that can be configured to trigger email and SMS notifications automatically during the order fulfillment process. CXT Software has been developing dozens of useful alert types that not only improve client communications, but also internal operations.

 

Want to let your client know their order is confirmed? There’s an alert for that.

 

Need to update a client about a change in the order rate? There is an alert for that too.

 

From “Picked Up” to “Out for Delivery,” notifications can be a powerful tool for your business throughout the shipment lifecycle.

 

Two new status event alerts introduced with the 22.7 release include “Order – Parcel Overage Scan” and “Route Stop – Parcel Overage Scan.” This alert will send notifications when an overage scan occurs informing the client of the excess parcel.

 

Click here for a full list of status event alerts.

There's Help for That

If you need help with the configuration of this product feature, give us a call or contact your Client Success Specialist.

 

Experiencing issues with the release or your product suite? Let our Support Team know and we’ll help get you back on track.

Release Updates​

What's New 📰

  • Created the ability for users to clone contracts as well as their associated stops in an effort to reduce manual duplication efforts.
  • Added two new Customer Record Status Event Alert options called “Order – Parcel Overage Scan” and “Route Stop – Parcel Overage Scan” that will trigger email/SMS notifications when overage scans occur on orders/route stops.
  • Added a “Forgot Password” option for the Cloud Client and Cloud Portal to allow users to reset their own passwords as needed when experiencing login difficulties.
  • Added a new option on the Cloud Client login screen to set a registry key if the user is on Windows 11 22H2 and experiences issues connecting to the application.

What's Improved 📈​

  • Updated the logic in the Driver App to allow sequencing to match the dispatch board when using the ‘Group by Tracking ID’ option in Mobile Option Sets.
  • Adjusted how we handle creating orders from the Client Portal‘s Recent Orders/Templates so that internet users no longer receive an error when using an address that is no longer saved in their address book.
  • Updated Beans.ai Assisted Dispatch functionality to use a driver’s vehicle capacity with the calculated dimensional volume on an order to better determine whether a vehicle is within its capacity limits.
  • Added logic so API users can include Address Point IDs for all orders, so they can be used for the Force Location Scan functionality.
  • Improved the search capabilities for the Client Parcel Portal so that different variations of both US and CAD postal codes can be searched.
  • Updated the internet user permission for ‘Allow Address Entry’ so that it controls whether Google Places, Drop Pin, and Manual Entry options are available in the Client Portal.

What's Fixed 🛠​

  • Fixed an issue when navigating away from the Place Order page in the Client Portal showed a blank page due to infinite scroll.
  • Fixed an issue that was preventing users from adjusting the driver pay if a route was not assigned to a driver.
  • Fixed an issue with the Credit Card Transaction report where not all transactions were being displayed properly when an exact date range was specified.
  • Fixed an issue that could generate an error if a stop contained a contract stop ID that no longer exists.
  • Fixed issue with Parcel Overage defaults that could sometimes display incorrect information.

Works in Progress 🏭

  • Entering an address in the Client Portal that does not validate causes old lat/lon values from previously validated addresses to be used for distance calculation and could cause incorrect distances to be placed on orders.
  • Subscription-based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field, as it is not supported.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign updated Lat/Lon values.
  • Internet User columns do not always sort as expected in the Operations App.
    Workaround: Click on any cell besides the header or the column that is selected, then click on the column again to sort in the other order.
  • An error occurs in the Operations App when a user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Operations Monitor – Help – View Manual results in a run-time error ’13’ type mismatch.

What's Coming 🎁​

  • QuickBooks Online integration improvements
  • Assisted Dispatch enhancements

Let's meet! Request a
guided demo.

Let's meet! Request a
guided demo.

Whatcha looking for?