# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Handing over the shift](https://xyes-com.gitbook.io/xyes-cs-guideline/best-practices/handing-over-the-shift.md)
- [General Site](https://xyes-com.gitbook.io/xyes-cs-guideline/categorizing-queries/general-site.md)
- [Useful Phrases and Questions](https://xyes-com.gitbook.io/xyes-cs-guideline/identifying-concerns/useful-phrases-and-questions.md)
- [Chargebacks (Under review)](https://xyes-com.gitbook.io/xyes-cs-guideline/categorizing-queries/fraud-security-related-issues/chargebacks-under-review.md)
- [Internal Communication & Escalations](https://xyes-com.gitbook.io/xyes-cs-guideline/best-practices/internal-communication-and-escalations.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://xyes-com.gitbook.io/xyes-cs-guideline/best-practices/handing-over-the-shift.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://xyes-com.gitbook.io/xyes-cs-guideline/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://xyes-com.gitbook.io/xyes-cs-guideline/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., `/xyes-cs-guideline/best-practices/handing-over-the-shift.md`).

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