Fix status when client's returns were already sent back and have registered successfully
Inbound
We click this link to verify a client's returns status - see if they're already registered or not (yet).
True or False: We can completely rely on Spectre to verify if the Fix is indeed lost on its way back to us.
False.
When we update the Fix status to "Lost Inbound," we also have to update the internal note that automates on the respective Fix. What do we add?
Reason why we updated the Fix status and the ZD ticket link.
Fix status when returns have been sent back, but client still got charged for them as they don't appear to be registered.
Truant
True or false. We only check a client's returns status when the Fix is still on "Delivered," but the client said she's being asked to pay for them.
True
What macro do we use to relay the confirmation of the Fix being "Lost Inbound" to the client?
Fix Scheduling or Arrival > Lost Inbound
True. Yes, we do.
A Fix status when client's returns were already sent back but haven't registered yet, setting up the Fix to possibly trigger truancy.
Delivered
Update Fix status to "Lost Inbound"
False. Truancy can only be stopped when a payment for the unreceived returns has already been made or when the Fix status gets updated or changed.
What status do we update a Fix which returns have registered on the carrier's end, but not in KingMob?
Inbound
True or False. We have to allow 5 days of not being registered from the date the returns were sent back up to the day we receive the concern before considering it "lost inbound."
False.
State the reason why we should change a Fix to a different status when its tracking info has already registered on the carrier's end, but hasn't updated on KingMob.
So it wouldn't trigger unnecessary and incorrect charge/s.