The Intelligence Dispatch — Issue No. 1

← Modern edition

Lead

The Analyst Arrives

A read-only colleague for Dispatch, grounded in your company warehouse

By the Command Intelligence desk · Early Access

For years, the day’s work lived in grids, filters, and a thousand tiny clicks. This morning, you can ask Dispatch a question in plain language and get an answer grounded in your own company’s data.

Welcome to the first issue of what we hope becomes a useful habit: a short dispatch when something real lands in Command Intelligence. Not a feature dump. A briefing on what changed, why it matters on a busy board, and how to try it without a training deck.

The headline act is the Analyst: 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. It reads from your operational data warehouse. It cannot hold, void, or rewrite anything. If a number feels off versus the live screen, remember the warehouse can lag a beat. Trust, then verify on the record.

We are starting narrow on purpose. A small set of Early Access customers. Dispatch first. Real questions before a wider rollout. That is the point of this issue: put the tool in your hands, then tell us what it got wrong.

Field Notes · Prompts for the Working Board

Copy a line, paste it into the Analyst panel, 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

Start wide. Ask for the unusual, the late, the at-risk.

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

Tickets are where the day gets noisy.

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

Open a ticket, open the Analyst, ask it to narrate.

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

Say chart and mean it.

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?

Tip

You can ask about an order by its everyday number (“What happened on order 50471 last week?”). When the Analyst names an order, ticket, customer, or project from grounded data, those names become links back into Dispatch.

For Dispatchers · What Landed

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 — orders jump straight to the order’s detail page.
Live answers Replies appear as they are written instead of arriving all at once.
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; a toast lets you know when a background answer lands.
Long threads Older turns compress automatically near the limit, so conversations keep going.

For admins

Command Center usage & schedules

Command Center shows AI consumption by profile, month by month, against the credit limit. Pools follow the annual contract term. The table opens sorted by total, grouped by profile, with a share-of-total column and filters above the chart.

In the AI app, admins can set a question on a recurring schedule with its own timezone, see last and next run, and refine a draft prompt against the target agent before saving. Platform admin and platform support activity no longer drains a customer’s pool. Users without entity-wide permission see only their own usage.

· Advertisement ·

How to try it

Three steps

Open the sparkle icon in the Dispatch header.
Copy a prompt from Field Notes above.
Rate the answer and report warehouse lag when numbers disagree with the live screen.

Also shipping

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; defined read-only agent; support can retrieve a full run with feedback.

Classified Advertisements

LOST — one attach ritual, last seen shortly before Early Access. If found, do not return.
FOR HIRE — read-only colleague. Does not hold, void, or rewrite. References on request at the sparkle icon.
NOTICE — the warehouse may lag a beat behind the live screen. Trust, then verify on the record.
WANTED — your hardest question about today's board. Reward: a grounded answer with links.
FOUND — assorted tickets out of sync, grouped by status. Owners may claim at Deliveries.
SITUATIONS — dependable schedules seek recurring questions. Own timezone kept. Apply: Command Center.