> 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/es/comenzar/onboarding/troubleshooting/safari-cookies.md).

# Cookies de Safari

Las funciones de privacidad de Safari pueden bloquear algunas cookies y provocar que los flujos de reserva se comporten de forma inesperada.

## Síntomas

* Botones que no responden
* Mensajes de sesión expirada
* Los datos del cliente no se mantienen entre pasos

## Acciones recomendadas

{% stepper %}
{% step %}

#### Modos de prueba

Prueba el flujo de reserva en Safari **Privado** y modo normal.
{% endstep %}

{% step %}

#### Configuración de solución de problemas

Pide al cliente que desactive temporalmente “Impedir seguimiento entre sitios” (solo para solucionar problemas).
{% endstep %}

{% step %}

#### Comprobación de la tienda

Confirma que la tienda sea Online Store 2.0 con el embed de Sesami habilitado.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Si el problema solo ocurre en Safari y no en Chrome, a menudo está relacionado con cookies/seguimiento.
{% endhint %}


---

# 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/es/comenzar/onboarding/troubleshooting/safari-cookies.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.