Safe Reach Workflow

Safe Reach Workflow Explanation

The provided flowchart explains the Safe Reach Workflow that includes two scenarios: the Actual Sign-off Workflow and the Planned Sign-in/Sign-off Workflow. The workflow ensures the verification of trip completion and passenger safety, using a combination of app notifications, IVR calls, and retry logic. Below is the detailed explanation:

1. Actual Sign-off Workflow

This workflow starts when a Tripsheet is Generated and involves the verification of trip completion through a combination of notifications and IVR calls.

Key Steps:

• Sign-off Received After Verification (Retry Logic): If the sign-off is successfully received after verification, the process ends. If not, it proceeds to further steps.

• App Notification: An app notification is sent to the designated individual. A buffer time of 2–5 minutes is maintained between the notification and the next step to ensure timely acknowledgment.

• 3 IVR Calls: If the app notification is not responded to, the system triggers three IVR calls to establish contact.

• Verification:

  • If the verification is successful after the IVR calls, the workflow ends.
  • If no response is received, the trip is marked as Manual Success or Failed, depending on further manual intervention or lack of verification.

2. Planned Sign-in/Sign-off Workflow

This is a preemptive workflow designed for planned trips, combining mobile app interactions with IVR-based fallback mechanisms to ensure safety.

Key Steps:

• Planned Sign-in and Mobile App Buffer Time:
  At the planned sign-in time, an app notification is sent, allowing users a buffer time for response.

• App Notification:
  The app notification initiates the verification process.

• Planned Drop Time + IVR Call Buffer:
  If there is no response to the app notification, IVR calls are triggered during the planned drop time, with an additional buffer for handling delays.

• 3 IVR Calls:
  If the planned verification via app notification fails, three IVR calls are triggered as a fallback.

• Outcome:

  • Verification Success: If a response is received at any stage, the trip is marked as successfully verified.
  • Failure: If there is no response after all attempts, the trip is marked as Failed, and additional steps may be initiated to ensure manual success if feasible.