# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Managing Your Tasks Tab](https://software-help-docs.gitbook.io/knowledge-base/software-guide/contacts/managing-your-tasks-tab.md)
- [Phone](https://software-help-docs.gitbook.io/knowledge-base/software-guide/phone.md)
- [Workflows](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows.md)
- [Loop Lockouts in Workflows](https://software-help-docs.gitbook.io/knowledge-base/software-guide/troubleshooting/loop-lockouts-in-workflows.md)
- [How to Create and Use Workflows](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/how-to-create-and-use-workflows.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://software-help-docs.gitbook.io/knowledge-base/software-guide/contacts/managing-your-tasks-tab.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://software-help-docs.gitbook.io/knowledge-base/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://software-help-docs.gitbook.io/knowledge-base/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., `/knowledge-base/software-guide/contacts/managing-your-tasks-tab.md`).

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