# Use Cases

Common ways teams use Screendesk Bug Reports in QA, support, and product workflows.

Pick the scenario closest to yours.

<table data-view="cards"><thead><tr><th>Use case</th><th>Jump to</th></tr></thead><tbody><tr><td>Capture bugs during manual QA. Share one link with full context.</td><td><a href="#id-1-manual-exploratory-testing">Manual &#x26; exploratory testing</a></td></tr><tr><td>Let users report issues from inside your app. Cut support back-and-forth.</td><td><a href="#id-2-end-user-bug-reporting">End user bug reporting</a></td></tr><tr><td>Let clients report bugs on their own machine. Great for agencies.</td><td><a href="#id-3-client-bug-reporting-solution">Client bug reporting solution</a></td></tr><tr><td>Turn monitoring alerts into clear repros. Add richer debugging data.</td><td><a href="#id-4-expand-on-monitoring-errors">Expand on monitoring errors</a></td></tr><tr><td>Hand off manual flows to automation. Start E2E scripts faster.</td><td><a href="#id-5-e2e-testing-handover">E2E testing handover</a></td></tr><tr><td>Capture “what just happened”. Save the last minutes without redoing the bug.</td><td><a href="#id-6-individual-monitoring">Individual monitoring</a></td></tr></tbody></table>

### Manual & exploratory testing <a href="#id-1-manual-exploratory-testing" id="id-1-manual-exploratory-testing"></a>

Use this during manual QA and exploratory testing.

Capture issues once. Share one link with the exact repro steps.

* Capture with [Screenshot](/bug-reports/capturing-a-bug-report/screenshot.md), [Video Screen Recording](/bug-reports/capturing-a-bug-report/video-screen-recording.md), or [Instant Replay](/bug-reports/capturing-a-bug-report/instant-replay.md).
* Include the debugging context engineers need. This includes logs and requests.

### End user bug reporting <a href="#id-2-end-user-bug-reporting" id="id-2-end-user-bug-reporting"></a>

Use this when customers hit bugs in production.

Use the [screen recording links](/bug-reports/capturing-a-bug-report/recording-links.md). Users can submit reports in-context.

* Reduce support back-and-forth. Get a repro instead of long threads.
* Capture technical context automatically. Engineers debug faster.
* Works well with helpdesks like [Intercom](/bug-reports/customer-support-integrations/intercom.md) and [Zendesk](/bug-reports/customer-support-integrations/zendesk.md).

### Client bug reporting solution <a href="#id-3-client-bug-reporting-solution" id="id-3-client-bug-reporting-solution"></a>

Use this if you build products for clients.

Install the Screendesk extension on the client’s browser. They can report issues themselves.

* Get better bug reports without chasing screenshots and logs.
* Works well for environment-specific and permission-specific bugs.
* See [Browser support](/bug-reports/getting-started/browser-support.md) for supported browsers.

### Expand on monitoring errors <a href="#id-4-expand-on-monitoring-errors" id="id-4-expand-on-monitoring-errors"></a>

Use this when monitoring catches exceptions, but repro is unclear.

Screendesk complements tools like Sentry, Rollbar, and Datadog.

* Turn an alert into a reproducible flow.
* Capture what happened plus logs, requests, and environment details.
* Verify the fix with a new capture.

### E2E testing handover <a href="#id-5-e2e-testing-handover" id="id-5-e2e-testing-handover"></a>

Use this to hand off manual test flows to automation.

Record the flow once. Hand it to an automation engineer.

* Share the exact steps and expected behavior.
* Reduce ambiguity around timing and navigation.
* Use the E2E helper to generate a starter test template.

### Individual monitoring <a href="#id-6-individual-monitoring" id="id-6-individual-monitoring"></a>

Use this for “it just happened” bugs.

Enable [Instant Replay](/bug-reports/capturing-a-bug-report/instant-replay.md) to keep a rolling buffer.

* Capture the last \~2 minutes without redoing the repro.
* Great for flaky UI, timing issues, and intermittent errors.
* Nothing uploads until you click **Save**.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.screendesk.io/bug-reports/getting-started/use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.