New! Transflo Mobile+ 6.7 Embedded Handset Release Notes

The Mobile+ app has been configured to support certain new large and mid-size fleet customers with integrated mobile hardware running Android OS. Geotab log-in credentials are used for authentication to Mobile+ and Geotab features.

When drivers are prompted to log in, instruct them to enter their user ID and password and then tap Login.

Example: This example shows the new Loads 2.0 user workflow and user login features in Transflo Mobile+ running on a mobile device handset engineered for freight shipping and delivery personnel.

As a driver, your user ID should be the same for your registered Transflo Mobile+ and Geotab HOS/ELD accounts. Use the exact same user ID for those two (2) separate driver accounts. Later, when you tap HOS Login, an easy single-sign on (SSO) process automatically authorizes you and logs you in based on the email User ID you already entered when you logged in.

As a driver equipped with a hardware handset running the special new embedded edition of Mobile+ R6.7, your embedded Transflo Mobile+ app experience includes the following key characteristics:

• You do not need to download or install anything; your admin will set up the app on each handset. (As a fleet admin, work with Transflo to side-load the appropriate APK, SDK, and other configuration files.)

• Your initial BETA app is based on the features in Mobile+ Release 6.6 and will transition to a special edition of Mobile+ Release 6.7 exclusively for your fleet.

• Your app runs on the Android 11 operating system (iOS is not supported).

• Your app runs only in dark mode to conserve battery power and reduce eye fatigue.

• When you log in to the Transflo Mobile+ app, you must use your existing Geotab username and password. Your credentials are shared across the Mobile+ app and the Geotab ELD functionality so that your experience with loads, scans, HOS, and other features is seamless.

• Your app supports the built-in hardware keys on your special company-issued handset. In addition to tapping directly on your device screen like a smartphone or tablet user would, you can also press the appropriate hardware keys on your handset.

This KB article describes new features under development in the 2025-2026 pre-release BETA edition of Transflo Loads Workflow 2.0. All KB articles are subject to change with or without notice and will be updated to align with future product development. When calling Support, be sure to identify your company fleet and type of handheld device.

By popular demand, the new embedded release runs only in dark mode. It does not offer support for switching the user interface of the mobile app between light and dark mode. For a consistent user experience, the Transflo Mobile+ app will ignore the current color mode in the Android mobile operating system (OS) settings and will always run in dark mode.

In low-light environments, especially during overnight hours, drivers have requested a way to invert the default color scheme of the app which is often too bright at night. Because screen brightness is immediately reduced, the new dark mode feature can significantly reduce eye fatigue and extend battery life.

Examples: iOS and Android Color Mode or Color Theme Settings can be used for other apps and for the OS but the Mobile+ app will always run only in dark mode.

(Dark Mode support is available only for Android users running the special embedded edition of Mobile+ on freight handsets.)

Examples: Transflo Mobile+ app in Light Mode (left) and Dark Mode (right)

(Examples only; your handset might show somewhat similar results.)

This KB article describes new features under development in the 2025-2026 pre-release BETA edition of Transflo Loads Workflow 2.0. All KB articles are subject to change with or without notice and will be updated to align with future product development. When calling Support, be sure to identify your company fleet and type of handheld device.

Note: This feature is available exclusively in the special embedded edition of release 6.7 and is limited to specific fleet customers and specific handsets; however, it is expected to become available to a wider audience of fleet drivers in a future release (for example, R7.2 in May 2026).

 

 

This new feature enables multiple dispatchers to communicate with drivers working in different sub-fleets, regional areas, or business units within a primary fleet. For example, chat messaging can be directed at the inbox for the Western region of Fleet 1, the Southern inbox for Fleet 1, or exclusively for workers on the Maintenance team of Fleet 2.

New Focused Inbox Chat Messaging features offer an extended set of benefits:

• Multiple business units or dispatch areas get full visibility into past, present, and ongoing future communications from dispatchers and drivers without access limitations or lost historical comments.

• Carrier fleets can set up dispatch groups for company-defined chat inboxes in Transflo Command Center or an API-enabled TMS.

• Dispatchers logging into Command Center and selecting an inbox will be able to send a message to a driver that will be sent and received as a continuous chat conversation inside the inbox.

• Dispatchers enjoy access to all ongoing dispatch communications for the current focused in-box.

• Dispatchers can target specific individuals, teams, or dispatch locations when sending messages and drivers or other team members can respond in the Mobile+ app.

• Enhances communication visibility, improves message clarity, reduces errors, and saves time.

Note: This feature is available exclusively in the special embedded edition of release 6.7 and is limited to specific fleet customers and specific handsets; however, it is expected to become available to a wider audience of fleet drivers in a future release (for example, R7.2 in May 2026).

 

 

This release improves the team driving experience by supporting more consistent and persistent functionality when switching drivers. In this release, when the driver in the driver's seat is selected in HOS, that driver's ID and similar ELD user data is carried into the Mobile+ app and automatically inserted where it might appear in the app such as an on-screen form.

Example: In this example, Driver 1 is the current driver selected in Transflo HOS. Later, when an equipment form is opened in the Transflo Mobile+ app, the ID for the currently active team driver is automatically inserted into the Driver field. An HOS change to Driver 2 would auto-insert the ID for that driver in similar forms in the Mobile+ app.

In past feedback for earlier releases, fleet managers advised us that in some team driving scenarios, their drivers could possibly be over-compensated or under-compensated because certain dynamic load and driver data in the Mobile+ app did not always dynamically update and persist to reflect the active team driver.

To improve the team driving experience, this release provides more comprehensive enhanced support for drivers operating as a team:

• Drivers can expect enhanced full support for driver switching not only in HOS but also throughout a greater number of Mobile+ features such as online forms.

• Fleet managers and load workflow designers can design driver forms that reliably auto-fill the active driver ID from Geotab.

• These enhancements help limit driver mistakes and improve the accuracy of form data, reports, and payment processing operations.

Note: This feature is available exclusively in the special embedded edition of release 6.7 and is limited to specific fleet customers and specific handsets; however, it is expected to become available to a wider audience of fleet drivers in a future release (for example, R7.2 in May 2026).

 

 

The app has been updated to support a more consistent user experience when sorting and selecting loads on different screens. When a driver is prompted to select a load, standard load sorting functionality helps the driver make a more informed decision.

More information about this future feature will appear here in a future update as information becomes available.

Traditional radial geofences where a preset radius of say 300 yards was used to define a circle at or near a driver destination are now considered somewhat lacking in precision. Older radial geofences were often inaccurate and left too large a margin of error, especially when the point-of-interest (POI) was particularly large.

This release allows ELD fleet customers to use new and more precise Geotab polygon zones in new driver workflows. Key benefits include:

• More accurate automated arrivals and departures

• More precise nested geofences for specific areas within a yard or site

• Geofence areas can now be configured with multiple points, allowing for complex shapes.

To learn more, see New! Define Geofence Polygon Borders Around a Location.

Note: This feature is available exclusively in the special embedded edition of release 6.7 and is limited to specific fleet customers and specific handsets; however, it is expected to become available to a wider audience of fleet drivers in a future release (for example, R7.2 in May 2026).

 

 

Starting with Release 6.7, the Mobile+ app will introduce and continue to support both Loads 1.0 and Loads 2.0 implementations. Although the app supports both implementations, customers can only remain on one and the legacy Loads 1.0 features will be deprecated through 2026 as customers migrate to Loads 2.0 (new user workflows). 

This special embedded edition for handsets supports only the new Loads 2.0 features. Drivers can manage all the required and optional steps to deliver their loads, submit load documents, and complete any other tasks you assign.

To learn more about the new user workflows (Load Workflow 2.0) features for drivers, fleet administrators, and the developer SDK and API options, see the New! Loads 2.0 KB.

In addition to the GPS-aware location tracking of the mobile device running the Mobile+ app, load workflows can also get the current location of the physical ELD in the vehicle, truck, trailer, or other asset.

Key benefits include:

• More accurate tracking of trucks entering and leaving yards

• Adds a configurable option for fleet workflow designers to compare the reported device location with the detected ELD location prior to triggering a geofence to validate a device and truck are truly in the same location.

Note: This feature is available exclusively in the special embedded edition of release 6.7 and is limited to specific fleet customers and specific handsets; however, it is expected to become available to a wider audience of fleet drivers in a future release (for example, R7.2 in May 2026).