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

# Data de início do calendário

Se quiser que o calendário da loja abra por padrão numa data específica, defina uma **data de início** ao nível do serviço.

## Como configurá-lo

{% stepper %}
{% step %}

#### Vá para Sesami → Serviços

Abra a aplicação Sesami e navegue até Serviços.
{% endstep %}

{% step %}

#### Clique no serviço que pretende editar

Selecione o serviço cuja data de início do calendário da loja pretende configurar.
{% endstep %}

{% step %}

#### Desloque-se até Data de início do calendário da loja

Localize o campo "Data de início do calendário da loja" nas definições do serviço.
{% endstep %}

{% step %}

#### Introduza a data a partir da qual pretende que o calendário comece

Especifique a data de início que pretende que os clientes vejam por predefinição.
{% endstep %}

{% step %}

#### Guardar

Guarde as suas alterações.
{% endstep %}
{% endstepper %}

## O que isto faz

Quando um cliente abre essa página de serviço, o calendário mostrará inicialmente a partir da data que configurou.


---

# 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/pt/reserva/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.
