Chat is not a feature of Delphi. Chat is the platform. You describe what you want in plain language, and Delphi does the work — pulling data, building visualizations, running scenarios, drafting reports, and answering questions grounded in your command center.
Every other surface in Delphi (metrics, data, alerts, scenarios, reports) is something the chat can reach into and change on your behalf. If you can say it, Delphi can usually do it.
How to ask a good question
Be specific about the outcome you want, not the steps. Delphi decides which tools to call — your job is to describe the decision you’re trying to make. Name the entities, the time window, and the comparison you care about.
Vague prompts get vague answers. “Show me the numbers” forces Delphi to guess. “How has groundwater in the Rift Valley changed over the last 90 days compared to the previous quarter?” gives it everything it needs to pick the right data source, window, and visualization.
Build a KPI card for average response time on the support queue, compared to last month, down is good.
What’s driving the spike in alerts from the water quality connector this week?
If you don’t know what’s possible, just ask. “What can you tell me about this dashboard?” is a perfectly good opening — Delphi will inventory what’s connected and suggest next steps.
What Delphi can do
Delphi can create and update dashboards, add and remove visualizations, configure connectors, write alerts, run scenarios, generate reports, query your documents, and answer questions that cross multiple data sources. It can also reach out to public data — weather, economic indicators, geological surveys, census data, and more — and wire any of it into your command center as a live connector.
On the enterprise side, it can query Google Workspace, Slack, BambooHR, Workday, Salesforce, Asana, and Linear, subject to your role and the dashboard’s connected accounts. See the data connectors overview for the full list.
Add a map layer showing active FEMA disaster declarations in Texas over the last 12 months.
Create an alert that fires when the reservoir level drops more than 5% in a single day.
What Delphi will do depends on your role. Viewers get read-only access to public data. Analysts can query, explore, draft scenarios, and export reports against public and internal data. Auditors can read across public, internal, and confidential data to verify controls without making changes. Editors, admins, and owners can mutate the dashboard — creating datasets, visualizations, KPIs, and alerts. See Roles and permissions for the full breakdown.
Citations and grounding
Delphi answers from your data, not from memory. When it pulls numbers, it tells you which dataset, connector, or document they came from, and when they were last updated. KPI cards carry provenance badges you can click to see the full lineage.
If Delphi can’t find grounding for a claim, it will say so rather than guess. You can always ask “where did that number come from?” and it will walk you through the source chain. For documents you’ve uploaded, Delphi cites the specific file and flags its authority level — canonical sources carry the most weight, while reference, field report, and unverified sources are labeled accordingly so you can judge how much to trust each citation.
When to ask for a report instead
Chat is for questions, exploration, and quick changes. Reports are for anything you want to save, share, or come back to — intelligence briefs, trend analyses, risk assessments, and status updates. They’re stored in the Reports tab and can be exported to PDF.
Ask for a report when the output matters as a durable artifact. Ask in chat when you just want the answer.
Write an intelligence brief on our Q1 performance across all operational functions, with recommendations.
For “what if” questions — staffing changes, budget reallocations, policy shifts — use scenarios instead. Scenarios are reproducible, comparable, and versioned; chat-only analysis is not.
Tips for power users
Stack context. If you’ve just asked about one metric, follow-up questions inherit the frame — you don’t need to repeat the time window or the entities. “And how does that compare to the north region?” works.
Use the active time window and filters on the dashboard. Whatever you set in the context bar flows into chat automatically, so “what changed?” is interpreted against the window you’re actually looking at.
Ask it to explain its reasoning. “Why did you pick that dataset?” or “walk me through how you got that number” surfaces the tool calls and source data behind any answer.
Summarize my uploaded documents on the new compliance policy and flag anything that contradicts our current SOPs.
Finally, don’t pre-optimize. Delphi is designed to handle messy, half-formed questions and refine them through conversation. Start somewhere, and iterate.