> For the complete documentation index, see [llms.txt](https://recatch.gitbook.io/releasenotes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://recatch.gitbook.io/releasenotes/updates/2026-1.md).

# 2026년 1월

### **24시간 쉬지 않는 영업사원, 이메일 자동화**

**힘들게 수집한 리드, 우리 DB 속에 잠들어 있지는 않나요?**고객이 자료를 다운로드하거나 문의 폼을 제출했다면, 지금이 이메일 자동화를 시작할 최적의 타이밍이에요. 도움이 될 만한 자료를 제공하는 것에서 시작해 우리 서비스를 자연스럽게 각인시키는 '자동화 시나리오'를 구축해 보세요.

**💡** 도입 문의가 들어왔을 때, 이렇게 세팅할 수 있어요!

* **1일차:** 우리 서비스의 핵심 가치가 담긴 **'***서비스 소개서***'** 발송
* **3일차:** 우리 서비스를 통해 문제를 해결한 *'유사 업종 성공 사례*' 공유
* **7일차:** 도입 전 궁금증을 해소해 줄 '*자주 묻는 질문 리스트*'와 함께 미팅 제안

<figure><img src="/files/KvpIeBQIe8fvz7UKOrag" alt=""><figcaption></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 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://recatch.gitbook.io/releasenotes/updates/2026-1.md?ask=<question>&goal=<endgoal>
```

`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.