> 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/how-to-enable-two-way-calendar-sync-google-and-outlook.md).
# How to Enable Two-Way Calendar Sync (Google & Outlook)
**How to Enable Two-Way Calendar Sync**\
Easily sync your Google Calendar or Microsoft Outlook with Rechat for seamless scheduling.
🗓️ **Activate Calendar Sync in 3 Easy Steps:**
1️⃣ Go to My Settings → Calendar Export.\
2️⃣ Select the events you want to sync.\
3️⃣ Click Generate URL — that’s it!
No need to copy or import a URL—just click **Generate URL** to activate syncing automatically! Once set up, your Rechat events (appointments, showings, and more) will sync effortlessly with your selected calendar.\
\
**Note:**
* Syncing from Rechat to Google or Microsoft calendars may take up to 15 minutes.
* If you're already synced, you'll need to disconnect and reconnect to apply this update.
* Don’t forget to generate a new URL whenever you change your event type selection.
{% embed url="" %}
If you have questions, our team is here to help. Happy scheduling! 🚀
---
# 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/how-to-enable-two-way-calendar-sync-google-and-outlook.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.
