> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/daily-operations/reception-notes.md).

# Reception notes

Open Reception Notes under Hotel Operations or use the notification button at the top.

![Reception Notes](https://582852079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH3QewPp8q2H0UbFFNMYS%2Fuploads%2Fgit-blob-c3afd15a86d4a02aca09b91e90e0639e5af5685b%2Fnotes.png?alt=media)

## Create a task

1. Confirm the selected property.
2. Open the new-note action on the board.
3. Write a short action-oriented title, such as “Check arrival preparations for room 203”.
4. Add the work required, room information and details the next shift needs.
5. Select status and priority, then save.
6. Confirm that the note appears in the correct column.

## Update progress

The board has To do, In progress and Completed columns. Drag a card or use its status menu to move it. The status menu is also suitable for touch and keyboard use.

Move the card to Completed only when the work is actually finished. Archive notes no longer needed on the daily board and restore them when necessary. Archiving is not permanent deletion.

## If two people edit the same note

If saving is rejected because another employee changed the note, reopen it, read the current version and apply your change again. The board refreshes periodically while open and when you return to the window. Use search and load more if a card is not visible.

Notes are shared within the property. Completing a note does not automatically update room cleaning, reservations or financial records. Also perform the actual operation in its corresponding screen.


---

# 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://docs.interaktifotel.com/en/daily-operations/reception-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.