# Page Not Found

The URL `bepay-support-vi/belending/cach-ket-noi-vi-tren-belending-cua-bepay` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [5. Các Kênh tương tác của bePOS](https://bepos.gitbook.io/so-tay-sale-bepos/x.-tai-nguyen/5.-cac-kenh-tuong-tac-cua-bepos.md)
- [8. Cách theo đuổi Khách hàng chuyên nghiệp và mất ít công sức nhất](https://bepos.gitbook.io/so-tay-sale-bepos/iii.-phan-loai-khach-hang-va-kich-ban-sale/8.-cach-theo-duoi-khach-hang-chuyen-nghiep-va-mat-it-cong-suc-nhat.md)
- [3. Khách hàng của bePOS](https://bepos.gitbook.io/so-tay-sale-bepos/x.-tai-nguyen/3.-khach-hang-cua-bepos.md)
- [3. Khuyến khích KH kể chuyện của họ](https://bepos.gitbook.io/so-tay-sale-bepos/ix.-cach-ke-chuyen-khi-ban-hang-hieu-qua-hon-vui-hon/3.-khuyen-khich-kh-ke-chuyen-cua-ho.md)
- [7. Tại sao Khách sẽ từ chối 7 lần trước khi mua hàng](https://bepos.gitbook.io/so-tay-sale-bepos/iii.-phan-loai-khach-hang-va-kich-ban-sale/7.-tai-sao-khach-se-tu-choi-7-lan-truoc-khi-mua-hang.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/x.-tai-nguyen/5.-cac-kenh-tuong-tac-cua-bepos.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/x.-tai-nguyen/5.-cac-kenh-tuong-tac-cua-bepos.md`).

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