> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/shared-mobility-portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/shared-mobility-portal/provider-or-my-service-requests.md).

# Provider | My Service Requests

### Steps to Access Service Requests

#### **1. Log into** [**Shared Mobility Portal**](https://atd.knack.com/smrt#home)

Use your credentials to log in

#### 2. Navigate to the Account Details

Go to the "Account Details" tab

#### 3. View your Service Request

Click on "[My Service Requests](https://atd.knack.com/smrt#my-service-requests/)" to view all Service Requests assigned to your account.

### Understanding the My Assigned Service Request Page

This page is specifically designed for providers and displays the status of Service Requests in three categories:

* **New:** Recently submitted Service Requests that have not yet been addressed
* **In Progress:** Service Requests currently being worked on. The status changes to "In Progress" when an activity, such as "Investigate Site," has been added
* **Close (Resolved):** Service Requests that have been completed. The status changes to "Closed (Resolved)" when activities like "Close Issue (Resolved)" or "Impound Device" have been recorded.


---

# 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://atd-dts.gitbook.io/shared-mobility-portal/provider-or-my-service-requests.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.