The assistant routes data questions to charts and tables, rule descriptions to the rules builder, and definitions or chart adjustments back into the conversation. Every answer links to the rows it used.

The assistant reads the message, splits it where needed, and sends each part to the chart engine, the rules builder, or the definitions layer. The user keeps writing in one place.
"Revenue by region for Q3 as a stacked bar."
Questions run against the same NetSuite-derived data the dashboards use. Answers return with the underlying rows and a chart that can be pinned to any dashboard.
"Flag any shipment that takes more than 2.5 days to deliver."
The assistant parses the condition and produces a draft for the rules builder with branches, severity, and reactions filled in. The draft can be tested before activation.
"What counts as gross margin here? Restrict the data to last year."
Definitions, calculation breakdowns, and chart adjustments stay inside the thread. A single message can combine data, rule, and definition asks; each part is routed independently.
Type “flag any shipment that takes more than 2.5 days to deliver” and the assistant produces a draft with the matching branches, severity, and reactions filled in. The rules builder opens with the draft loaded.
Drafts from chat use the same rule primitive as hand-authored ones. They appear in the rules list, can be tested against historical data before activation, and support manual revisions.

Bring a question from last quarter’s close. We’ll show the answer, the rows behind it, and how the same thread would draft a rule to catch it next time.