> ## Documentation Index
> Fetch the complete documentation index at: https://docs.headlesslabs.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Utilities

> Utilities include help, latency, polls, and reminders. Prefix commands use the server's current prefix.

## Help and diagnostics

`.help` opens the catalog and `.help <category>` opens a category; `/help` provides the slash selector. For example, `.help mod` and `.help snipes` open known sections. `.ping` reports Discord connection latency; it does not diagnose a feature's provider, database, or permissions.

> **Help V2**
>
> Browse categories in the menu and open help links. Use `.help` or `/help`; sections depend on the catalog Headless has registered.

> **Poll**
>
> Create polls with 2 to 9 options. The question allows up to 180 characters and each option up to 80; choose an optional duration from 10 seconds to 7 days.

> **Remind**
>
> Schedule a reminder from 5 seconds to 7 days. Durations accept formats such as `10m`, `2h`, or `1d`; the task stays in process memory.

### `.help`

```headless-command Syntax theme={null}
.help [section]
```

```headless-command Example theme={null}
.help
```

Also works: `.help tickets`

### `/help`

```headless-command Syntax theme={null}
/help [section:<section>]
```

```headless-command Example theme={null}
/help
```

### `.ping`

```headless-command Syntax theme={null}
.ping
```

```headless-command Example theme={null}
.ping
```

### `.say`

```headless-command Syntax theme={null}
.say <message>
```

```headless-command Example theme={null}
.say important notice
```

> [!WARNING]
>
> Do not put personal or sensitive information in a public poll.

## Polls and reminders

`.poll` (`.encuesta` alias) and `/poll` create a poll with 2 to 9 options. The question can contain up to 180 characters and each option up to 80. Prefix input accepts fields separated with `|` or in quotes; `--time` is optional and accepts 10 seconds to 7 days. Without a duration, no automatic close is scheduled; with one, Headless updates the result when it expires.

`.remind <duration> [message]` (`.reminder` and `.rm` aliases) accepts 5 seconds to 7 days; the default message is `Reminder`. Headless confirms the task in-channel, then tries to send a private message (DM) when it is due; if that fails, it posts the notice in the original channel.

> [!NOTE]
>
> Reminders are not persistent: restarting the bot before they are due may prevent delivery. If the DM cannot be sent, Headless posts a notice that mentions the member in the original channel.

`.say <message>` (`.echo` alias) posts text as the bot and requires `Manage Messages` from the caller. Headless tries to delete the invoking message; if Discord blocks that, it may remain visible.

### `.poll`

```headless-command Syntax theme={null}
.poll [payload]
```

```headless-command Example theme={null}
.poll "Event?" "Yes" "No" --time 10m
```

### `.remind`

```headless-command Syntax theme={null}
.remind <duration> [message=Reminder]
```

```headless-command Example theme={null}
.remind 10m review logs
```

## Check server invites

`/invites list` lists up to 20 active invites, sorted by use count, with each code, use count, creator, and channel. `/invites info code:<code>` shows those details, the maximum uses, expiration, and whether the invite is temporary. These commands only query active invites; they do not create or edit invites. If a code is no longer active, the command reports that it was not found.

Discord marks both commands with `Manage Server` as the caller's default permission. Headless also needs `Manage Server` to query server invites; if Discord rejects the request, the command returns an error instead of a partial list.

```headless-command Syntax theme={null}
/invites list
```

```headless-command Example theme={null}
/invites list
```

```headless-command Syntax theme={null}
/invites info code:<code>
```

```headless-command Example theme={null}
/invites info
```

## Setup help

Utilities do not replace module configuration guides: review permissions and risks before running setup or moderation actions.

## Steps

**1. Find a command**

Use `.help` or a category and confirm syntax in the linked guide.

**2. Try a simple example**

Use a short question or a non-sensitive reminder.

**3. Check delivery**

Verify the bot response and, for reminders, that the DM can be received.

## Related pages

* [Getting Started](/docs/en/getting-started.md)
* [Permissions](/docs/en/permissions.md)
* [Tickets](/docs/en/server/tickets.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.