Establish Unified Flow for Pick-up & Delivery Failure Reasons

shipsy

Nov 14, 2022

This all-new functionality enables users to unify the flow for both Pickups/Delivery Failure Reasons, make the flow compatible with the reason category, and handle the multiple PODs (Proof of Delivery) for Pickups. Earlier, Pickups and their NPRs (Non-Pickup Reasons) were handled from Internal Dashboard (IDB) configuration.

How to Use This Feature?

All the common Failure Reasons for all tasks available are shown in App Flow Config → Failure Reasons on the new App Flow Config → Config Object → Failed Attempt Proof section.

The Failure Reasons shown in the ‘Failed Attempt Proof’ section can be configured as per multiple proof requirements. This section also acts as a common POA (Proof of Arrival) reason master for configuring image/video count.

Caption: App Flow Config → Config Object → Failed Attempt Proof
Caption: Edit Reason dialog box
Caption: TMS app view for POAs

Join hands with a future-ready logistics technology partner