> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/mssgtrack/user-and-server.md).

# User & Server

## User Tracking

Every time a user sends a message, it is tracked and counted \
You can view a user's messages and the time of last sent message using the `/messages view` command and selecting a user, this will then show you this message

<figure><img src="/files/q3jzlPh430AMWxMMEk2Y" alt="" width="563"><figcaption><p>User Message Tracking Embed</p></figcaption></figure>

## Server Tracking

Similar anytime any user sends a message it is tracked and counted towards the server's message count.

You can view the server's total message count and last sent message timestamp with `/messages view` and NOT selecting a user, doing so will give you the below message

<figure><img src="/files/UEgbJIPGoekrOtirCHID" alt="" width="563"><figcaption><p>Server Message Tracking Embed</p></figcaption></figure>

## Manage Message Tracking

For server specific configuration you can use this command /messages config and you can do two operations with it.&#x20;

**Reset Count:** This will reset the server's message count, if you do this on accident we can reinstate it if you are TicketsPRO and open a ticket, however this is the only operation that can be undone with manual intervention, no other operation in Message Tracking can be done, so proceed with caution

**Reset All User Counts:** This will reset every user's count on your server, you cannot undo this.


---

# 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://invomagic.gitbook.io/ticketsdocs/mssgtrack/user-and-server.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.