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

# Qualify requests before they're created

Set up the Qualification playbook so the AI IT Agent asks employees clarifying questions, for equipment, VPN or software issues, before it creates a complete request

### About this Playbook

Some requests need more context before the IT team can start working.\
The **Qualification** playbook lets the AI Agent ask employees targeted questions before creating the request — ensuring it contains the right details from the start.

### When to Use It

Use this playbook for cases such as:

* **Equipment issues** (broken, lost, or stolen)
* **VPN or access problems** (new access, password reset, connection failure)
* **Software malfunction** (type of error, frequency, device)

### How It Works

1. The employee initiates a message in Siit or Slack.
2. The AI Agent detects that more information is needed.
3. It asks one or several **clarifying questions** (e.g., “Is the device broken, lost, or stolen?”).
4. Once it has all the necessary context, it **creates the request** with those details pre-filled.

### Why It’s Useful

* IT agents no longer chase missing details.
* Tickets are ready to resolve upon creation.
* Employees experience a smoother interaction — no back-and-forth later.

### Example in Action

> Employee: “I lost my laptop.”
>
> AI Agent → “Thanks. Can you confirm which device was lost?”
>
> Employee: “MacBook Air 2023.”
>
> AI Agent → Creates request *Lost equipment report*, adds device info, and routes it to the correct service.

✅ **Result:** Requests arrive complete, enabling IT teams to act immediately.


---

# 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.siit.io/guides/ai/ai-agent-request-qualification.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.