The Analyst arrives

The job

When you are on a Dispatch board, you want to ask a question in plain language, so you can see what needs attention without working through every grid.

What changed

The Analyst is a read-only panel inside Dispatch. Open it from the sparkle icon in the header. Ask which orders look at risk, what is odd on today's tickets, or how a customer has been running.

Why

The day's work lived in grids, filters, and a thousand small clicks. A question should reach the same operational data.

Impact

Open the sparkle icon and ask. The Analyst cannot hold, void, or rewrite anything. If a number disagrees with the live screen, check the record. The warehouse can lag by a short interval. Nothing about how you dispatch has to change.

We are starting narrow on purpose. A small set of Early Access customers. Dispatch first. Real questions before a wider rollout.

How to try it

1. Open the sparkle icon in the Dispatch header.
2. Copy a prompt from Field notes below.
3. Rate the answer; report warehouse lag when numbers disagree with the live screen.

Field notes — prompts for the working board

Copy a line, paste it into the Analyst, follow the thread. Stay on Orders, Deliveries, or Customers when you ask. If you skip a date range, it usually looks at about the last seven days.

From the order list

• Summarize the orders beyond this screen and highlight anything unusual.
• Give a status overview for the orders beyond this screen, including delivery timing risks.
• Which orders look late or at risk today, and why?

From deliveries

• Summarize the tickets beyond this screen — group by status, call out voided or out-of-sync loads, and highlight tickets that need attention.
• Give a status breakdown of the tickets beyond this screen. Flag sync issues and patterns across customers, plants, or drivers.

On a single ticket

• Explain this ticket's current delivery state — supplier status, customer status, sync, and any reason codes.
• Review this ticket for problems or gaps I should know about.

When you want a picture

• Show a bar chart of ticket counts by plant for the last 7 days.
• Which customers ordered the most volume last week? Chart the top 10.
• What happened on order 50471 in the last 7 days?

You can ask about an order by its everyday number. When the Analyst names an order, ticket, customer, or project from grounded data, those names become links back into Dispatch.

What landed

• 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.

For admins — Command Center usage & schedules

• 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.

Also shipping

• 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.

That is Issue No. 1. Try one prompt on a real morning board. Rate the answers. Tell us what the warehouse got wrong, what the Analyst missed, and which question you wished you could ask.