> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/debug-with-ai/ai-summary.md).

# Report intelligence

Use AI summaries, issue findings, and reproduction steps to understand recordings and reports faster.

Report intelligence analyzes the evidence in a recording or report and turns it into a summary and useful investigation context.

It can use visual content and captured technical evidence as well as spoken context. A recording does not need speech to contain useful evidence.

## What you get

Depending on the report and the available evidence, analysis can include:

* A summary of what happened.
* Issue findings, observed behavior, and relevant context.
* Reproduction steps and useful moments to review.
* Technical findings supported by captured browser or network evidence.

Some reports do not contain enough evidence for every section. A missing reproduction sequence should not be treated as proof that no issue occurred.

## Enable automatic analysis

Go to **Settings → AI & Intelligence** and enable **AI processing** and **Report intelligence**.

The feature must be available for your workspace. It applies to eligible new content; switching it on does not automatically reanalyze all historical reports.

See [AI settings](/debug-with-ai/ai-settings.md).

## Review an analyzed report

1. Open the recording or report in Screendesk.
2. Read the summary and available analysis.
3. Review the reproduction steps and the moments or evidence they refer to.
4. Check the original recording, screenshot, or logs before deciding on a fix.

Use [AI transcripts](/debug-with-ai/ai-transcripts.md) when you need the spoken wording or want to search for a phrase.

## Different inputs provide different evidence

| Input                                 | What the analysis can use                                                                 |
| ------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Screen recording or capture video** | Recorded visual content and available audio or technical context                          |
| **Screenshot**                        | The captured image and available report context                                           |
| **Instant replay**                    | Captured actions, navigation, console and network metadata, and other supported telemetry |
| **Recorded video call**               | Eligible recording analysis and, where enabled, transcription and conversation recap      |

Instant replay intelligence is telemetry-based. It does not visually inspect replay DOM snapshots, page HTML, input values, or network bodies. Treat its findings as analysis of captured events, not visual confirmation of what appeared on screen.

Recorded-call features depend on workspace settings, feature availability, and recording consent.

## How it relates to AI Resolution

Report intelligence describes the evidence in the report. [AI Resolution](/debug-with-ai/ai-resolution.md) adds the current Zendesk ticket, trusted documentation, and workspace guidance to investigate a next step.

A completed report analysis does not mean a customer reply has been sent or a ticket has been resolved.

## If analysis is missing

Check that processing and report intelligence are enabled and available for the workspace, and that the report has finished processing. Processing time varies with the content and recording length.

A silent recording can still have visual analysis, but it will not have a spoken transcript. If processing has failed or remains incomplete, share the report URL with Screendesk support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/debug-with-ai/ai-summary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.