> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/customer-support/user-reports-issue.md).
# Reporting a Problem
This page tells you how a user reports a problem using the Movatic app
Here's how you can locate the reported problems of specific users: Navigate to the [User Details](/admin-site/users/user-details.md) section. Look for **Reported Problems** under the **User Memberships** section. This will show you a list of issues reported by a particular user, if any.
Reported Problems Section
These are the steps on how a user can report a problem via the app:
1. Open the app and click on the 3 lines on the upper left side of the screen. Select **Report Problem > Choose a system** where you want to report an issue with.
Below you will see an example of how a user will see this on the app.
Note: The systems on the right will only show the list of the systems that the user has interacted with --- this is not the full list of Movatic systems.
2\. This will redirect them to a page where it will prompt the user to describe the problem in detail inside the text box provided.
3\. Once they click **Submit**, the ticket will be sent to the [**Support Tickets**](https://documentation.movatic.co/admin-site/customer-support) page on admin.
Support Tickets on Admin view
Sample Support Ticket
## Other ways to Report a Problem
Alternatively, a user can also report a problem on **Rental History** or under the **Station Information.**
In **Rental History >** Select the specific rental they have encountered an issue with and click on **Report Problem** below.
In **Station Information:** on the map, click the station's pin > click **Report Problem.**
---
# 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://documentation.movatic.co/admin-site/customer-support/user-reports-issue.md?ask=&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.
