The Intelligence Dispatch · Shipped
Everything shipped
- 38 features
- 4 releases
Every customer-visible change, newest first, one line each. Type to narrow it — the whole list is on this page, so browser find works too. Copy next to a release grabs that list for Slack or email.
2026-08-20Analyst update — 20 August9 features
2026-08-20 Analyst update — 20 August 9 features Files in the message box Attach a spreadsheet or image from the composer so the Analyst can use it with the question. @ mentions with a date range Type @ to search orders, tickets, and other records. You can change how far back that search looks. Records stay chips in charts and tables Customer, order, and ticket names stay clickable in grids and chart data, not only in the written answer. One view at a time A chart answer does not also repeat the same numbers as a table unless you ask for both. You can switch a chart to a grid from the chart menu. Chart download Export chart data as CSV or Excel from the chart menu, and cap how many points the chart shows. On-site time You can ask for time on site, including averages across customers, using arrive-job and leave-job times in the warehouse. Questions about another entity stay scoped Asking about a different company or plant does not relabel the record you already have open. Oversized screen context If the open record is too large to send in full, the chat says what was trimmed instead of failing without explanation. Rating a failed turn Thumbs still work after a turn that did not finish cleanly. Client-only error notices do not show thumbs.
- Files in the message boxAttach a spreadsheet or image from the composer so the Analyst can use it with the question.
- @ mentions with a date rangeType @ to search orders, tickets, and other records. You can change how far back that search looks.
- Records stay chips in charts and tablesCustomer, order, and ticket names stay clickable in grids and chart data, not only in the written answer.
- One view at a timeA chart answer does not also repeat the same numbers as a table unless you ask for both. You can switch a chart to a grid from the chart menu.
- Chart downloadExport chart data as CSV or Excel from the chart menu, and cap how many points the chart shows.
- On-site timeYou can ask for time on site, including averages across customers, using arrive-job and leave-job times in the warehouse.
- Questions about another entity stay scopedAsking about a different company or plant does not relabel the record you already have open.
- Oversized screen contextIf the open record is too large to send in full, the chat says what was trimmed instead of failing without explanation.
- Rating a failed turnThumbs still work after a turn that did not finish cleanly. Client-only error notices do not show thumbs.
2026-08-11Analyst update — 11 August7 features
2026-08-11 Analyst update — 11 August 7 features Late arrivals have a defined rule A ticket is late when it arrived at the jobsite after its scheduled arrival time. The answer states the definition it used, and you can ask for a grace window such as more than 15 minutes late. Dates follow your entity's time zone Questions about today, yesterday, or a specific date use your entity's time zone, so the day starts and ends when your operation does. Name matching is case-insensitive Customer, project, and product names match regardless of capitalization, and close misspellings still find the right record. Lookups use the numbers on your screen Ticket, order, invoice, and billable lookups accept the identifiers you already use. You no longer need an internal CRN. Invoice and billable line items You can ask what was charged on a billable or an invoice, including line items, quantities, and delivery addresses. Units of measure on totals A total on a quantity field only carries a unit when the underlying data supports one. Large list requests ask for a filter If a request would return more rows than are useful, the Analyst asks you to narrow the date range or filter rather than returning a partial list.
- Late arrivals have a defined ruleA ticket is late when it arrived at the jobsite after its scheduled arrival time. The answer states the definition it used, and you can ask for a grace window such as more than 15 minutes late.
- Dates follow your entity's time zoneQuestions about today, yesterday, or a specific date use your entity's time zone, so the day starts and ends when your operation does.
- Name matching is case-insensitiveCustomer, project, and product names match regardless of capitalization, and close misspellings still find the right record.
- Lookups use the numbers on your screenTicket, order, invoice, and billable lookups accept the identifiers you already use. You no longer need an internal CRN.
- Invoice and billable line itemsYou can ask what was charged on a billable or an invoice, including line items, quantities, and delivery addresses.
- Units of measure on totalsA total on a quantity field only carries a unit when the underlying data supports one.
- Large list requests ask for a filterIf a request would return more rows than are useful, the Analyst asks you to narrow the date range or filter rather than returning a partial list.
2026-08-05Analyst update — 5 August4 features
2026-08-05 Analyst update — 5 August 4 features Charts Ask for a chart — "chart ticket counts by plant for the last 7 days" — and you get a rendered visual you can ask follow-up questions about. Answers show their work Replies now cite the records behind them, so you can see which orders, tickets, or customers a number came from. Those names are links Click a cited record to open it in Dispatch. Orders go straight to the order's detail page, and links now open in the right place instead of dropping you at the wrong screen. Background answers tell you when they're done Heavier questions keep running if you move on, and you get a notification the moment the answer is ready.
- ChartsAsk for a chart — "chart ticket counts by plant for the last 7 days" — and you get a rendered visual you can ask follow-up questions about.
- Answers show their workReplies now cite the records behind them, so you can see which orders, tickets, or customers a number came from.
- Those names are linksClick a cited record to open it in Dispatch. Orders go straight to the order's detail page, and links now open in the right place instead of dropping you at the wrong screen.
- Background answers tell you when they're doneHeavier questions keep running if you move on, and you get a notification the moment the answer is ready.
2026-07-27The Analyst arrives18 features
2026-07-27 The Analyst arrives 18 features Ambient context Open from any Dispatch screen and ask. Screen context travels with the question. Linked answers Grounded order, ticket, customer, and project names open in Dispatch. Real charts Ask for a chart and get a rendered visual, plus follow-ups. History Reopen earlier conversations with full context. Dock Pin the panel left, right, top, or bottom. Long runs Heavier questions keep running while you work. Usage you can actually read Command Center shows consumption by profile, month by month, against the credit limit — sorted by total, grouped by profile, with a share-of-total column. Contract-term pools Credit pools follow the annual contract term, not a calendar month. Command Center first The AI app lands on Command Center by default; full-page chat stays a gated admin route. Scheduled runs Put a question on a recurring schedule with its own timezone, see last and next run, and refine the prompt before saving. Plain-language limits When credits run out, the message says so. Fair accounting Platform admin and platform support work inside a customer entity no longer drains that customer's pool. Clearer refusals Off-topic questions get a plain no, not a confident invention. Guardrails A blocked message stays out of later turns. Language UI is localized; replies match the language you write in. Scroll & dock New replies stay in view; dark-mode dock menus are legible. Permissions Permission errors surface; chat-less users are not bounced to chat. Safety Input and output checks; a defined read-only agent; support can retrieve a full run with feedback.
- Ambient contextOpen from any Dispatch screen and ask. Screen context travels with the question.
- Linked answersGrounded order, ticket, customer, and project names open in Dispatch.
- Real chartsAsk for a chart and get a rendered visual, plus follow-ups.
- HistoryReopen earlier conversations with full context.
- DockPin the panel left, right, top, or bottom.
- Long runsHeavier questions keep running while you work.
- Usage you can actually readCommand Center shows consumption by profile, month by month, against the credit limit — sorted by total, grouped by profile, with a share-of-total column.
- Contract-term poolsCredit pools follow the annual contract term, not a calendar month.
- Command Center firstThe AI app lands on Command Center by default; full-page chat stays a gated admin route.
- Scheduled runsPut a question on a recurring schedule with its own timezone, see last and next run, and refine the prompt before saving.
- Plain-language limitsWhen credits run out, the message says so.
- Fair accountingPlatform admin and platform support work inside a customer entity no longer drains that customer's pool.
- Clearer refusalsOff-topic questions get a plain no, not a confident invention.
- GuardrailsA blocked message stays out of later turns.
- LanguageUI is localized; replies match the language you write in.
- Scroll & dockNew replies stay in view; dark-mode dock menus are legible.
- PermissionsPermission errors surface; chat-less users are not bounced to chat.
- SafetyInput and output checks; a defined read-only agent; support can retrieve a full run with feedback.
Nothing matches that. Try a shorter word.