> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/de/buchung/availability/calendar-start-date.md).

# Startdatum des Kalenders

Wenn Sie möchten, dass der Storefront-Kalender standardmäßig an einem bestimmten Datum geöffnet wird, legen Sie ein **Startdatum** auf Serviceebene fest.

## So richten Sie es ein

{% stepper %}
{% step %}

#### Gehen Sie zu Sesami → Services

Öffnen Sie die Sesami-App und navigieren Sie zu Services.
{% endstep %}

{% step %}

#### Klicken Sie auf den Service, den Sie bearbeiten möchten

Wählen Sie den Service aus, dessen Startdatum des Storefront-Kalenders Sie konfigurieren möchten.
{% endstep %}

{% step %}

#### Scrollen Sie zu Startdatum des Storefront-Kalenders

Suchen Sie das Feld „Startdatum des Storefront-Kalenders“ in den Serviceeinstellungen.
{% endstep %}

{% step %}

#### Geben Sie das Datum ein, ab dem der Kalender beginnen soll

Geben Sie das Startdatum an, das Kunden standardmäßig sehen sollen.
{% endstep %}

{% step %}

#### Speichern

Speichern Sie Ihre Änderungen.
{% endstep %}
{% endstepper %}

## Was dies bewirkt

Wenn ein Kunde diese Serviceseite öffnet, wird der Kalender zunächst ab dem von Ihnen konfigurierten Datum angezeigt.


---

# 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.sesami.co/de/buchung/availability/calendar-start-date.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.