Docs
Ask a question
Plain words in. The number, where it came from, and the SQL folded underneath.
Type the question the way you'd ask a person. It reads what it knows about your business first (your words, your definitions, what happened last month), then the data, and answers with the number and the table it came from. The query it ran is folded under the answer if you want it.
If a word in your question could mean two things, it asks. Your answer becomes a definition it keeps, so it never asks that one again.
Things to ask
Which products actually make money after shipping?
How many customers ordered twice this year?
What was net revenue in March, and why is it different from the board deck?
Which invoices over 60 days have nobody called about?
What it can and can't do
- It only reads. Nothing it does can change your data. The two things it can write are a card in your inbox for you to approve, and a clean table it thinks is worth keeping, which shows up under Models where you can edit or delete it.
- It sees what you see. Every answer runs under your own key, so a person who can't read the books can't get the books out of it.
- It shows its work. Every number carries the definition it used and who confirmed it. If the answer looks wrong, the receipt tells you which part to fix.
- Long answers stop at 200 rows. For a full table, open it on the Data screen or ask for a worklist.
When it gets it wrong
Say so, in the same box. "No, net revenue is after refunds." The correction is kept as a fact with your name on it, and every later answer, dashboard and agent reads it.