Track delivery progress on the timeline

While the status badge shows where a delivery stands right now, the Delivery Activity timeline shows how it got there — a full, chronological record of everything that's happened. You'll find it on the full details page, and in the Activities tab of the quick-look drawer — same timeline, either way.

What's on the timeline

Each entry is a dot on a running feed, with a timestamp. Failure events stand out visually so problems are easy to spot while scanning. Entries cover things like:

• Status changes as the delivery moves through its lifecycle.
• Pickup and dropoff milestones.
• Provider or courier reassignments.
• Driver-offer events — offered, accepted, or rejected.
• Driver phone calls — logged automatically, with a phone icon and a label for who was dialed: the customer, the pickup, or support.
• Masked phone calls — where the driver and customer reach each other through a masked number that hides their real phone numbers, each call adds its own row when it ends. The row shows how the call went and who called whom — for example Completed call: Driver to customer or Unanswered call: Customer to driver — followed by how long the call lasted when it connected.
• Proof-of-delivery captured.
• Notifications sent — expand one to see the message itself.

Note

Masked calling isn't set up for every organization, so you may never see masked-call rows. Availability varies by organization — reach out to Nash if you'd like it. Where it is set up, a call can show as Completed call, Unanswered call, Unanswered call (busy), Failed call, or Cancelled call, in one of three directions: Driver to customer, Customer to driver, or Customer to support. A call that reached voicemail counts as completed.

When a delivery involves more than one provider or task, an event's provider chip filters the feed down to just that task, so you can follow one thread without the rest of the noise.

Narrow or add to the feed

Filter tabs above the timeline let you narrow the feed to specific kinds of events instead of scrolling through everything. If something happened that isn't captured automatically, use Add Event to log a custom entry — handy for noting a manual step so it's part of the delivery's record.