ShipOpsShipnoc “UNABLE TO CONTACT”: what it means
Attempt failed
Shipnoc UNABLE TO CONTACT means the rider tried to reach the customer and could not, so the delivery did not happen. It is a failed visit, and the reason points at the phone number more than the address.
It is one of the rarer reasons on Shipnoc.
Before anything else, check the number on the order for a missing digit or a landline. A wrong number fails every visit after this one too.
What to do now
| Your move | The rider could not reach the customer by phone. Check the number on the order. |
|---|---|
| The customer | If the customer then calls you asking about the parcel, ask for a second number the rider can use. |
| Retry or return | Shipnoc does not take a retry or return instruction from outside its own portal, so the answer goes in by hand; ShipOps still shows the parcel with its reason and links you there. |
The reasons Shipnoc gives on a failed visit
| Non-service area | NSAAddress problem |
|---|---|
| Refused to accept | REFCustomer refused |
| Held for customer pickup | HSC |
| Consignee not available | CNACustomer not available |
| Consignee out of city | OOCCustomer not available |
| Order cancelled | CAN |
| Address issue | ADRAddress problem |
| Phone not responding | NRPPhone problem |
| Needs review | OTHER |
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 Shipnoc statuses →
The same state on other couriers
See every Shipnoc parcel in plain words
Connect your Shipnoc account and ShipOps reads every status for you, raises the parcels that need a decision, and checks Shipnoc's COD payouts against your orders. Free to start, no card.