> 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/february-5th.md).

# Daily Email

### Daily Email

Starting today, every morning at 6AM (Your local time), Rechat will send a "daily" email to you.

This email is supposed to give you an overview of all the important aspects for the day:

1. Your daily schedule. So you can have a quick peek into your day.<br>
2. Upcoming celebrations for the next week, including birthdays, wedding and home anniversaries.
3. Your latest deals and the opportunity to start marketing them with a click.
4. Insights into the emails you sent in the past 3 days.
5. A schedule of upcoming Rechat webinars, so you can join us and fine tune your Rechat skills.

We will be adding more features to the daily email to make it as useful as possible.


---

# 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/february-5th.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.