> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/support/contact-info.md).

# Contact info

All methods to get in touch with us

The Contact info page provides you with all methods to contact us for questions and in case of an incident.

1. Click on **Contact info** in the menu to see all options to get in touch with us
2. We will always be there to help you, contact us if you have any questions
3. Support methods avaible for Modular and Tailored subscriptions

{% hint style="info" %}
Best method in case of a high priority issue for Modular and Tailored subscriptions is to first create a **support ticket** and then **call** us to discuss the impact and help us to start the investigation as soon as possible.
{% endhint %}

{% hint style="info" %}
The options shown differ based on the subscription type.
{% endhint %}

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2FOxsVRESmfOHlIZ1lVWDu%2Fsupport%20contact_211024.png?alt=media&amp;token=f812af10-2181-4130-8cd2-5a5a50fe414f" alt=""><figcaption><p>Contact info</p></figcaption></figure>


---

# 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://docs.kpnthings.com/kpn-things/the-portal-explained/support/contact-info.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.