> 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/contacts/set-follow-up-reminders.md).

# Set Follow-Ups

Setting follo&#x77;**-**&#x75;ps and acting on them is arguably the single most important activity you should do regularly in your CRM. That's why you utilize a CRM: to quickly set follow-ups and ensure you make contact when reminded.&#x20;

## Steps

1. Get in touch with a contact (Phone, Text, In-person meeting).
2. Log it in your CRM.
3. Set a follow up reminder in your calendar.

If you manage to do these three steps religiously, then before you know it your CRM engine starts running and you are on auto-pilot, growing your business!&#x20;

## Three Ways to Set a Follow Up

1. Set a follow-up with creating a calendar reminder. Select **Create** on the side navigation bar, and then select **Event**.
2. You can also add an event from a contact profile.
3. If you send an email, Rechat will then ask if you wanted to be reminded for a follow-up, with some simple suggestions which will make a calendar event for you and put it in your calendar.

In all above cases you will have a calendar event created for you which will notify you for that event, and then you need to make sure you make that contact and don't skip the activity.

Make sure your account is [connected to Outlook or Google](/appendix/integrations/setting-up-your-contacts.md) so you can have the events automatically added to your other calendars as well.&#x20;

![](https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJZySovZjoLVT1XAonI%2F-MX5TjNeRhRkA_alhbG4%2F-MX5TpnonWl4q_Mkt-c0%2FEvent%20Creation.gif?alt=media\&token=4a538063-69a9-4777-940e-26fc5b2782c0)


---

# 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/contacts/set-follow-up-reminders.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.
