Visualizations

Turn ideas and information into interactive visual explanations with EvoX

Visualizations can turn questions, ideas, and information into charts, flowcharts, relationship diagrams, dashboards, calculators, simulations, and interactive explanations. Ask for them in an EvoX Chat or Cowork task, combine them with uploaded files and data, then inspect and refine the result in the artifact preview.

Visualizations are available in EvoX Desktop Chat and Cowork tasks. When you request a chart, dashboard, calculator, or interactive demonstration, EvoX can create an interactive HTML/SVG artifact or a static visual suited to the task.

Check availability

Choose when to use a visualization

Ask for a visualization when it explains the answer more clearly than a long text response. Common cases include:

• Compare values, trends, or distributions with bar, line, scatter, or chart-and-table combinations.
• Explain steps, dependencies, or system relationships with flowcharts, architecture diagrams, timelines, or graphs.
• Explore changing inputs with sliders, toggles, or numeric controls.
• Show spatial, location, or coordinate relationships with maps, layouts, or coordinate diagrams.
• Summarize multiple metrics with dashboards, tabs, and filters.

Specify the expected result and controls

Strong visualizations start with a clear outcome, data definition, and interaction request. Provide the source data, question, desired form, and required controls.

Analyze the attached channel-performance.csv and compare monthly organic and campaign traffic.
Create an interactive line chart with both series visible by default. Show the value and
month-over-month change on hover, add channel toggles and a month-range filter, preserve units
and source labels, and do not infer missing months.

For complex data, also define field meaning, units, allowed aggregation, missing-value handling, and facts that must remain unchanged.

Explore an interactive example

This interactive example follows a sample CSV through channel trends, the data behind a monthly finding, and a revenue simulation. The chart, lineage nodes, and simulated result respond to your input. Demo values are not real business results.

Refine and continue

Continue in the same conversation, naming the exact changes and what must remain stable. For example:

• Add or remove controls, filters, tabs, and buttons.
• Correct sources, units, formulas, aggregation, or missing-value handling.
• Adjust titles, labels, legends, color, layout, and dark-theme behavior.
• Use a specific file, worksheet, column, or date range from the attachments.
• Add explanatory copy, annotations, reference lines, thresholds, or anomaly markers.
• Add sliders, hover details, animation, or other interactions that improve understanding.
• Change the chart form while preserving the source data and metric definitions.

Follow-up requests revise the current result. State which data, interactions, and visual structure must be preserved before requesting broader changes.

Share or reuse the result

Conversation visualizations work well for explanation, comparison, and exploration. To hand off or continue the work:

• Save the HTML/SVG artifact or export a screenshot together with the source data and metric definitions.
• Keep the artifact, source files, and revision requirements in one project.
• Review files for personal, confidential, or restricted data before sharing.
• Move to the Sites workflow when the result needs durable hosting, access control, or persistent data.

Improve accessibility

Request a clear title, units, legend, and text summary, and do not rely on color alone to communicate state. Distinguish similar colors with shapes, line styles, or labels, and give controls readable names and sufficient contrast.

On narrow screens, allow legends and controls to wrap or switch complex horizontal layouts to a vertical arrangement. Review both desktop and mobile sizes before sharing so text, controls, and data do not overlap or clip.

Handle generation failures

Complex visualizations can take additional time. If the result is blank, inaccurate, or unresponsive:

• Reduce the request to one chart or one question.
• Trim the data and define field types, units, date ranges, and missing-value rules.
• Remove optional animation and complex controls, then add them back one at a time.
• Name the exact worksheet, column, or data range in the uploaded file.
• Fall back to static SVG, an HTML chart, or a table while preserving the source data.
• Describe the concrete error and expected result in a follow-up so EvoX can revise the current artifact.

Related docs

• Sites
• Projects and chats
• File handling
• Image input

EvoX Docs · Features · Workflows