> For the complete documentation index, see [llms.txt](https://help.bloomsharing.com/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bloomsharing.com/doc/the-bloom-dashboard/service-alerts.md).

# Service alerts

## User reported issues

You can view issues submitted by users via the Report function on the User App. The report includes the location of the user at the time of the submission. Service alerts are also sent by email to the administrator.

## Asset alarms

Depending on the functionalities of the mobility asset, it may automatically report activity based on improper usage or parking.  This activity will be displayed here.

## Open locks

If locking mechanisms that are open for greater than 24 hrs are detected by the System, they are listed here. Using this tool can help you detect and locate mobility assets that may have been inadvertently left open.


---

# 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://help.bloomsharing.com/doc/the-bloom-dashboard/service-alerts.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.