> 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/this-week-in-rechat/week-37-in-rechat.md).

# Week 37 in Rechat

Fri Sep 18, 2026

### Simplify Deal Communication Actions

{% embed url="<https://drive.google.com/file/d/1RwRkqpfUSwpLfpbQweXFxszAtdC4L3E_/view?usp=sharing>" %}

Moved Notify Agents and Send Email under the Send Email dropdown in the Deal header, creating a cleaner experience while keeping each communication option clear and easy to access.

***

### Add Digisign Re-Authentication

{% embed url="<https://drive.google.com/file/d/1rNxZfqRaTLhsul3Y4BkXK11BbBFLDV2R/view?usp=sharing>" %}

{% embed url="<https://drive.google.com/file/d/1rNxZfqRaTLhsul3Y4BkXK11BbBFLDV2R/view?usp=drive_link>" %}

Users can now re-authenticate their Digisign connection when the integration becomes disconnected or authentication expires, allowing them to quickly restore the connection and continue working without additional support.

***

### Webhook Management in Settings

{% embed url="<https://drive.google.com/file/d/1yLU-ifzM9JSsEYHKu54zYMZfMVnG7rZh/view?usp=sharing>" %}

Rechat is introducing webhook management so teams can connect key activity in Rechat to external systems and automation workflows. Admins can create webhook subscriptions for supported event types, starting with Deals and Contacts, and use secure signing keys to verify payloads.


---

# 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/this-week-in-rechat/week-37-in-rechat.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.