> 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/contact/contact/merge.md).

# 병합

***

동일한 고객이나 회사가 중복으로 등록되어 있는 경우, 데이터를 하나로 병합하여 효율적으로 관리할 수 있습니다.

리드/딜/고객/회사 페이지에서 병합하고자 하는 데이터를 2개 이상 선택하여, `병합` 버튼을 클릭하세요.

예시) `A 웹 폼`을 제출한 고객 1과 `B 웹 폼`을 제출한 고객2를 병합할 경우, 제출된 웹 폼 목록은 A, B가 됩니다.\
단, 시퀀스를 실행 중인 경우 기준에 부합하지 않는 고객이 있다면, 시퀀스에서 삭제됩니다.

<figure><img src="https://266453150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMQWZWEhmSM7VgdI2ju3B%2Fuploads%2FWG4UYRa4DYUyXf9hQoyS%2F%E1%84%80%E1%85%A9%E1%84%80%E1%85%A2%E1%86%A8_%E1%84%92%E1%85%AC%E1%84%89%E1%85%A1%20%E1%84%87%E1%85%A7%E1%86%BC%E1%84%92%E1%85%A1%E1%86%B8.png?alt=media&amp;token=aec87568-0386-4531-b8a8-4d3b67fe8b63" alt=""><figcaption><p>병합</p></figcaption></figure>

{% hint style="danger" %}

#### 데이터 병합 시 주의사항

* 최대 10개의 중복 고객/회사를 하나로 병합할 수 있습니다.&#x20;
* 액티비티, TODO, 노트, 첨부파일 등의 이력은 함께 병합됩니다.&#x20;
* **본 작업으로 삭제된 데이터는 다시 복원할 수 없습니다.**
  {% endhint %}

<figure><img src="https://266453150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMQWZWEhmSM7VgdI2ju3B%2Fuploads%2FknScmNltKTlMY5nNDKRe%2F%E1%84%87%E1%85%A7%E1%86%BC%E1%84%92%E1%85%A1%E1%86%B8%20%E1%84%80%E1%85%A7%E1%86%BC%E1%84%80%E1%85%A9%20%E1%84%86%E1%85%A6%E1%84%89%E1%85%A6%E1%84%8C%E1%85%B5.png?alt=media&amp;token=aaed078b-c7ee-4083-9640-ff52a61decdd" alt=""><figcaption><p>병합2</p></figcaption></figure>


---

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