Lesson 9: Delivery Problems & Status Codes
Know what to do when a delivery cannot be completed normally.
Why This Matters
Incorrect statuses, missing notes, or poor communication create customer complaints, failed deliveries, payment disputes, and dispatch confusion.
If there is a problem at the stop, it must be documented correctly inside MobileTek.
Common Delivery Problems
- Customer unavailable
- Wrong address
- Business closed
- Access gate or entry issue
- Damaged package
- Customer refused delivery
- Barcode will not scan
- Missing package
- Unsafe delivery location
Watch This Example: Delivery Exceptions & Status Workflow
Watch these walkthroughs showing how to handle delivery issues, exceptions, and status updates inside MobileTek.
Focus on:
- How to select the correct delivery status
- How to document delivery problems clearly
- How to add notes and photos correctly
- When dispatch should be contacted
What You MUST Do
- Select the correct status code or exception status.
- Add clear notes explaining what happened.
- Take photos if needed.
- Contact dispatch immediately if the stop cannot be completed.
- Wait for instructions if needed.
Good Notes vs Bad Notes
Bad Note:
Good Note:
Never Do These Things
- Do not mark a stop complete if delivery did not happen
- Do not guess a status code
- Do not leave the stop without documenting the issue
- Do not wait until the end of the route to report problems
- Do not use vague notes
- Do not ignore failed deliveries
ROLO Standard:
Problems must be communicated immediately — not hours later.
Success Check
You should now understand:
- When to use a status code
- How to document delivery problems
- Why notes and photos matter
- When dispatch must be contacted
- How to properly handle failed deliveries
Need Help?
If you are unsure which status to use or how to document the stop correctly, contact dispatch before completing the stop.