# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [25.01.09 폼/리드라우터 - 폼 배너](https://recatch.gitbook.io/releasenotes/updates/2025/2025-1/25.01.09-1.md)
- [2026년 3월](https://recatch.gitbook.io/releasenotes/updates/2026-3.md)
- [2026년 1월](https://recatch.gitbook.io/releasenotes/updates/2026-1.md)
- [25.01.09 폼/리드라우터 - 전환율 대시보드](https://recatch.gitbook.io/releasenotes/updates/2025/2025-1/25.01.09.md)
- [10.07 리드 - 벌크 기능](https://recatch.gitbook.io/releasenotes/updates/2024/2024-10/10.07-1.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://recatch.gitbook.io/releasenotes/updates/2025/2025-1/25.01.09-1.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://recatch.gitbook.io/releasenotes/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://recatch.gitbook.io/releasenotes/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., `/releasenotes/updates/2025/2025-1/25.01.09-1.md`).

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