> 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-features/booking-notes.md).

# Booking Notes

### What it is

Staff can attach short text notes to any booking in the portal, similar to sticky notes attached to a booking.

Booking Notes are useful for keeping important context about a customer or appointment, such as:

* “Customer prefers the side entrance”
* “Running 10 min late last visit”
* “VIP — comp the add-on”

Anyone who opens the booking can see the notes.

<figure><img src="https://934599958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FGILHFz0wUg3c3XvQzCzm%2FScreenshot%202026-09-09%20at%2010.56.03.png?alt=media&amp;token=e1e1ca53-1ea9-4371-bd7b-b396c1a372b8" alt=""><figcaption></figcaption></figure>

### How it works

* Each note shows who wrote it (name and profile photo), the note content, and when it was added, displayed in the viewer’s own time zone.
* Notes appear newest first. When a booking has multiple notes, they collapse into a compact stacked view. Click Show more to expand the list.

#### Adding a note

* Enter your note in the text box and click Add.
* You can also use Shift + Enter to add a note.

#### Removing a note

* When removing a note, Sesami asks you to confirm the action first, helping prevent accidental deletion.
* Notes are append-only. You can add or delete notes, but existing notes cannot be edited. This keeps a clean and unalterable history.

<figure><img src="https://934599958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FMIfej5vklAoGTbhXNpwS%2FScreenshot%202026-09-09%20at%2011.04.09.png?alt=media&amp;token=06c9d783-1beb-4a64-8eea-357e04460d07" alt=""><figcaption></figcaption></figure>

### Limits

* A maximum of 10 live notes can be added to each booking.
* Each note can contain up to 1,024 characters.
* Deleting a note frees up space, allowing you to add a new note.

Once the maximum of 10 live notes is reached, the note input is replaced with a “maximum reached” message.

### Soft deletes & traceability

Notes are never truly erased.

Deleting a note only hides it from the Sesami interface. The note remains stored in the database together with information about who removed it and when.

This means:

* Deleting a note frees up space for a new note.
* There is a complete record of who created and who removed each note, including timestamps.
* Nothing disappears without a trace.

### Who appears as the author?

The author is automatically determined based on how the note was created:

* Staff member → their real name and profile photo
* Connected app → the app’s name when an integration adds a note
* Automated/system action → displayed as System

### Rollout

For now, Booking Notes are enabled on request.

Later, the feature can be controlled like other Sesami features, making it available to everyone or limiting it to specific plans.

Contact the CX team: <help@sesami.co>


---

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