Queries about your data
Proposal chat does not query business records. Asking “how much have I invoiced?” does not turn its response into a read of your invoices. Lack of access does not prove there are no invoices, clients or expenses.
Choose the source of the answer
| Need | Where to work |
|---|---|
| Review an invoice or expense | Open the record in its application module. |
| Obtain a report | Use the report center and review its filters. |
| Query data through an agent | Use a tool advertised by your MCP connection or an API endpoint. |
| Prepare a question or interpret data you supply | Use chat, clearly identifying the information you provided. Do not assume an automatic query. |
Insights and anomaly analysis are a separate application surface, described in the insights guide. Their existence does not enable queries in chat.
Define the question before querying
Specify workspace, period, currency and the statuses to include. Distinguish issued documents, drafts, recorded payments and bank transactions: they are not the same measure.
For example, “invoices issued between two dates” and “money collected between those dates” require different criteria. Do not sum different currencies without an explicit conversion method.
Review a connected agent's query
Check that the operation is read-only and uses the authorized workspace. Review filters, pagination and response scope. One page of results does not prove the entire dataset was read.
Ask the agent to separate retrieved data, calculations and assumptions. If the query fails or authorization is missing, the result is unavailable, not “zero”, “no issues” or “all paid”.
What chat can contribute
A useful request is: “Help me identify the columns needed to compare invoicing and collections; do not assume you have my data.” Review the method before retrieving records through the appropriate channel.
Do not confuse an illustrative table with a queried report. Forecasts should identify their assumptions even when based on real data.
Next step: Exports and files.