Skip to main content
Nash has a built-in, customizable notifications platform that lets you own the end-to-end customer experience and keep internal teams up to speed on delivery events. Each notification separates the trigger and message from the audience (destination), so you can send the same message to different audiences — or different messages on the same event — without duplicating work. Notifications can be delivered across multiple channels:

SMS

Email

WhatsApp

Slack

Webhook

​
Customer notifications & the tracking page

Out of the box, your account includes customer-facing SMS notifications on key status transitions — for example Pickup Complete, Dropoff Enroute, and Dropoff Complete — plus internal notifications (such as Delivery Booked and Task Reassigned) that are disabled by default. You manage these under Settings > Triggers in the Nash dashboard. Customer messages typically include a tracking link ({{job_tracking_link}}) that opens Nash’s live-tracking page, where the customer sees the courier’s position on a map and real-time status updates. You can also embed that same live-tracking experience directly in your own web or mobile app — see Embedding the Nash live-tracking experience.
For the full catalog of triggers (status transitions, delays, dispatch failures, incident reports, and more) and the dynamic variables available in messages, see the Notifications reference.

​
Deny list

The deny list is how you suppress notifications for a specific contact who has opted out of communications. Each entry records a type of communication and the value for that type — for example an email address or a phone number — giving you fine-grained, per-contact control over who Nash messages.
1

Add a contact

Add a contact to the deny list (POST /v1/organization-management/notifications/deny-list) opts a contact out. Provide the required type and value; that contact will no longer receive delivery notifications.
2

Review the list

Get contacts in the deny list (GET /v1/organization-management/notifications/deny-list) returns the suppressed contacts, with page / pageSize pagination.
3

Remove a contact

Remove a contact from the deny list (DELETE /v1/organization-management/notifications/deny-list) opts the contact back in so they resume receiving notifications.
The deny list operates at the organization level. Adding a contact suppresses Nash-sent notifications for that contact across deliveries, not just a single job.

​
Customization

Notification messages support dynamic variables so each message reflects the specific delivery. Variables span the customer, pickup, dropoff, job, and delivery-provider context — for example {{customer.first_name}}, {{pickup_business_name}}, {{dropoff_eta}}, {{job_tracking_link}}, and {{driver.name}}. The complete list, along with every available trigger, is maintained on the Notifications reference page, and Nash adds to it regularly. For richer customer-facing customization — re-skinning the live-tracking UI or embedding only selected widgets — see the advanced options in Embedding the Nash live-tracking experience.

​
Next steps

Notifications reference

Triggers, channels, and dynamic message variables.

Add to deny list

Suppress notifications for a contact.

Get deny list

Review who has opted out of communications.

Live-tracking embed

Embed the Nash tracking page in your own app.