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

# Remove Sesami Branding

Remove the Sesami logo from your booking calendar and notification emails for a fully branded experience.

{% hint style="info" %}
Available on **Pro** and **Premium** plans.
{% endhint %}

## What Gets Removed

When you remove Sesami branding:

* The **Sesami logo** is removed from the storefront booking calendar
* The **email sender name** changes from "Sesami App" to your **store name** on default Sesami notification emails

{% hint style="warning" %}
This applies to **Sesami default emails only**. Sesami Flows emails have separate sender settings.
{% endhint %}

## How to Remove Branding

1. Go to **Sesami > Settings > Storefront Settings**
2. Find the **Remove Sesami Branding** option
3. Enable it
4. **Save**

## Related

* [Pricing](https://help.sesami.co/get-started/about-sesami/pricing.md) — plan comparison
* [Notification Emails](https://help.sesami.co/notifications/notification-emails.md) — email settings
* [Sesami Flows](https://help.sesami.co/automations/sesami-flows.md) — custom email automation


---

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