> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/de/benotigen-sie-hilfe/contact-verkada-support/locate-customer-id.md).

# Kunden-ID finden

Suchen Sie Ihre Kunden-ID, um sie mit Verkada-Vertretern zu teilen

{% hint style="danger" %}
Bevor Sie Verkada kontaktieren, benötigen Sie Ihre **Kunden-ID** bereit, Ihrem Ansprechpartner mitzuteilen. Ihre Kunden-ID besteht aus "C", gefolgt von 8 Ziffern; zum Beispiel: C-XXXX-XXXX.
{% endhint %}

## Kontomenü

{% stepper %}
{% step %}
**Melden Sie sich bei Ihrem Verkada-Command-Konto an.**
{% endstep %}

{% step %}
**Wählen Sie unten links Ihren Organisationsnamen aus.**
{% endstep %}

{% step %}
**Ihre Kunden-ID wird oben auf der Seite angezeigt.**
{% endstep %}
{% endstepper %}

## Hilfe-Symbol

{% stepper %}
{% step %}
**Melden Sie sich bei Ihrem Verkada-Command-Konto an.**
{% endstep %}

{% step %}
**Unten links klicken Sie auf das Hilfe-(?) Symbol > Kontaktieren Sie uns.**
{% endstep %}

{% step %}
**Ihre Kunden-ID wird oben im eingeblendeten Pop-up angezeigt.**
{% endstep %}
{% endstepper %}

## Admin-Seite

{% stepper %}
{% step %}
**Gehen Sie in Verkada Command zu Alle Produkte > Admin.**
{% endstep %}

{% step %}
**Klicken Sie in der linken Navigation auf Support.**
{% endstep %}

{% step %}
**Ihre Kunden-ID wird oben auf der Seite angezeigt.**
{% endstep %}
{% endstepper %}


---

# 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.verkada.com/command/de/benotigen-sie-hilfe/contact-verkada-support/locate-customer-id.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.