> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/get-started/what-can-i-use-guideflow-for.md).

# What can I use Guideflow for?

Guideflows can be used for various use cases. Here is a quick overview of what you can use Guideflow for:

* **Sales:** As an interactive sales material to send inside, cold outreach campaigns, follow-ups, or during live demos.
* **Marketing**: As an interactive product tour that you can embed in your website to increase conversions and collect leads information.
* **Customer Success**: As onboarding content to guide new users into using your solution, and reduce the workload for CSM teams.
* **Customer Support**: As a guiding material to embed inside help center articles or to share with users to guide them through complex workflows on your solution.
* **Employee training/onboarding:** As a training material for internal use that you can insert in your company's knowledge base (to show how to use software like Salesforce with the company processes).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guideflow.com/help/get-started/what-can-i-use-guideflow-for.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.