Docs

Pickup Notifications Explained

Every trigger on the Pickup Notifications tab, and the one trigger whose checkbox does not actually control anything.

Published

The Pickup Notifications tab is one of five tabs on the Notifications page in the dispatch software. Reach it at Notifications → Pickup Notifications, or /app/notifications?v=pickup. It controls the SMS and email messages sent to a customer when the ticket they are on is set to the Pickup transaction type.

Pickup vs Delivery is a setting on the ticket, not two different audiences

Every delivery ticket carries a Destination Transaction Type, chosen on the Add New Ticket form: Delivery ("Dropoff product to customer's delivery address") or Pickup ("Pick up product from customer's delivery address"). The person notified is the same customer at the same address either way — what changes is which tab's switches and templates apply. A ticket marked Delivery is governed entirely by the Delivery Notifications tab; a ticket marked Pickup is governed by this one. No ticket draws from both tabs.

The triggers

Toggle SMS and Email independently for each row, then press EDIT to write your own wording using the merge tags. There is no Mobile Push column on this tab — Pickup Notifications are customer facing, and your customer does not have the Zippykind driver app.

  • Ticket Created — the ticket was just created, from the Add New Ticket form, the API, or the bulk uploader.
  • Request Received — a driver accepted the ticket (or, on an auto-accept account, it was accepted for them).
  • Driver Started — the driver marked that they are headed to this stop.
  • Driver Arrived — the driver marked that they have arrived at the pickup address.
  • Successful — the ticket was completed successfully.
  • Failed — the driver marked the ticket failed.
  • Notes — read the warning below before you rely on this one.
  • Update Notes — the driver edited a note already on the ticket.
  • Signature — a signature was captured for the ticket.
  • Photo — a photo was captured for the ticket.
  • Contactless Signature — a contactless signature request was sent. See Contactless Signature Disclaimer.

The Notes trigger on this tab does not do anything

This is worth being precise about, because it is easy to turn it on, write a template, and have nothing ever go out. When a driver adds the first note to a ticket, the code deciding whether to text or email the customer about it checks the Delivery Notifications → Notes switch on every ticket, Pickup type or Delivery type alike. The Notes row and template on this Pickup tab are never read by anything that sends a message. If you want a customer to be notified when a driver adds a first note to a Pickup-type ticket, turn it on under Delivery Notifications instead — that one switch covers both transaction types for this particular trigger. This reads as an unfinished branch in the code, not a documented product decision.

The Update Notes row, directly below it, is different: editing an existing note on a Pickup-type ticket does correctly read this tab's Update Notes switch and template. There is a separate, narrower gap on that one too — see the merge tag reference for exactly what it is before you write the template.

Saving

Press Save Notification Triggers at the bottom of the tab. It saves this tab only.