# Page Not Found

The URL `francais/sms-et-code` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Les méthodes de diffusion de vos visites :SMS,  sur Guideo, au guichet , billet électronique , etc..](https://and-you.gitbook.io/guideo-customer-info/francais/diffusion-des-visites/sms-et-code.md)
- [Gestion des langues](https://and-you.gitbook.io/guideo-customer-info/francais/gestion-des-langues.md)
- [Avant de commencer !](https://and-you.gitbook.io/guideo-customer-info/francais/documentation-guideo.md)
- [Monétisation et paiements](https://and-you.gitbook.io/guideo-customer-info/francais/monetisation-et-paiements.md)
- [Rattacher des visites](https://and-you.gitbook.io/guideo-customer-info/francais/vendre-des-visites.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://and-you.gitbook.io/guideo-customer-info/francais/diffusion-des-visites/sms-et-code.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://and-you.gitbook.io/guideo-customer-info/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://and-you.gitbook.io/guideo-customer-info/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., `/guideo-customer-info/francais/diffusion-des-visites/sms-et-code.md`).

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