> 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/help-center-live-nl/boeking/availability/calendar-start-date.md).

# Startdatum van de agenda

Als je wilt dat de winkelpagina-kalender standaard op een specifieke datum opent, stel dan een **startdatum** in op serviceniveau.

## Hoe stel je het in

{% stepper %}
{% step %}

#### Ga naar Sesami → Services

Open de Sesami-app en ga naar Services.
{% endstep %}

{% step %}

#### Klik op de service die je wilt bewerken

Selecteer de service waarvan je de startdatum van de winkelpagina-kalender wilt instellen.
{% endstep %}

{% step %}

#### Scroll naar Startdatum van de winkelpagina-kalender

Zoek het veld 'Startdatum van de winkelpagina-kalender' in de service-instellingen.
{% endstep %}

{% step %}

#### Voer de datum in waarop je wilt dat de kalender begint

Geef de startdatum op die klanten standaard moeten zien.
{% endstep %}

{% step %}

#### Opslaan

Sla je wijzigingen op.
{% endstep %}
{% endstepper %}

## Wat dit doet

Wanneer een klant die servicepagina opent, toont de kalender aanvankelijk de door jou ingestelde datum.


---

# 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/help-center-live-nl/boeking/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.