Awaiting Status
What was released?
A new status called “Awaiting” will be displayed when an appointment is eligible to be booked automatically, but is missing required information.
Why is this important?
Previously, there were booking requests that looked like they were in progress since they showed a status of “Requested”. However, they actually had not yet been sent to the terminal because they were missing some required information.
How do I use it?
If a user sees "Awaiting” status on Load, the missing field should be updated as quickly as possible.
The booking request status of “Awaiting” will apply if it is manually triggered by a user OR the appointment is eligible to be automatically booked (meets the following criteria)
Routed to an automation-enabled Terminal
Matches a Template that is set to “automatically run in the background”
BUT a field that is required by the Terminal or the Template is either missing or incorrect
The status will be visible on the Dispatch Board and the Load Info page along with a tooltip that will list the required field(s)
On the Appointments List page, there is an additional filter for the Awaiting status. Clicking on this filter will quickly show all the booking requests currently requiring additional information in order to be sent to the terminal. Please note that requests in Awaiting status will not show in the List unless the filter is selected OR the container is specifically searched for.
“Deadline Date” Control
What was released?
A Template toggle to control whether or not appointments should be booked if they are after a “Deadline date” (LFD, Per Diem, Cutoff)
Why is this important?
From customer feedback, we have found that some customers want the automation to book the first available appointment regardless of whether it is past LFD (or other deadline date) while others do not. This gives further control over the appointment selection logic.
How do I use it?
This toggle is applicable when the Timing Preference of a Template is set to “First Available Appointment” and controls the scenario of no appointments being available until after the “Deadline Date”.
The “Deadline Date” will depend on the type of appointment
Import Pickups = LFD
Import Returns = Per Diem LFD
Export Returns = Cutoff Date
If the first available appointment is after the Deadline date…
… and you want the system to book the appointments, then turn this toggle ON
… and you do not want the system to book the appointments, then leave this toggle OFF
Recommendation
For Import Pickups - really varies by customer (will see the most variability here)
For Import Returns - ON
For Export Returns - OFF
For Export Pickups - NA (no applicable deadline date)
Set Maximum Capacity by Port and Day
What was released?
Users can set different Appointment Slot Maximums based on the Port and by day of the week.
Why is this important?
Previously, the Maximum settings applied across all days and all Port. However, this did not support the following common scenarios:
A Carrier’s hours of operation and number of Drivers scheduled will often vary depending on the day of the week. For example, in LA/LB, it is common for Carriers to schedule Drivers in the following manner, which results in varying capacities depending on day of the week
Mon-Thurs: 1st & 2nd shift
Fri: 1st shift only
Sat: 1st shift only, and with fewer drivers
For Carriers who work across multiple Ports, it is unrealistic to use the same Driver pool across the different regions. Because of this they may have more capacity in one region compared to another and want to set their maximums based on the number of Drivers per region
How do I use it?
By navigating to Appointment Settings > Maximum Appointment slots, users can see the maximum number of appointments they currently have set.
By clicking on an individual time slot, users can update the maximum number of Pickup and Drop slots they want to allow
These maximums only apply when the system is calculating the acceptable timeslots in an automatically-triggered booking request. The system will allow users to exceed these limits when manually triggering a booking request, booking a timeslot through the “Manual Booking” button, or manually setting the appointment themselves.
*Upon initial launch, all maximum capacity values will default to 20 pickups and 20 returns per timeslot.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article