# L1 checklist

## Problem <a href="#l1checklist-summary" id="l1checklist-summary"></a>

Troubleshooting L1 issues can be time-consuming and inconsistent across devices, leading to extended downtime. Without a standard approach to troubleshooting and a centralized view of key device characteristics, this process can become very engineer-specific.

## Solution

The L1 checklist helps you check for the most common L1 issues with a single device-specific checklist available directly from the [Device View](/platform/user-guide/device-view.md) or [Amplify](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/configure-amplify.md).

## Benefits and outcome

This checklist will:

* Enable L1 agents to quickly perform basic health checks, reducing troubleshooting time.
* Make the troubleshooting process smoother by helping L1 agents avoid switching between multiple IT tools or contacting end users.
* Improve the end-user experience by minimizing user involvement and potential disruption as end-users are less likely to be contacted for basic health checks.

## Getting started with

Configure and start using this library pack by following these links:

* [Usage guide: L1 checklist](/platform/library-packs/l1-support/l1-checklist/usage-guide-l1-checklist.md)
* [Configuration guide: L1 checklist](/platform/library-packs/l1-support/l1-checklist/configuration-guide-l1-checklist.md)


---

# 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.nexthink.com/platform/library-packs/l1-support/l1-checklist.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.