Visuals in answers

Agents can draw the numbers — and explain how things connect

Every agent that can draw an in-chat dashboard can also add a diagram when it makes an answer easier to understand. The visual is part of the message, next to the agent's written explanation.

What you can ask for

For numbers across categories or over time, ask for a dashboard:

• "Show me turnover by month for this year, with a trend and the totals."
• "Compare open cases per team for the last quarter — chart it."
• "Top 10 customers by revenue this year, as a dashboard with the share of the top three."

For a process, relationship, architecture, sequence, state or timeline, ask for a diagram:

• "Show how a sales order moves from draft to invoicing."
• "Explain the relationship between customers, orders and invoices with a diagram."
• "Draw the approval flow and show where each team acts."

You do not have to name a visual. When an answer describes a process, flow, sequence, state change, relationship, architecture, dependency or timeline, the agent leans toward adding a compact diagram when it makes the path or connections easier to grasp. Simple explanations remain text only. You can still say "as a line chart", "show the process", or "plain text only".

What you get

• KPI cards for headline figures — total, average, best month, change.
• Bar and line charts for breakdowns and trends.
• Doughnut charts for shares of a whole.
• A table when the exact rows matter.
• A process or sequence diagram for steps and interactions.
• A state or relationship diagram for statuses, dependencies and structure.
• A timeline for ordered milestones.

Visuals follow your theme, work on a phone, and stay in the conversation. You can pan and zoom a diagram, fit it to the available space, open it full-screen, copy its source, or download it as a PNG.

Diagram controls sit in their own slim row, so they do not cover steps or connections. A sequence of about five or more stages is a strong candidate for short alternating rows stacked as a snake. This uses the conversation width without turning the diagram into one long row or a very tall column. Short processes may remain in one row, while processes with real branching, convergence, or hierarchy usually use a top-to-bottom layout. Process steps usually show a short bold name with one line of detail underneath. At each turn, the arrow connects the last card of one row directly to the first card of the next row, so the sequence remains unambiguous. The diagram is displayed in the layout the agent generated; Operator does not rewrite it automatically.

Agents can also choose colors from Operator's accessible chart palette when color helps distinguish categories. For example, ask: "Show revenue by product as a colorful bar chart, and keep the same color for each product in the share chart." The agent cannot supply arbitrary colors, so every chart continues to work in both light and dark themes.

Records, statuses and timelines

The same dashboard can also show everyday ERP shapes:

• Record cards — a few specific records at a glance: name, a status badge, key fields, and a link to open it in ERP.net. When the retrieved data confirms that one document is the parent of another, arrows connect the cards from parent to child.
• Status stepper — where one document stands: order, delivery, invoice, payment, with the current step highlighted and dates under finished steps.
• Comparison — this period next to the previous one, with the change and a tiny trend line.
• Timeline — dated milestones such as a delivery schedule or payment plan, with overdue points marked.

For ERP.net document states in Bulgarian, visuals use the standard names: Нов, Планиран, Твърдо планиран, Пуснат, Завършен and Затворен.

Try:

• "Where is sales order 4711?"
• "Show order 4711 and the documents created from it."
• "Show me the three overdue invoices of Acme."
• "Compare turnover this month with last month."
• "What is the payment plan for contract 88?"

Good to know

• Every figure comes from data the agent actually retrieved. If it cannot get the data, it says so rather than drawing something.
• Each answer carries one dashboard, with the written explanation around it.
• An answer may include both one diagram and one dashboard when the diagram explains the flow and the dashboard explains the figures. For example: "Show our order-to-cash process, then chart this quarter's volume at each completed stage."
• These are visuals for one answer, not a saved BI dashboard or an editable process model: there are no filters, no drill-down and no automatic refresh. To change the view, ask the next question.
• Inside apps built with the App Builder and in background runs, agents do not send these visuals — the containing experience owns its presentation.