Latest Features on 6.2.5 and 6.2.6

Handle alphanumeric vehicle reg no. cases on driver app : 


Driver app will now accept alphanumeric characters for starting duty/ marking no show etc. in single driver cases - useful for international customers

How does it work:

On enabling the property - the driver app would allow input in alphanumeric mode for single driver use cases.

Flow:

If ETS prop is enabled → Single driver case → wherever user is currently entering verification code should show up an alpha numeric keypad like we show for multi driver cases → user will input vehicle reg no. → confirm → respective workflow should be completed.

Properties to be enabled: Reach out to SE Team/Driver Exp
Version Needed : 6.2.5 and above

2) Nudge users to choose language upon driver onboarding : 

Problem:

Currently, drivers can’t onboard themselves without external help if they can’t understand the default language - English. 

Solution:

• As soon as the app is opened after installation for the first time, the first step would be to select a preferred language and then continue on to the DL entering screen.

Flow:

BYOD → Opening for the first time → Show language change screen → Enter DL (entry point on top right to change language)

BYOD → Switch offices page (entry point on top right to change language)

In-cab → Opening for the first time → Switch offices page (entry point on top right to change language)

Both BYOD and IN-cab → “Switch language“ under hamburger menu → should also display the same page

Clarifying the Difference Between End Trip and End Duty!

Problem:

In a lot of cases, drivers would click on end trip in place of end duty and get confused on why the duty is not ending. This is to clear the confusion between the two buttons and provide clarity for the actions.
As both the popups for “End duty“ and “End trip“ look very similar with minor message difference, for incomplete trips the drivers click on “End Trip“ and input the verification code for “End duty“ hoping this should end the trip / duty. But, here the ideal behaviour is to call the THD and get the cancel code for the trip to cancel the trip.

To reduce confusion, the "End Trip" user interfaces (UI) should be clearly differentiated from "End Duty".

Restricting Auto - Sign Off of Marshalls within office radius during trip start - Login Trip

Problem:

In scenarios where marshals sign in to the driver device within the office geofence and initiate the trip, the auto-sign-off feature, when enabled for the site, prematurely ends the trip by automatically signing off the marshal. This results in operational inefficiencies:

Ad-hoc Trip Creation: To compensate for the prematurely ended trip, additional ad-hoc trips are created, leading to unplanned resource allocation and increased administrative overhead.

Solution:

• Ensure that login trips are not prematurely completed due to auto-sign-off of marshals by implementing logic that restricts auto-sign-off to occur only after an employee-level event.

• Reduce operational inefficiencies caused by premature trip completions.

• Eliminate the need for ad-hoc trip creation.