> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/buildertek-ticketing-guide/introduction.md).

# Introduction

#### Purpose of this Guide

To provide end-users with a detailed, step-by-step guide to using BuilderTek's customer-facing ticketing system for initiating and tracking support requests.

#### Scope

This guide strictly covers the frontend ticketing workflow from the customer's perspective. Internal (backend) processing by BuilderTek is outside the scope.

#### Intended Audience

BuilderTek customers, end users, project stakeholders.

#### Prerequisites

* Active BuilderTek account
* Valid login credentials
* Internet access and compatible browser

#### Version Control Statement

This document reflects Version 1.0 of the ticketing process as of \[Insert Date]. Future revisions will be documented in the Appendices.

<br>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.buildertek.com/buildertek-ticketing-guide/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.