> For the complete documentation index, see [llms.txt](https://nomadia-docs.gitbook.io/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nomadia-docs.gitbook.io/products/getting-started.md).

# Getting-Started

Create your TourSolver account and learn what you can do with the platform.

## Before you begin

* Use a supported browser. See [Which Browsers and Systems Are Compatible with TourSolver?](https://nomadia-docs.gitbook.io/products/faq/which-browsers-and-systems-are-compatible-with-toursolver.md).
* Have a valid email address to sign up. No installation is needed, because TourSolver is a fully cloud-based solution hosted on Microsoft Azure.

## Feature overview

* **Trial account**: Lets you test the platform immediately, with up to 5 drivers, up to 5 route optimizations per day, and up to 250 deliveries per optimization.
* **Import and Data setup**: Create depots and users, import your deliveries, and modify their addresses.
* **Resource and Vehicle Management**: Create and modify resources, and rename vehicle quantities.
* **Operations and Route Management**: Optimize your deliveries, export your routes, share a tour with the mobile app, and geolocate your delivery people.
* **Simulation**: Manage deliveries and routes, view the map, and analyze the results.
* **Customer Communication**: Configure the messages that you send to your customers.
* **FAQ**: Answers to frequently asked questions.

## Features

* [Signup Process](https://nomadia-docs.gitbook.io/products/getting-started/gettingstarted-signupprocess.md)
* [Log in to TourSolver](https://nomadia-docs.gitbook.io/products/getting-started/log-in-to-toursolver.md)

## Tips

{% hint style="info" %}
**Start with the sample data**: During the onboarding, TourSolver creates five resources and offers sample deliveries that you can import to explore the platform.
{% endhint %}

## Related topics

* [Import and Data setup](https://nomadia-docs.gitbook.io/products/importanddatasetup.md)
* [Resource and Vehicle Management](https://nomadia-docs.gitbook.io/products/resource-and-vehicle-management.md)
* [Operations and Route Management](https://nomadia-docs.gitbook.io/products/operationsandroutemanagement.md)
* [Simulation](https://nomadia-docs.gitbook.io/products/simulation.md)
* [Customer Communication](https://nomadia-docs.gitbook.io/products/customercommunication.md)
* [FAQ](https://nomadia-docs.gitbook.io/products/faq.md)


---

# 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://nomadia-docs.gitbook.io/products/getting-started.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.
