ShipOpsTCS “Consignee not home”: what it means
HN Attempt failed Also printed as Delivery Attempted; Consignee Not Home · Receiver Not Available
TCS HN Consignee not home means the rider reached the address and nobody was there to take the parcel. It is a failed delivery attempt. TCS will send the parcel out again on its own, without waiting for you. CN Receiver Not Available means the same.
On the tracking page it often reads Delivery Attempted; Consignee Not Home, with no code. ShipOps counts both as an attempt and shows the parcel as attempted.
The next update is normally another Out For Delivery. Protect that visit. A parcel that keeps missing the customer drifts towards a return, and you pay the freight either way.
What to do now
| Your move | A failed visit with the customer absent. TCS will try again; reach the customer so the next visit is answered. |
|---|---|
| The customer | The customer may say they were home and nobody came. Agree a time and a number they will answer for the next visit. If one area keeps producing these, raise it with TCS. |
| Retry or return | TCS takes a retry or return instruction only while the parcel is in its review window. ShipOps raises the parcel when that window opens and files the instruction from the order. |
| Attempts | TCS tries 3 times before it starts a return. |
The reasons TCS gives on a failed visit
| Status Has Been Incorrectly Updated | 99Courier-side |
|---|---|
| Consignee not home | HNCustomer not available |
| Receiver Not Available | CNCustomer not available |
| No Response on mobile | NMPhone problem |
| No Response on phone | NRPhone problem |
| Receivers premises closed | RCCustomer not available |
| Delivery Rescheduled | DR |
| SCHEDULED FOR NEXT DELIVERY CYCLE | NDCourier-side |
| Refused to accept | RDCustomer refused |
| On Hold | OHCourier-side |
| Temporary On Hold at TCS Facility | THCourier-side |
| Bad Address | BAAddress problem |
| BAD ADDRESS | BDAddress problem |
| Wronge Address | WAAddress problem |
| INCOMPLETE ADDRESS | IAAddress problem |
| Unable To Locate Delivery Address | ULAddress problem |
| Address Closed | CAAddress problem |
| Need Further Consignee Information | NCAddress problem |
| Receiver Shifted From Delivery Address | NPAddress problem |
| Consignee Shifted | CSAddress problem |
| Mobile Switched Off | MOPhone problem |
| Wrong Mobile Number | WMPhone problem |
| No Telephone Number | NTPhone problem |
| Wrong Land Phone Number | WPPhone problem |
| Awaiting Correct Number | ANPhone problem |
| HOLD FOR COLLECTION | HFHeld |
| Held for Self Collection | SCHeld |
| Held for Payment | HPHeld |
| STOP DELIVERY | STCourier-side |
| Shipment Stop | SSCourier-side |
| Please Contact TCS | PCCourier-side |
| Contact TCS Local Customer Services | CSCCourier-side |
| Contact TCS Local Customer Services | CSRCourier-side |
| Out of delivery Area | NSAddress problem |
| OUT OF SERVICE AREA | OSAddress problem |
| Short Received | SRCourier-side |
| Shipment Partially Received | PRCourier-side |
| Partial Piece Delivered | POK |
| Partial delivery | PD |
| Shipment Damaged | DMLost or damaged |
| Prohibited Item | PILost or damaged |
| Lost shipment | LSLost or damaged |
| Abandon Shipments | ABLost or damaged |
How ShipOps reads it
Attempt failed A delivery failed, the courier still has it. The parcel goes into the Action Inbox with the courier's reason in plain words. The useful move is to reach the customer before the next attempt; ShipOps puts the call and WhatsApp buttons on the row and counts the attempts made so far.
ShipOps shows every courier's parcels in the same few plain states, so your team learns one set of words instead of one per courier. All TCS statuses →
The same state on other couriers
See every TCS parcel in plain words
Connect your TCS account and ShipOps reads every status for you, raises the parcels that need a decision, and checks TCS's COD payouts against your orders. Free to start, no card.