Set up customer notifications

The Notifications workspace is where you decide what happens when something changes on a delivery — when it's picked up, when the ETA slips, when a driver is assigned — and who hears about it. You build a trigger, write the message it sends, and point it at one or more destinations (an email inbox, an SMS number, a Slack channel, and more).

You'll find it under Notifications. The page header reads "Notifications" with the subtitle "Manage notifications for your organization".

The model: trigger → message → destination

Every notification is one trigger that ties three things together:

1. When it fires — the trigger Type (for example, Delivery Status Transition) plus its per-type Settings (for example, when a delivery transitions to Delivered). This is the firing condition.
2. What it says — an optional message you compose, with {{merge fields}} that Nash fills in from the delivery when the message is sent.
3. Who receives it — one or more destinations you've set up, each with its own channels (email, SMS, Slack, and so on).

A single trigger can send to several destinations at once, and each destination can override the message it gets. The firing condition and the message config live together in one drawer, so you set up the whole notification in one place.

The three tabs

The workspace has three tabs. The Triggers and Destinations tabs show a count badge when they hold items; the Settings tab has no badge:

• Triggers — the list of notifications you've built. This is where you create and edit them. See create a notification trigger.
• Destinations — the contact groups a trigger can send to, and the channels on each. See manage notification destinations.
• Settings — your organization's SMS Sender Configuration (Twilio credentials for sending SMS). See the notification trigger reference.

Note

The Settings tab is hidden for provider organizations.

Find and filter

Above the list, a toolbar gives you:

• Search — match triggers or destinations by name.
• A status filter (Triggers tab only) — All statuses, Active, or Inactive.
• A New Trigger / New Destination button — the label follows the tab you're on.

The Triggers table lists each trigger across Name, Description, Destinations, Type, and Status. Select a row to open it for editing.

What it produces

This workspace is operator-facing — the customer never sees it. What they see is the message it produces: the SMS, email, WhatsApp, or push notification that lands from a trigger you built. How and when that message is actually delivered is handled by Nash (and, for SMS, your Twilio sender); this page controls the trigger, the template, and the destination.

Related

• Create a notification trigger — build one end to end.
• Manage notification destinations — set up who receives them.
• Notification trigger reference — every trigger type, every merge field, and the SMS sender settings.
• Looking for the tracking page a customer opens from their link? That's a separate surface — see customize your tracking page.
• Broader workflow automations (a distinct concept from notification triggers) live in Automate.