> 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/guides/crm/inbox.md).

# Inbox

Connect Gmail or Outlook to Rechat.

By connecting your Rechat account with Outlook and Gmail you will then have all of your emails flowing  in and out of Rechat. &#x20;

* Any email sent from Rechat will be found in the sent folder of your Outlook/Gmail account.
* All emails sent out of Rechat will have real time insight delivered to you by notifying you if user has opened your email or clicked a link in your email.

{% hint style="info" %}
Tip: Call or message your contacts right when you get notified that they are engaged with your email in order to have a higher chance of converting them.&#x20;
{% endhint %}

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

## Set your email signature

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


---

# 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/guides/crm/inbox.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.
