> 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/see-email-engagement-directly-in-your-contact-history.md).
# See Email Engagement Directly in Your Contact History
You can now track email delivery and engagement directly within a contact’s history. Instantly see when emails are delivered and opened, without leaving the contact record.
Your contact history just got a **major upgrade**.
You’ve always been able to see **what emails were sent and when**—but now, you can see **how your contacts are engaging** with those emails, all in one place.
With this update, you can now:
* See when an email was **successfully delivered**
* Track when a contact has **opened your email**
* Get quick visibility into engagement **without digging into Insights**
#### Why This Matters
This update helps you take faster, smarter action:
* Follow up at the right time when you know someone is engaging
* Prioritize warm leads who are actively opening emails
* Stay fully informed without switching between tools
No more guessing. No more extra clicks. Just clear, actionable insight—right where you need it.
---
# 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/see-email-engagement-directly-in-your-contact-history.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.
