Partner integrations: I know they are newer on the scene but an option for Carrier Assure as an integration partner. We really need a way to get FreightGuard reports into PB. I know C411 has historically been close chested on this information and others are now offering FreightGuard-esque reports in their products, but FG has been around a very long time, and we do rely on them over some of the others that newer vendors like Highway that offer these reports.
A way to highlight if a carrier is able to be on high value freight or not. We're currently developing a solution around this but would be nice if there was a checkbox for high value or a rubric to add that would reduce the pool of carriers that are approved for high value that could then be folded into the carrier quals.
Add some gates or options to DQ a carrier based on authority active date (this may be handled with custom quals which we don't have in our version).
VIN verification
A way to detect changes in FMCSA data whether that be through a warning on the carrier master that then flows to the load (if a change is detected on a carrier that is active on a load). Maybe the FMCSA detection changes stem from the integration partner but either way those changes should flow into PB and then be highlighted in the system as a warning or require user intervention to take action on the carrier. (control file that allows each customer to determine how they want to handle alerts i.e. - warn at change or 'no dispatch' at change or some hybrid of those).
A way to DQ carriers that use a certain insurance carrier. I.E. - progressive
A way to warn or highlight carriers that have contacts that have certain initials.
A setting (maybe control file) that sets a carrier to no dispatch after being dormant after a period of time (should be a configurable setting but could be something like no loads moved within the last 24months). We could create a FLX routine for this but would be cool if the system detected that.
Phone# validation - when a phone # is entered in carrier dispatch, validate the phone number as being a cell of a driver vs. a landline or VOIP
If any of this is already in PB web or versions later than 20.1 of PB, feel free to file this in file 13. ;)
Partner integrations: I know they are newer on the scene but an option for Carrier Assure as an integration partner. We really need a way to get FreightGuard reports into PB. I know C411 has historically been close chested on this information and others are now offering FreightGuard-esque reports in their products, but FG has been around a very long time, and we do rely on them over some of the others that newer vendors like Highway that offer these reports.
A way to highlight if a carrier is able to be on high value freight or not. We're currently developing a solution around this but would be nice if there was a checkbox for high value or a rubric to add that would reduce the pool of carriers that are approved for high value that could then be folded into the carrier quals.
Add some gates or options to DQ a carrier based on authority active date (this may be handled with custom quals which we don't have in our version).
VIN verification
A way to detect changes in FMCSA data whether that be through a warning on the carrier master that then flows to the load (if a change is detected on a carrier that is active on a load). Maybe the FMCSA detection changes stem from the integration partner but either way those changes should flow into PB and then be highlighted in the system as a warning or require user intervention to take action on the carrier. (control file that allows each customer to determine how they want to handle alerts i.e. - warn at change or 'no dispatch' at change or some hybrid of those).
A way to DQ carriers that use a certain insurance carrier. I.E. - progressive
A way to warn or highlight carriers that have contacts that have certain initials.
A setting (maybe control file) that sets a carrier to no dispatch after being dormant after a period of time (should be a configurable setting but could be something like no loads moved within the last 24months). We could create a FLX routine for this but would be cool if the system detected that.
Phone# validation - when a phone # is entered in carrier dispatch, validate the phone number as being a cell of a driver vs. a landline or VOIP
If any of this is already in PB web or versions later than 20.1 of PB, feel free to file this in file 13. ;)