Start with what you are trying to do.
You should not have to study a BI tool before you can answer a business question. These docs explain what Overscore can do and when each capability is useful. Your agent can handle the buttons, commands, and implementation.
How to use these docs
Learn enough to recognize the kind of problem you have. Then describe the outcome in plain language. Your agent can recommend the right approach, build it, and bring the result back for review.
Start with the outcome
You do not need to arrive knowing the feature name. Describe the problem. Overscore and its agent guidance should recognize the pattern, recommend the right capability, and explain why it fits.
Keep an answer current
Build a dashboard
Use a dashboard for a question people will ask repeatedly: sales performance, inventory, retention, or operating health.
Build a dashboard that tracks pipeline coverage by rep and refreshes every morning.
Answer a question once
Run an analysis
Use an analysis for an investigation with a durable answer: why churn moved, whether data ties out, or what happened in a campaign.
Investigate why enterprise churn increased last quarter and publish the findings.
Know when something changes
Create an alert
Use an alert when the important outcome is a state change, not another screen someone has to remember to check.
Alert me if rolling six-hour cost per lead rises above $45, but only after enough spend.
Deliver an update automatically
Create an email report
Use a report for a recurring narrative update with numbers and charts. Your agent can prepare and test it. A person starts the send.
Draft a Monday morning pipeline report for the sales leadership team and send a test only to me.
Show each person only their rows
Use viewer scoping
Map each viewer to warehouse identifiers and bind those values as typed SQL parameters. One dashboard can safely serve every rep or customer.
Scope this dashboard so each sales rep sees only their opportunities, then verify it as Jason.
Make future work smarter
Save project knowledge
Store definitions, join rules, source-system quirks, and business context once so every future dashboard and analysis starts informed.
Save what we learned about recognized revenue and use it in every future artifact for this project.
Dashboards and analyses are different tools
A question you ask forever
Dashboard
A live application with registered queries, refresh behavior, access controls, and a stable URL. Use it when the answer needs to remain current.
A question you ask once
Analysis
A durable investigation with the findings and SQL preserved. Use it when you need to answer something, share the conclusion, and move on.
How to work with an agent
Describe the problem
Use business language. Say who needs the answer, how often, and what decision it supports.
Review the approach
The agent should name the capability, explain the plan, identify the data, and surface assumptions.
Approve the consequence
Review before work goes live, sends recurring email, changes access, or performs a destructive action.
An agent can prepare, test, and preview consequential changes. Billing, ownership, account deletion, and other irreversible actions remain human-controlled by design.