# Page Not Found

The URL `files/awNAj5c4WDpcKJB9FxkK` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Вебинарная воронка для школы фейс пластики](https://cases.salebot.pro/vebinarnaya-voronka-dlya-shkoly-feis-plastiki.md)
- [Бот магазина-ателье "Домашний текстиль"](https://cases.salebot.pro/keisy-po-sozdaniyu-chat-botov-i-avtomatizacii/bot-magazina-atele-domashnii-tekstil.md)
- [Кейс салона красоты Марии Никитиной](https://cases.salebot.pro/keis-salona-krasoty-marii-nikitinoi.md)
- [SaleBot: Чат-бот для вступления в Закрытый Клуб в ВК](https://cases.salebot.pro/keisy-po-sozdaniyu-chat-botov-i-avtomatizacii/salebot-chat-bot-dlya-vstupleniya-v-zakrytyi-klub-v-vk.md)
- [Виртуальный менеджер для фитнес-клубов «Metrofitness»](https://cases.salebot.pro/virtualnyi-menedzher-dlya-fitnes-klubov-metrofitness.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://cases.salebot.pro/vebinarnaya-voronka-dlya-shkoly-feis-plastiki.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://cases.salebot.pro/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://cases.salebot.pro/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/vebinarnaya-voronka-dlya-shkoly-feis-plastiki.md`).

You may also use `Accept: text/markdown` header for content negotiation.