ShipOpsTCS “No Response on mobile”: what it means
NM Attempt failed Also printed as No Response on phone
TCS NM No Response on mobile means the rider called the customer and nobody picked up, so the parcel was not handed over. NR No Response on phone means the same. It is a failed attempt, and TCS will try again.
The number works; the customer just did not answer. That is different from Mobile Switched Off and Wrong Mobile Number, where the number is the problem and TCS waits for you. With NM, TCS keeps the parcel on its own schedule.
Riders call from numbers customers do not know. A WhatsApp from your store, naming TCS and the amount, often gets read where the call did not. ShipOps groups NM with the phone problems so your team knows to message rather than call.
What to do now
| Your move | The rider could not reach the customer. WhatsApp usually works where a call did not. |
|---|---|
| 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.