Fleet Profiles for Truck Dispatch Preferences

Create Fleet Profile for trucking dispatchers and equipment providers. For truck dispatchers and equipment providers, a Fleet Profile tab will appear in the settings view. Admin user types are able to define what pieces of information are required to be provided by service centers in events. These options include:

REACH 24
  • PO#
  • License Plate/State
  • DOT#
  • Return Used Tire(s)
  • Odometer Reading
  • Hubometer Reading
  • Vehicle Model
  • Cross Border
  • Fleet Authorization
  • Free Form field for additional details

When a service center or technician marks an event as Complete, REACH will make sure all elements the truck dispatch has added in its Fleet Profile are present. If information is missing, the service center will be notified to enter as such and will otherwise not be permitted to close the event.

Choose preferred payment method. Truck dispatch users of the Admin and User types will have the option to choose their preferred payment method when creating or editing their fleet profiles. If their preferred payment method is not shown, these users will also have the option to add a custom option by choosing "Other."

Display additional truck dispatch details in the event view screen. Similar to the hyperlink within the event that allows truck dispatchers to review service center contact information, a hyperlink will be added to the truck dispatch name to display the following information:

  • Preferred payment method
  • Fleet Profile
  • Instructions included in the Fleet Profile

This information will only be available to those users designated as Admins.

REACH 24

Include total count of service center classifications in Find Service Center results. In addition to tabs sorting service center types within the results, the tabs will also display the number of service centers within that classification. The ability to filter results by associated tags will also be present.

Move custom fields to a tab of its own. To accomodate the growing use of custom fields, the service event view screen will have an additional tab to separate the default and custom items.

REACH+24

Based on the preferences set by Admins in the portal settings, custom fields will either be editable by other parties or read-only. Users working within their own portals will be able to see all fields within events with visual cues noting those that are read-only.

List existing service centers in the Out of Network Service Center form. When a truck dispatcher or a call center creates an Out-Of-Network service center that has already been created in REACH system-wide, a dropdown menu will appear with that option. When selected, the fields will populate with information previously entered.

Major Changes in Find Service Center Results, Custom Fields, and More

REACH 24
  • Sort Find Service Center results. When dispatchers click to find vendors within the desired radius, results can now be sorted by agreement type and by those of which are able to be assigned events ("Under Radius").
  • View existing out-of-network vendors. When dispatchers enter information for an out-of-network vendor, a list of existing options will appear and populate the information fields to prevent duplicate vendor creation.
  • Initiate and send invoices to other companies on REACH. Add attachments, create custom email templates, and generate a public URL to send to companies not on REACH.
  • Make custom fields viewable by other companies on REACH. Previously, custom fields were limited to be viewed only by the portal by which they were created; now, Admins have the ability to switch customer fields to be public. The tab to do so is found in the portal control panel.
  • Add a fleet or equipment provider company on the fly. Vendors and call centers often receive requests for service from fleets that are not using REACH. This feature provides a way to quickly add a fleet with minimal information including the fleet's DOT number and SCAC code; if these details already exist in the system, matching options will appear from a dropdown list to avoid duplicate fleet entries.