Ana asked me a clarifying question. What do I do?
Ana asked me a clarifying question. What do I do?
Just answer it in plain English. This is Ana being careful instead of guessing — pick the meaning you intended (“invoiced revenue”) and she’ll continue.
The answer doesn't match a number I've seen elsewhere.
The answer doesn't match a number I've seen elsewhere.
This is usually a definition difference, not an error — calendar vs. fiscal quarter, gross vs. net, test accounts in or out. Run the Module 2.3 reconciliation: “Why might your number differ from [the other report]?” If they truly conflict, propose the right definition as a patch (Module 6.1) — finding these is valuable.
Ana says she doesn't have the data I asked about.
Ana says she doesn't have the data I asked about.
The data source may not be connected yet, or it wasn’t attached to this thread (Module 0.2), or you may not have access. Note exactly what you asked and send it to your data team — requests like this drive what gets connected next.
Will it make numbers up?
Will it make numbers up?
Every number is auditable — that’s the protection. Ana is designed to report missing data as missing (you tested this in Module 1.4), and when something looks off, you have the verification moves from Module 2: “How did you calculate that?”, check the definition, challenge the result. Trust the audit trail, not blind faith — that’s true of any analyst, human or AI.
My question is taking a while.
My question is taking a while.
Bigger questions (long time ranges, many breakdowns) take longer — Ana narrates what she’s doing in the meantime. For a faster first pass, narrow the time window and broaden later.
Can it replace our BI dashboards?
Can it replace our BI dashboards?
It can build and refresh dashboards (Module 4) — and answer the questions dashboards can’t (Module 3).
Who do I contact for help?
Who do I contact for help?
Your workspace administrator for access issues; your TextQL team for anything else. In a guided session, just ask your facilitator.