Safe Reach Confirmation

Description

Employees traveling within a designated time window will receive a safe reach notification upon reaching home.

We have a dedicated dashboard that allows monitoring of the status of employees who have received safe reach notifications.

The system enables tracking of safe reach confirmations, facilitating manual follow-up for employees who fail to confirm or whose confirmation fails.

Dependency

Employees in the ETS should be registered with the mobile number.

Shift of the employees should fall under the set time window.

Configurations

Console property: 

We have to enable the Email from the console through SE team, To get Safe reach emails.

ETS side configuration : MISadmin => Manage properties =>  Engineering => IVR_DROP_VERIFICATION_FAILED_EMAIL_ENABLED - This property will allow the email to trigger in case if any employee failed to respond the IVR call and the safe reach status is failed.
Email will be triggered the next day at 8:00 AM.

IVR failed entries are triggered the next day at 8:00 AM. Manual success and manual failed entries will trigger email immediately after the status is changed.

Master switch to enable safe reach confirmation.

Below options allow us to enable mobile app notification and IVR calls for safe reach confirmation.

Below configuration will allow us to select Gender, Trip type and Time at which the Notification has to be triggered.

Shift time has to fall under the window.

Safe reach entry of the verification will be marked duplicate if there are any sign in in the last 60 min and in next 60 min.

If the below option is enabled then the safe reach notification will be triggered only after the actual sign off is received.

If the above option is disabled, System will consider the buffer time from the below config.
Mobile app notification will be triggered after planned pick up time + Buffer time set below for planned and  Adhoc trip if actual pick up time is not received.
If actual pick up time is received before the planned pick up time then the Mobile app notification will be triggered after Actual pick up time + Buffer time. 

Example : Planned pick up time is 18:00 and the buffer time is 10 Min, Then the Mobile app notification will be triggered to employee at 18:10 if actual pickup is not received on the server till 18:00, If actual pick up is received on the serve before 18:00 that is at 17:55 then the notification will be triggered at 18:05 that is 10 min after the actual pickup time.

If “Start IVR At Sign Off” property is disabled System will consider the buffer time from the below config to trigger safe reach IVR call. 

Safe reach IVR call will be triggered after planned drop time + Buffer time set below for planned and  Adhoc trip if actual drop time is not received.
If actual drop time is received before the planned drop time + Buffer time then the safe reach IVR call will be triggered after Actual drop time + time set in this “Time Difference Between Mobile App Notification And First IVR Call Time” configuration. 

Denotes at what time difference between each notification.

If the actual drop off time is not received for ad hoc trip, the safe reach verification would not take place if the sign off is not received on the server until buffer time mentioned.

If the actual sign in/sign off is not received on the server until the above configured time, there will be no drop verification

 If the employee press IN CAB when IVR call is triggered, the next IVR is delayed by above configured time.

Email Will be sent for IVR failed cases (Employee and reporting manager,team manager will get email along with mentioned email ID)

Email Will be sent for manual Success cases

Manual success is being done by monitoring specialist who manually calls the employee to confirms female employee safe reach when mobile app notification and IVR are not answered.

Common Issues and Cause

1. Call not triggered to Employee 

Goto => SRC dashboard 

Search for the employee with employee Id => select BUID => date of issue reported

No answer - Employee not responded

Failed - Network issue or operator issue

Busy - Employe on another call or blocked the span calls