> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/contact-us/contact-us.md).

# Contact Us

We welcome engagement from business leaders, public sector organisations, technology providers, academia, and practitioners who are shaping the digital future of their organisations and communities.

Whether you would like to share your transformation journey, explore a collaboration, or learn more about our work, please contact us at <digitaltx@itu.int>. We look forward to hearing from you.

### Watch and Learn

To support those driving change on the ground, our YouTube channel offers hands-on, step-by-step videos that build practical skills for digital transformation.

We invite you to follow along at your own pace, apply what you learn in your own context, and subscribe: [@ITU\_digitaltransformation](https://www.youtube.com/@ITU_digitaltransformation)


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/contact-us/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.