> 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/booking/availability/calendar-start-date.md).

# Calendar Start Date

If you want the storefront calendar to open on a specific date by default, set a **start date** at the service level.

## How to set it

{% stepper %}
{% step %}

#### Go to Sesami → Services

Open the Sesami app and navigate to Services.
{% endstep %}

{% step %}

#### Click the service you want to edit

Select the service whose storefront calendar start date you want to configure.
{% endstep %}

{% step %}

#### Scroll to Storefront calendar start date

Locate the "Storefront calendar start date" field in the service settings.
{% endstep %}

{% step %}

#### Enter the date you want the calendar to start from

Specify the start date you want customers to see by default.
{% endstep %}

{% step %}

#### Save

Save your changes.
{% endstep %}
{% endstepper %}

## What this does

When a customer opens that service page, the calendar will initially show starting from the date you configured.


---

# 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/booking/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.
