> 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/how-to-contact-us.md).

# How to contact us?

Or suggest a feature or report any issue with the app

If you want to talk to us, suggest a new feature, or report a bug, we have a simple way to do so.

There are actually many ways of doing this:

1. You can drop us a line by going to the MyWay app setting (top right menu icon) and then the "Report a Problem" or "Talk to Us" menu item.
2. You can go to our public website <https://mywayroute.com> and talk to us via online chat there.
3. You can drop us an email at <support@mywayroute.com>. &#x20;

We usually respond quicker in online chats, but feel free to use any method that works for you. We will be happy to talk.


---

# 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/how-to-contact-us.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.