# Page Not Found

The URL `bepay_vn/tong-quan/doi-ngu-co-van` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [1. Ngôn ngữ cơ thể đúng](https://bepos.gitbook.io/so-tay-sale-bepos/iv.-gi-i-hon-va-ban-duoc-nhieu-hon/1.-ngon-ngu-co-the-dung.md)
- [7. Chốt đơn hàng](https://bepos.gitbook.io/so-tay-sale-bepos/iv.-gi-i-hon-va-ban-duoc-nhieu-hon/7.-chot-don-hang.md)
- [9. Quản lý thời gian](https://bepos.gitbook.io/so-tay-sale-bepos/iv.-gi-i-hon-va-ban-duoc-nhieu-hon/9.-quan-ly-thoi-gian.md)
- [2. Dịch vụ cung cấp](https://bepos.gitbook.io/so-tay-sale-bepos/ii.-san-pham-dich-vu-va-quy-trinh/2.-dich-vu-cung-cap.md)
- [14. Quy trình vận hành](https://bepos.gitbook.io/so-tay-sale-bepos/x.-tai-nguyen/14.-quy-trinh-van-hanh.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://bepos.gitbook.io/so-tay-sale-bepos/iv.-gi-i-hon-va-ban-duoc-nhieu-hon/1.-ngon-ngu-co-the-dung.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://bepos.gitbook.io/so-tay-sale-bepos/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://bepos.gitbook.io/so-tay-sale-bepos/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., `/so-tay-sale-bepos/iv.-gi-i-hon-va-ban-duoc-nhieu-hon/1.-ngon-ngu-co-the-dung.md`).

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