> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/working-with-prebuilt-crm-modules/modules/system-modules/notes.md).
# Notes
The Notes module stores all notes added across various modules as records. Notes appear as a built-in field in every module, allowing a field for adding notes to each record. You can add reminders, to-dos, next steps, media files or any relevant information as notes. If needed, the note field can be deleted from a module. Any note added to a record is saved in the Notes module along with an association to the relevant record, functioning as a lookup field. Clicking the **Associated Record** in the Notes module lets you view, edit, duplicate, or delete the record to which the note was added. The Notes module mainly includes Title, Description, Media and Associated Record fields. The note content is saved in the Description field within the Notes module record, and no fields within the Notes module can be deleted.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.pickyassist.com/setting-up-guide/working-with-prebuilt-crm-modules/modules/system-modules/notes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.