Known issues to flag

Set expectations honestly during demos and blueprint sessions. Flagging these early builds trust and avoids surprises.

Confirm before you demo, every time. Run your full demo sequence on the actual demo environment shortly before the session. Reports depend on data and filters; a clean dry run prevents an empty result in front of the customer.

• Reports need the right filters. An empty result usually means a filter was off, not that data is missing. Prepare known-good filters for the reports you will show.

• Simple list-style reports are not run through the report tools. If a customer asks for one specifically, use a standard analytical report or a list request instead, and explain why.

• Phrase report requests with a clear period and company. Vague requests can return broad or empty results. Encourage specific questions.

• The database query and code sandbox are for administrators and trusted analysts only. Do not promise these to general users. Position them as the analyst's power tools.

• Charting happens through the dashboard tools, not inside the analysis sandbox. When showing visuals, use the chart and dashboard capability.

• Very large reports run in the background. For a smooth demo, prefer a month of data over a full year, or pre-run the heavy report so the result is ready.

• Document recognition quality depends on the scan. Use a clear, well-lit sample for the recognition demo.

• Keep the demo focused. The assistant can do a great deal. Show a tight, rehearsed sequence rather than improvising broadly.