AIOInsights (⌘I) used to be strongest on analytics questions. It now spans the full spine: work and releases, insights and support conversations, bookings, experiments, revenue, and the customer 360.
How an answer is built
Your question is classified, a deterministic reader pulls the matching records, and only then does a model narrate the result — with citations back to your data. Simple factual questions (counts, sums, lookups) skip the model entirely: no token cost, no chance of an invented number.
Routing that respects your bill
Light questions run on a fast, inexpensive model; only genuinely hard synthesis escalates. You shouldn't pay reasoning-model prices to ask how many open bugs a customer has.
Ask it things that used to take three tabs: "what did Acme's users hit last week, and did anyone follow up?" — one question, one cited answer.