> For the complete documentation index, see [llms.txt](https://kyela-inbox.gitbook.io/kyela-inbox-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kyela-inbox.gitbook.io/kyela-inbox-docs/help.md).

# Get help

Tap **Help** in the bot, or send `/help`, for setup instructions, missing-address checks and help restoring syncing. Help buttons update the current message, so browsing instructions does not fill your chat with extra posts.

## An address is missing

Check these in order:

1. **The group is selected.** Open **Choose groups** on the connection page.
2. **The device is checking.** Look at the last-check time. If checking stopped, [restore syncing](/kyela-inbox-docs/connection.md).
3. **Your alert settings include it.** Check caller filters, quiet hours, digest timing and repeat suppression in the bot.
4. **Your access is active.** Open **My access**.

Kyela recognises supported addresses in text, captions and certain links. Images, voice notes and ticker-only posts are unsupported. Content from before you enabled a group is not automatically imported.

## I do not remember my Telegram password

This is Telegram's two-step verification password, if you enabled one. It is different from the login code Telegram just sent and from your phone's PIN.

Use Telegram's own password-recovery process. Kyela cannot recover it for you. Do not send your password or login code in any bot or support chat.

## The sign-in page seems stuck

If a loading indicator is visible, the page is still working. Keep it open. If it shows a connection error, check your internet and retry when offered. Respect any wait Telegram requests.

If told to reopen, close the connection page and open it again using the bot's button. This does not erase a valid device sign-in or your saved group choices.

## A group is missing from the picker

Check that you used the Telegram account which belongs to that group. Groups with content protection are excluded. A group you joined later still needs to be selected explicitly.

## A button or menu has expired

Open the current menu in the bot and try again. This prevents an old button from overwriting newer settings.

## Ask for help with an address

Open **Help → Support diagnostics** in the bot to review sample access. This controls which diagnostic samples support may inspect; it does not submit a support request. When reporting a problem, include its approximate time, what you expected and what happened. You do not need to provide a Telegram password or login code.

If checking a real address is necessary, select **Allow samples for 15 minutes**. During that window, support can inspect exact addresses in retained cards. Group names, caller names and source links remain masked.

You can stop sample access immediately in the same menu; it also expires automatically. Already-viewed samples may remain in the support chat. This permission does not share your Telegram credentials or session.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://kyela-inbox.gitbook.io/kyela-inbox-docs/help.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 `build a script that syncs our docs to a CMS` 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.