The Driver Notifications tab controls the messages sent to a driver when something happens to a ticket assigned to them: a mobile push into the Zippykind driver app, an SMS to the driver's phone, and an email. Reach it at Notifications → Driver Notifications, or /app/notifications?v=driver. Like Pickup and Delivery Notifications, it is account-wide — one set of switches for every driver, not one per driver.
The triggers
- Assign Ticket — a ticket was assigned to the driver, by a dispatcher or by auto-assignment. Default Mobile Push text if you leave the template blank: "A new ticket has been assigned to you, Ticket ID: [TicketID]. Delivery Date and Time is [DeliveryDateTime] to [CustomerName] at [CustomerAddress]."
- Update Ticket — a ticket already assigned to the driver was changed. Default text: "Ticket ID: [TicketID] status has been updated."
- Deleted Ticket — a ticket assigned to the driver was cancelled. The row is labelled Deleted Ticket in the table; the option prefix behind it is
CANCEL_TICKET. Default text: "Ticket ID: [TicketID] has been cancelled."
Those three defaults are used automatically for Mobile Push whenever you leave that trigger's push template blank. Write your own with the EDIT button and your wording replaces it; SMS and Email have no built-in default and send nothing until you write one.
Turning on more than one channel notifies the driver more than once
The panel note above the table says this directly: enabling Mobile Push and Email together for the same trigger sends the driver two separate notifications for the same event — the channels do not know about each other. Zippykind's own recommendation is to enable push only for drivers.
What a driver template can and cannot reference
These templates use the narrower driver-info family of merge tags: ticket, customer and pickup-location fields, plus DriverName and DriverPhone. There is no [TrackingLink], [TrackingReceipt], [Notes], [Signature], [Photo] or [SignLink] here — those are customer-facing artifacts and are never substituted in a driver notification, so typing one into a driver template leaves the literal bracketed text in the message. See the full merge tag reference for exactly what each tab supports.
What stops a driver hearing anything at all
If Send Push Notifications Only To On-duty Drivers is on (the General Settings tab) and the driver is off duty at the moment the trigger fires, none of the three triggers on this tab reach that driver — not push, not SMS, not email, because the code that sends all three returns before checking any of them. See General Settings tab explained.
Saving
Press Save Notification Triggers at the bottom of the tab. It saves this tab only.