# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Not hearing Tiledesk push notifications in Google Chrome](https://guide.tiledesk.com/notifications/not-hearing-tiledesk-push-notifications-in-google-chrome.md)
- [How to Connect Your Bot to Slack](https://guide.tiledesk.com/other-integrations/how-to-connect-your-bot-to-slack.md)
- [How to configure push notification in Chrome](https://guide.tiledesk.com/notifications/how-to-configure-push-notification-in-chrome.md)
- [How to Retrieve Data from Make.com to Tiledesk](https://guide.tiledesk.com/other-integrations/how-to-retrieve-data-from-make.com-to-tiledesk.md)
- [Tiledesk Analytics 101](https://guide.tiledesk.com/tiledesk-analytics-101.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://guide.tiledesk.com/notifications/not-hearing-tiledesk-push-notifications-in-google-chrome.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://guide.tiledesk.com/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://guide.tiledesk.com/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., `/notifications/not-hearing-tiledesk-push-notifications-in-google-chrome.md`).

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