> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/post-processing/e-mail-summaries.md).
# Email summaries
After every conversation, your agent can automatically send a **summary by email** This way, you, your team, or external recipients receive the most important information without having to log in.
### **Set recipients**
You can find the settings here:
* **sipgate sona:** Agent overview → select agent → **Summaries** in the sidebar. Alternatively, drag **Summaries** into the overview via drag and drop.
* **AI Agents:** AI Agents → select agent → **Configuration** → all the way down to **Summary recipients**.
You can **add and edit any number of email addresses** add and edit.
### **What is in the email?**
**Each summary includes:**
* Caller’s phone number
* Your agent’s phone number
* Time and duration of the conversation
* Category
* Summary of the conversation content
{% hint style="info" %}
**For** [**custom playbooks**](/documentation/en/behavior/playbooks.md#eigene-playbooks)**:** Check the box **Summary** for all tasks whose details should appear in the email. Information from tasks that are not checked will not be included.
{% endhint %}
{% hint style="info" %}
**Note:** You can find the complete conversation logs with transcript and note function in the sipgate app. More about this in the article [**Summaries & Transcripts**](/documentation/en/post-processing/summaries-and-transcripts.md).
{% endhint %}
#### View complete conversation logs
The complete conversation logs with **transcript and note function** can be found in the area **Analysis**. More about this at [Summaries & Transcripts](/documentation/en/post-processing/summaries-and-transcripts.md).
---
# 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.sipgate.com/documentation/en/post-processing/e-mail-summaries.md?ask=&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.
