> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/ai-memo.md).

# AI Memo

Lucy just got a major upgrade. Introducing AI Memo — a new way to capture your client conversations and turn them into clear, actionable next steps automatically.

{% embed url="<https://rechatq.wistia.com/medias/py3p0sms8v>" %}

Lucy just got a memory upgrade.

Meet **AI Memo** — a new way to capture your client conversations and turn them into clear next steps automatically.

Record a meeting (with permission), or simply dictate what just happened. Lucy will generate a clean summary, key takeaways, and suggested follow-ups — no note-taking required.

This is built for how agents actually work. Not every conversation happens on Zoom. After a showing, open house, or client call, just speak for 15–30 seconds and let AI Memo handle the rest.

Because it’s built into Rechat, your notes are instantly connected to your contacts and deals. No extra tools, no copy-pasting, no missed details.

Next time you finish a client conversation, don’t rely on memory.

Open Lucy, use AI Memo, and let every conversation turn into your next follow-up.

{% content-ref url="/pages/oA1bJri1aDf3Y6XQRqCu" %}
[Lucy: Your AI Assistant](/guides/lucy-your-ai-assistant.md)
{% endcontent-ref %}


---

# 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://help.rechat.com/whats-new/ai-memo.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.