# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [[Thao Tác] Gắn Thẻ Flow & Đặt lịch chăm sóc lại](https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/thao-tac-gan-the-flow-and-dat-lich-cham-soc-lai.md)
- [[Tư duy] Tag FLOW chăm sóc khách](https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/tu-duy-tag-flow-cham-soc-khach.md)
- [Đổi tên Zalo khách trên pancake](https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/huong-dan-cho-sale/doi-ten-zalo-khach-tren-pancake.md)
- [Nhập thông tin vào CRM trực tiếp trên Pancake](https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/huong-dan-cho-truc-page/nhap-thong-tin-vao-crm-truc-tiep-tren-pancake.md)
- [[Thao tác] Note ghi chú về việc làm việc với khách](https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/thao-tac-note-ghi-chu-ve-viec-lam-viec-voi-khach.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://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/thao-tac-gan-the-flow-and-dat-lich-cham-soc-lai.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://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://travel-simple-tour.gitbook.io/travel-simple-sales-playbook/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., `/travel-simple-sales-playbook/thao-tac-gan-the-flow-and-dat-lich-cham-soc-lai.md`).

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