Skip to main content
When you ask the AI Analyst to summarize findings or give a recommendation after running an analysis, it uses Summary or Opinion mode — responding directly from thread context without running new SQL.

​
When This Workflow Is Used

This workflow handles follow-up requests — questions that refer to results already in the thread rather than asking for new data.

​
Summary triggers

Summarize the findings
Summarize this for leadership
Summarize that in three bullets
Rewrite that in plain English
Explain the key takeaways
Write that as a haiku

​
Opinion triggers

What should we do next?
What is your recommendation?
What would you focus on?
What's the highest-leverage action here?
What does this mean for our strategy?
These requests share key characteristics:
  • They refer to prior results in the same thread, not new data
  • They ask what the data means or what to do, not for fresh computation
  • They do not require running a new SQL query
Summary and Opinion requests require prior analysis in the same thread. If no analysis has been run yet, the AI Analyst will ask you to run one first.

​
How It Works

1

Classify Intent

The AI detects summary or opinion language and checks for prior analysis context in the thread.
2

Load Thread Context

The AI retrieves the retained analysis context from the current thread — results, findings, and prior SQL outputs.
3

Generate Response

The AI synthesizes a summary or recommendation directly from thread context. No SQL is executed.
If the classifier is not confident enough that this is a summary or opinion request, it falls back to Standard Analysis and runs fresh SQL instead.

​
What You’ll See

Summary and Opinion responses are fast — no SQL runs, so there’s no table identification or query execution step.
ComponentDescription
ResponsePlain text summary or recommendation grounded in thread context
Suggested promptsThree follow-up questions to continue the analysis
Summary and Opinion responses do not include SQL, CSV, or charts.

​
Summary vs. Opinion

SummaryOpinion
What it doesReports what was foundRecommends what to do
Trigger”Summarize”, “rewrite”, “explain the takeaway""What should we do?”, “What’s your recommendation?”
Output styleFactual recap of findingsJudgment-based guidance
You can get both in one request: “Summarize the findings and tell me what to do next.” The AI will summarize and add recommendations.

​
Tips for Best Results

Summary and Opinion need prior results to work from. Ask your data question first, then ask for a summary or recommendation in the same thread.
Thread context does not carry across threads. Ask follow-ups in the same thread where the analysis ran.
In Slack channels, include @SourceMedium in your follow-up: @SourceMedium summarize that for leadership. In DMs, you can reply naturally without a mention.
“Summarize in three bullets” or “give me a one-sentence takeaway” shapes the output. Generic requests like “summarize” also work but may return a longer response.
Summary and Opinion use retained context, not live data. If the thread is old or you need updated numbers, run a new analysis first.

​
Limitations

  • Requires prior context — If no analysis has run in the thread, the AI will ask you to run one first
  • No fresh SQL — These responses use retained thread context only; they do not re-query BigQuery
  • No charts or CSV — Output is plain text only
  • Context depth — Very long threads may not retain every detail; the AI works from a condensed summary of prior results
  • Confidence threshold — Low-confidence summary or opinion classifications are rerouted to Standard Analysis, which runs fresh SQL instead

Standard Analysis

How specific metric questions are handled with fresh SQL.

Deep Analysis

How open-ended strategic questions trigger multi-perspective analysis.

Thread continuity and follow-ups

Learn how thread context works in DMs vs channels, and when to start a new thread.