Email templates you write once

Highlight

Email templates you write once. A delivery email usually gets written several times: once on the "on its way" notification trigger, again in the workflow that handles late orders, again in the one for scheduled orders. Each copy drifts, and fixing a typo or swapping in a new logo means finding every one of them. Engage → Email templates keeps those emails in one library. Workflows and notification triggers point at a template, and when you publish a change, every one of them sends the new version.

• Build it as a designed email. The editor works in blocks: headings, buttons, images, dividers, sections, and two-column rows, with variables inserted as chips. The Design panel sets typography, colors, width, padding, and corner radius, and the preview shows the email at desktop and mobile widths with sample data in place of the variables.
• Start from six delivery emails. Add starter templates adds Delivery booked, Order is on its way, Order delivered, Delivery unsuccessful, Delivery time updated, and Delivery feedback request ready to edit.
• Draft, then publish. Save draft never changes what customers receive. Publish makes the draft live and first lists the Affected workflows and Affected notification triggers, so you see what an edit will reach before it goes out. If a colleague saved the same draft while you were editing, you choose whose version to keep.
• Use it from a workflow. On Send email, set Email content to Use a template. The workflow keeps its recipients; the template supplies the subject and body.
• Use it from a notification trigger. On a delivery trigger, each recipient group's email contacts can get a template, while contacts on other channels get the trigger's Message for other channels. If a template can't render at send time, Nash sends the trigger's inline subject and message instead, so the customer still hears from you.

Viewing templates needs read access to notifications, and editing them needs write access. See Email templates.

New & improved

Portal

• The Routes grid gained a planning toolkit. (For organizations with Routes turned on and Routing UI set to Grid.) See Plan routes on the Orders map.
• A summary over the tables totals the day's routes, stops, orders, unassigned orders, distance, time, and capacity. It counts routes that are Late, Over capacity, or have no driver, and clicking Late or Over capacity lists only those routes. Show plan metrics adds Window compliance, cost, cost per drop, and drops per hour, each compared with the plan and with your last change.
• Plan check lists what's left before you dispatch: unassigned orders, routes with late stops, routes over capacity, routes with no driver or vehicle, and empty routes. Each line takes you to its route.
• Assign a driver or vehicle straight from the route table, with a warning when the driver is already on another route. Tick routes to Dispatch Routes or Archive empty routes, or tick stops to Unassign them.
• A late stop shows how late it is, and a window that crosses midnight shows its day.
• Drop unassigned orders or ticked stops on the map and they join the nearest drawn route, or drag a stop's pin onto another route. A stop's row and its pin highlight each other.
• The unassigned list filters to Ready to route or Needs attention, with the reason an order needs attention.
• On more than one monitor, move the summary, stops, or routes panel to a New window, or open the map in its own window. Each window stays in step with the others.
• Route colors no longer use reds, so they don't read as warnings, and the map's pins are smaller. This applies on every map.
• When you edit routes on the Orders map, Resequence the changed routes re-optimizes the stop order and timing of the routes your change touched. Leave it off to keep your order and update only the times. The setting is saved per user. (For organizations with Routes turned on.)
• Selecting orders or routes opens a compact action bar. The main action follows what you selected, such as Dispatch or Create Route, and the rest sit in its overflow menu.
• Split Batch numbers its stop cards in stop order. Select stops by number takes a range of stops, and Shift-click selects a range.
• The info tooltip on a custom event someone added by hand names who added it.
• The Store Location filter on Activities lists every store, not just the first 100, and has a search box.

Platform API

• API keys can be given the Contracts permission group when you generate or edit them, so a key can read your provider contracts with GET /v1/contracts.

Orchestration

• Notifications a workflow sends show on the delivery's timeline with their recipients, as notification-trigger sends already did. Sends that failed are recorded too.

Nash Agent

• Every version of a custom agent's file has Download, so you can read an older version without restoring it. The history opens as soon as a file has one earlier version. See Go back to an earlier version of a file.
• Wide tables in a chat answer keep their column widths and scroll sideways.

Fleet

Driver App version 1.14 is in the App Store and Google Play. Changes marked 1.14 need that version.

• Choose which stops skip item marking: any of pickup, dropoff, and return. At those stops the driver sees how many items there are, with nothing to tick or scan, and Nash marks the items picked up or delivered when the stop is completed. Photo, signature, and ID requirements still apply. Skip item marking at these stops replaces the old on/off setting under My Fleet, and a driver group can override it. (Opt-in.) (1.14)
• New Camera Experience (beta), in the Driver App's settings, puts the package list over a full-screen camera. Every barcode in view is boxed with its stop number and customer name and colored by whether it belongs to this stop, is already scanned, belongs to another stop, or isn't on the route. A package counts only once it's inside the guide brackets. (Off by default; each driver turns it on.) (1.14)
• On a pickup's package list, a canceled order's items sit in their own greyed section marked Canceled, and scanning one warns the driver not to load it. Canceled orders don't count toward the pickup or block completing it. (1.14)

Fixes

Portal

• Changing the provider on a dispatched route, from the Orders map or from Execute, reassigns the route's deliveries to the new provider. It used to change only the route's label.
• Saving a shift template in the Portal keeps the breaks, optimization settings, driver, and vehicle set on it through the API or a CSV upload.
• An order removed from dispatch also leaves its route's job, so the job no longer lists it.
• A delivery created from an ingested email shows that email again.
• Route times on a depot's load stop are no longer struck through.
• A workflow's trigger shows its own settings after you've opened another workflow.
• The address field keeps focus while suggestions load.
• The example CSV for refund resolutions downloads again.
• A provider finishing Stripe onboarding, or returning from Stripe's dashboard, lands on Billing.

Orchestration

• Workflow conditions compare an order's item count, value, and tip as numbers, so "greater than 9" matches 10.
• A variable with no value fills in as empty text, not "None", and two variables in one field, such as {{order.id}}-{{order.reference_id}}, both fill in.
• A live test of an email or SMS step sends once to a recipient listed twice.

Nash Agent

• Approving an action that then fails, such as "Order not found", shows it as failed with the error, and you can approve it again. It used to read "Action approved".
• A scheduled agent that produces more than three files emails its report files first. The email used to arrive with no attachments.
• A Google Sheets tab connected without a cell range picks up rows added after you connected it, such as new form responses.
• An agent's Runs tab lists the runs colleagues started and shared with your organization.
• Saving in the agent builder keeps settings the builder doesn't show.

Fleet

• Delivered orders stay delivered when the driver returns to the store at the end of a route. They could be marked returned.
• A proof-of-delivery photo taken offline uploads once the phone reconnects. It used to fail and leave the driver stuck on the stop. (1.14)
• Opening and closing Reassign Provider on a job no longer makes the Driver App lose the driver group's settings and ask for each package to be marked. (1.14)
• The pickup package list scrolls and responds on low-end Android phones. (1.14)
• Fewer map crashes and freezes: on iOS, the hangs on the first stop's pin and when the app goes to the background; on Android, a map crash. (1.14)
• Buttons at the bottom of sheets and screens clear Android's navigation bar. (1.14)
• On iOS, the number pad no longer covers the camera's shutter when a photo or QR field follows a number field. (1.14)
• Long checkbox labels on driver forms wrap inside the screen. (1.14)