> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Neo Insights
> Analyze your closed tickets to see where your team spends time and how much automation could save — scoped to your whole desk, a single end-client, or specific months.
Neo Insights analyzes your closed tickets and turns them into a projected return on investment from automation: how many hours and how much money you could reclaim, which work to automate first, and how to set it up. Open it from [**Insights**](https://dashboard.neoagent.io/insights) in the dashboard.
Your first report runs automatically once your PSA sync finishes. After that you can run new reports any time — for your whole desk, for a single end-client company, or for specific months — and switch between the reports you've already run without re-running anything.
Insights reads only **closed** tickets that Neo has already processed with AI summaries, so a brand-new tenant sees a report once its first sync and AI processing complete.
## What's in the report
**Executive summary** — the headline: total savings opportunity in hours per year and money per year.
**Top opportunities** — the highest-impact areas Neo found (for example Security Alerts, Ticket Triage & QA, Ticket Dispatch), each with projected annual savings, hours, and the number of tickets it applies to.
**Recommended setup** — the specific agents and workflows to build for those opportunities, and the key tools each one needs, so you can go from insight to automation.
**Savings breakdown** — a chart of where the projected savings come from, by category.
**Analysis details** — the parameters behind the numbers:
| Field | What it means |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Company** | The end-client this report is scoped to, or **All companies** for your whole desk |
| **Analysis period** | The date window the tickets were drawn from |
| **Sample size** | How many tickets were classified to build the projection |
| **Annual ticket volume** | Your total eligible tickets, extrapolated to a year |
| **Region** | The region used to pick a default technician cost |
| **Avg. cost per ticket hour** | Your fully-loaded technician cost (salary, benefits & overhead) that turns saved hours into money — editable inline |
The projection extrapolates from a representative sample of your tickets to your annual volume, so the figures are directional estimates for planning, not exact accounting.
## Switch between saved reports
Every report Neo runs is saved. The **report switcher** in the top-right of the Insights page shows which report you're viewing (its company and time window) and lists every saved report — one per company-and-months combination, with the date it was run. Pick one to open it instantly; nothing is re-run and no analysis is consumed.
## Run a new analysis
Use **New analysis** in the top-right (next to the report switcher) to open the settings and run a fresh report.
Click **New analysis** to open the settings popover.
Pick a single end-client under **Company** to scope the whole report to that customer, or leave it on **All companies** to analyze your entire desk.
Either choose an **Analysis Period** (Last 30 / 90 / 180 / 365 days), or pick one or more **Specific months**. Selecting specific months **overrides** the rolling period.
Confirm the **Cost per Ticket Hour** — your fully-loaded technician cost — so the money figures reflect your team.
Click **Run Analysis**. A run typically takes **2–5 minutes** while Neo classifies your tickets and calculates the projection; the page shows progress and updates automatically when it's done.
Scoping to a single end-client is ideal for a QBR or a per-customer ROI story — the report reads exactly like the desk-wide one, just for that company.
### Choosing months
The month picker lists every month you have ticket history for, newest first, and you can select several at once — including non-consecutive months. Neo analyzes only the tickets from the months you pick and annualizes from what it observed. Choosing months that span a limited part of the year can skew seasonal categories, so the analysis period shown on the report always reflects the exact window that was used.
### When a company doesn't have enough tickets
A meaningful analysis needs at least **30** closed, AI-summarized tickets. When you scope to a company that has fewer than that in your chosen window, Neo automatically **widens the window to all time** for that company and tries again — so smaller clients still get a report where the data allows. If there still aren't enough tickets, Neo shows a clear **"not enough data"** message instead of an unreliable projection; pick a different company or period and try again.
## Good to know
* **Who can run it** — only tenant admins can start a new analysis. Everyone with access can view saved reports.
* **Re-running is safe and cheap** — each run replaces the saved report for that exact scope; running a company or month view never overwrites your whole-desk report.
* **Export** — use **Export PDF** to share the current report outside the dashboard.
## Related
* [Analytics](/product/analytics) — measure live workflow performance and credit consumption once your automations are running.
* [Company mapping](/product/company-mapping) — how Neo recognizes the same end-client company across your connected systems, which is what powers the company filter here.