> 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/booking-experiences/remove-sesami-branding.md).

# Remover a marca Sesami

Remova o logótipo da Sesami do seu calendário de reservas e dos e-mails de notificação para uma experiência totalmente personalizada.

{% hint style="info" %}
Disponível em **Pro** e **Premium** .
{% endhint %}

## O que é removido

Quando remove a marca da Sesami:

* O **Logótipo da Sesami** é removido do calendário de reservas da loja
* O **nome do remetente do e-mail** muda de "Sesami App" para o seu **nome da loja** nos e-mails de notificação padrão da Sesami

{% hint style="warning" %}
Isto aplica-se apenas aos **e-mails padrão da Sesami**. Os e-mails do Sesami Flows têm definições de remetente separadas.
{% endhint %}

## Como remover a marca

1. Aceda a **Sesami > Definições > Definições da loja virtual**
2. Encontre a **Remover a marca da Sesami** opção
3. Ative-o
4. **Guardar**

## Relacionado

* [Preços](/pt/comecar/about-sesami/pricing.md) — comparação de planos
* [E-mails de notificação](/pt/notificacoes/notification-emails.md) — definições de e-mail
* [Sesami Flows](/pt/automacoes/sesami-flows.md) — automação de e-mails personalizada


---

# 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/booking-experiences/remove-sesami-branding.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.