> For the complete documentation index, see [llms.txt](https://help.mywayroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mywayroute.com/faq/what-service-time-should-you-choose.md).

# What Service Time should you choose?

Recommendation about the Stop Duration (Service Time) to choose to get the best route optimization results

To get the most accurate route that is very well optimized for your needs, you need to choose service time correctly. As a Service Time may vary, it will change the overall route time and the time you arrive at each stop. The wrong service time has an especially dramatic effect on those stops that have time windows. Service Time (time on a stop) depends on the type of delivery (or business you are in). Please check the recommended service type down below:

| Business                                                             | Recommended Service Time |
| -------------------------------------------------------------------- | ------------------------ |
| Documents Delivery                                                   | 5 minutes                |
| Good Delivery, Delivery from On-line Store (Small Box/Package, etc.) | 10 minutes               |
| Clothe Delivery (If customer wants to try it out)                    | 20 minutes               |
| Delivery of Big Boxes/Packages (Furniture, etc.)                     | 40 minutes               |

Please choose Service Time correctly to make the most of the route optimization. 


---

# 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://help.mywayroute.com/faq/what-service-time-should-you-choose.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.