> For the complete documentation index, see [llms.txt](https://docs.salesmap.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmap.kr/videos/setup/template/note.md).

# 노트 관리

여러분들은 고객과의 히스토리를 어떻게 관리하고 계신가요?\
세일즈맵에서는 각 영업 기회별로 노트, TODO, 이메일 이력 등을 모두 한 곳에서 관리할 수 있는데요.

이때, 노트에 모든 영업 히스토리를 기록하면, 모든 인원이 확인할 수 있고 \
스니펫 기능을 활용해 반복되는 템플릿을 저장해두고 불러와 활용할 수 있죠.

이번 영상에서는 모든 현황을 한 곳에서 관리할 수 있는 노트 기능에 대해 알려드릴게요.

{% embed url="<https://www.youtube.com/watch?v=rsBAc9Fhbl0>" %}


---

# 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.salesmap.kr/videos/setup/template/note.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.