Release notes

​

Week of June 15, 2026

​

Highlight

​

New & improved

• Create and update custom scheduled agents directly from chat — describe the report or watch you want, and the Agent sets up the schedule and email delivery, confirming before it saves.
• A single custom agent can now run on multiple schedules (for example, a morning and an evening report) without cloning it.
• Draft prompts are reviewed before you save an agent, flagging instructions that belong in enforced settings — scope, output schema, guardrails, cost caps — with suggested fixes you can apply or undo.
• Analytics queries can export the complete result set as a downloadable CSV or Excel file, delivered in chat or attached to scheduled runs, instead of a capped preview.
• Chat now accepts Word (.docx) and PowerPoint (.pptx) uploads, reading their text so you can ask the Agent about documents and decks.
• Administrators can switch the Sessions list between their own chats and all users’ chats across the organization, with an owner label on each session.
• Custom agents and org defaults pinned to an older model tier now run on the latest model in the same tier automatically. The “Most capable” option reflects the latest Opus model, and new custom agents default to the Balanced tier — you can still choose any model.
• Insight stat changes are colored by whether the change is good or bad for your operation — a falling cost or error rate reads positive — rather than by raw direction.
• Insights render inline, full-size charts and support sorting, filtering by impact and category, a “has chart” filter, and load-more pagination.
• Pulse charts (runs per day, trend, and outcome donuts) are interactive with hover tooltips.
• Follow-ups sent while the Agent is mid-answer are folded into the current run and shown as separate chat bubbles, and continuing a teammate’s shared session loads the full conversation history.

• When a manual reassign targets a dispatch strategy with a single allowed provider, the order automatically gets fresh quotes and dispatches, instead of waiting for manual quote selection.
• Route triage labels internal-fleet assignments and quotes with their driver-group name instead of a generic “Internal Provider.”
• Reoptimizing a route asks for confirmation to prevent an accidental recalculation.
• Manually assigning a delivery to a single driver makes it visible in their Active tab and notifies them immediately, overriding the dispatch-before-pickup timer.

• Several provider integrations now set the carrier trackingUrl on GET /jobs/<id>, the jobs list, and webhook payloads, alongside the existing Nash tracking link.
• Shopify packing slips refresh as soon as finalized tax and shipping totals are available, instead of waiting for the lagging order-updated webhook.

• New POST /v1/zones/query returns zones in a paginated {data, meta} envelope, filterable by ids and externalIds — replacing per-zone GET loops.
• New POST /v2/orders/upsert/bulk returns a {results, summary} envelope with per-row success and failure outcomes and error details.
• A new endpoint removes a route-based order from dispatch, freeing its package external identifier for re-dispatch and returning the updated order.
• The Driver Geolocation notification trigger now accepts a deliveryStatusIncludes array, so one trigger can fire across several delivery statuses.

• Driver item acceptance now appears across the Portal: per-stop picked, delivered, and returned counts on routes, item events on the route timeline, per-item rows on the delivery timeline, and return condition and notes on returned items.
• Search the fleet vehicle list by name, type, make, model, license plate, or external ID.
• New Route Card Fields settings under My Fleet let you hide price, status, metrics, addresses, or stops on driver-app route cards.

• A Shift column (hidden by default) on the Orders table and CSV export shows the shift code for both routed and delivery-window orders.
• Item and sub-item details now show each item’s Category.
• Delivery details show when a driver adjusted an item’s quantity at pickup, with the original count struck through next to the new count.
• Redesigned Billing settings: a clearer payment-methods view with expiry warnings, an invoices list with open-balance cues and Pay, Receipt, and PDF actions, and a hosted billing-portal fallback for accounts where a payment method can’t be added in-app. Organizations billed outside of Stripe now see their custom billing report here.
• Find a notification trigger or destination by pasting its ID into the Notifications search.

​

Fixes

• A single agent with an invalid saved configuration no longer takes down the whole agents list — it degrades gracefully while the rest stay available.
• Disabling an agent or stopping an entity watch clears its outstanding confirmation prompts so they no longer linger in the Needs Attention queue.
• Files the Agent generates in Slack (Excel, CSV, PDF) are reliably saved and delivered as downloads.
• Run-count labels on the Pulse and runs-per-day charts are no longer clipped.

• Orders created without a description or vehicle size apply package defaults reliably instead of failing pre-dispatch quote requests.
• Dispatch-strategy swaps regenerate quotes against the new strategy and clear any stale selection, so orders ship on the correct provider.
• Route stops keep stable, unique IDs across copy, split, and upsert, and a route completes automatically when its last open order is removed.
• Manually-added job and order events trigger matching event-type workflows.
• Address sync no longer overwrites merchant-owned provider store names.
• Creating a courier with workRelationship or dateOfBirth set succeeds instead of returning a 400.
• Dispatching an order with missing pickup or dropoff time windows returns a clear TASK_MISSING_TIME_WINDOW error.
• Re-creating a package for the order that already owns it no longer raises a false duplicate-identifier error; genuine cross-order duplicates still return RESOURCE_ALREADY_EXISTS.
• Auto reassign-on-failure evaluates provider eligibility against the fallback strategy’s allowed providers.
• AU PO Box dropoff addresses validate when the geocoder omits the postcode, and request-log search recovers records that were indexed with a null external identifier.
• An order pointing at a soft-deleted dispatch strategy is recovered automatically when that is its only validation error.
• Provider webhooks and quotes tolerate non-JSON content types and fractional-second timestamps.
• Quote and provider type values always serialize as strings (for example, PICK_AND_PACK).

• Individual pickup and dropoff markers reappear on the deliveries history map when zoomed in, with scheduled time and ETA back in the tooltips.
• Changing items on a dispatched order reconciles per-item pick states, so added items become trackable and removed items no longer appear as phantom pending items in the driver app. Removing an order from dispatch resets its item pick states.
• Drivers are no longer blocked from finishing a route after it’s split mid-delivery — stop actions stay available.

• Workflow filters using “starts with” and “ends with” save and apply reliably.
• Drawing zone, coverage, and route-restriction polygons works again.

​

Multiplayer Agents, Testable Workflows, and Smarter Route Control

​

New features

• Collaborative sessions: Multiple teammates can join the same Nash Agent session live, see each other’s messages, and work through investigations together in a single shared thread.
• Mid-run steering: Send a follow-up while Nash Agent is still working and it folds the new direction into the current turn, with no cancellation or restart required.
• Code execution with file artifacts: Nash Agent can run analyses on the fly and stream Excel, CSV, and chart files back into the chat as it works.
• Per-session spend caps: Admins can cap each Nash Agent session at a maximum number of tokens or USD at the org level, with per-custom-agent overrides for tighter control.
• Webhook-triggered custom agents: External systems can kick off custom agent runs via a webhook authenticated by a Nash API key, with no user login required.

• Workflow simulation: A new Test surface in the workflow builder runs an entire workflow or a single step against mock data, validates channels and variable interpolation, and tags executions so they’re easy to distinguish from real events.
• API workflow trigger: Any workflow can be invoked directly through POST /api/v1/workflows/{id}/trigger, with optional input data and both synchronous and asynchronous execution modes.

• Customers workspace: A new Customers section in the merchant portal lists every customer in your org, with a detail view showing lifetime stats, recent orders, last-meter preferences, a 7×24 delivery-times heatmap, and recent proofs of delivery.

• Exception status lifecycle: Route exceptions move through clear open, in-progress, resolved, and dismissed states, with consistent badges across the portal so dispatch teams can track investigations end to end.

​

Improvements

• Post-dispatch route edits: Operators can modify routes after they’ve been dispatched without canceling and recreating them, controlled by a new org preference.
• Auto-dispatch on route creation: Newly created routes can be auto-dispatched the moment they’re created (including via the routes API), and a failed dispatch attempt no longer blocks the route itself from being created.
• Configurable return routing: Returns routing is configurable per store, so each location can pick the approach that matches its operations.

• Default navigation app per driver: Drivers can pick their preferred map app from a per-user setting, with Nash’s in-app navigation available behind a per-fleet toggle.
• In-app navigation polish: The map stays active throughout a trip, supports pinch-to-zoom and free panning, and shows a destination pin with which side of the road the dropoff is on.

• Searchable activities: The Activities screen has searchable display names, filter counts on every facet, and a new Store Location filter for faster triage.
• New webhook & API surfaces: Custom form submissions emit a webhook event, order items are exposed in webhook payloads, and route assignments are available via GraphQL.
• Inbound delivery update API: Internal fleets and Nash-connected partners can drive their delivery state (status, coordinates, proof of delivery, courier identity, and failures) via single or bulk PATCH /v1/fleet/deliveries endpoints authenticated by their org API key.

• Vehicle dimensions in route planning: The routing engine factors vehicle height, weight, length, and width into route plans, so trucks and vans avoid road segments — including low bridges — they can’t legally or safely use.

​

Smarter Optimization, Multi-Session Agents, and Stronger Driver Tools

​

New features

• Optimization review: A new Review & Dispatch surface in the Optimize Orders drawer separates routes that need attention from those safe to dispatch, with toggleable Table, Map, and Timeline views.
• Replayable optimization workspace: A new portal app lets teams replay past route plans with adjustable parameters to compare outcomes and tune dispatch strategies.

• Multi-session Nash Agent: Manage multiple Nash Agent sessions in parallel, making it easier to track several investigations at once.
• Chat cards for Nash objects: Nash Agent renders driver, order, and route information as rich, in-conversation cards for faster context.
• User-level Agent permissions: Admins can scope Nash Agent access to specific users for finer-grained governance over who runs AI workflows.

• Route search and filtering: Drivers can search routes by customer name or phone and group routes by merchant for faster trip selection.
• WhatsApp messaging: Drivers can message customers via WhatsApp directly from the Driver App, in addition to SMS.
• Route flags: Dispatchers can flag routes that need attention, making it easier to track and triage problematic deliveries.

​

Improvements

• A new route.stops_updated webhook event fires whenever a route’s stops change, keeping integrations in sync with mid-route adjustments.
• House photos in create-order API: Drivers see a photo of the customer’s dropoff location at the stop when a house-photo link is included on order creation.
• Delivery status backfill: The status update API accepts an occurred_at parameter, so integrations can record the real time a status change happened.
• Return condition tracking: Drivers can mark returned items as good or damaged in the Driver App, and each update fires a webhook for downstream systems.

• Redesigned org switcher: A search-first org picker on sign-in and in the sidebar, plus static sidebar chrome when toggling between main and settings views.
• Type-to-confirm reassignment: A new confirmation dialog protects post-pickup driver reassignments from accidental clicks.

• Redesigned route card: The Driver App route card shows the delivery window more clearly and groups stops by merchant for at-a-glance trip planning.

​

Fixes

• The optimization results drawer no longer shows the wrong contract when opened from an activity link.
• Portal shift links use path segments instead of query parameters, so the right shift opens consistently when shared.

​

Smarter Coordination, Stronger Privacy, and More Control Across Workflows

​

New features

• Staggered Arrivals AI Agent: Coordinates staggered arrival times to keep delivery scheduling efficient and reduce congestion at pickup and dropoff locations. Fully configurable from the portal.
• Face Masking AI Agent: Automatically detects and pixelates faces in proof-of-delivery photos to protect the privacy of people involved in deliveries.
• Structured prompt-to-response timeline: The activity timeline groups prompts, tool calls, and responses into cohesive conversation cycles, making AI-driven workflows easier to follow and audit.
• Grouped tool calls under phases: Tool calls are visually nested under phase updates (for example, “Investigating” or “Implementing”) for a clearer progression of work.
• Compact passing quality checks: Multiple passed quality-check rows condense into a single summary, reducing timeline clutter.
• Refund request experience: The refund submission page displays separate Original, Requested, and Approved amounts, giving providers and customers more transparency at every step of review.
• Enhanced route optimization analytics: Added performance tracking and analytics for route optimization, including usage data and simulation insights.

​

Improvements

• Dynamic Dispatch: Settings include advanced customization of dispatch strategies and presets like “Balanced” and “Promise-Based,” giving teams precision without sacrificing usability.
• The Bird’s Eye map view includes drop-off and pickup time tags and business information for faster operational decisions.

• Custom notification configurations are available in additional sandbox environments for testing real-world use cases.
• Improved timing instrumentation across the notification pipeline.
• Support for custom SMS sender settings, including Twilio accounts and alphanumeric sender IDs.
• Notification pipelines support asynchronous webhook processing, reducing delays and improving throughput.

• Improved timeline icons: A standardized icon system across the platform for better readability and consistency.

​

Fixes

• Resolved intermittent errors in delivery rescheduling workflows and timeline evaluations.
• Fixed cache connection delays affecting notification performance.
• Corrected missing report data and improved dashboard query handling for faster load times.