> For the complete documentation index, see [llms.txt](https://support.doowii.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.doowii.io/getting-started/quickstart.md). # Quickstart Welcome to Doowii! This guide will help you get started with our conversational analytics platform. Below are the key topics to begin your journey:


Introducing Doowii	Review core platform features.	Introducing Doowii	Gitbook CMS Card Cover Image (1).png
Setting Up Your Account	Create and configure your Doowii account.	Setting Up & Managing Your Account	Gitbook CMS Card Cover Image (10).png
Asking Your First Question	Discover insights with natural language questions.	Asking Your First Question	Gitbook CMS Card Cover Image (9).png
Refining and Filtering Answers	Refine your queries for precise information.	Refining and Filtering Answers	Gitbook CMS Card Cover Image (7).png
Creating Charts & Graphs	Visualize your data with charts and graphs.	Broken link	Gitbook CMS Card Cover Image (11).png
Using Pinboards	Save, organize, and share your insights.	Using Pinboards	Gitbook CMS Card Cover Image (13).png
Exploring Available Data	Review integrated data sources.	Exploring Available Data	Gitbook CMS Card Cover Image (14).png

--- # 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://support.doowii.io/getting-started/quickstart.md?ask=&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.