> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/revenue/syncing-opportunities-with-crm.md).

# Syncing opportunities with CRM

Admins can map opportunity fields from their CRM into custom fields in Rox. A pre-requisite for this is that the CRM must be connected to Rox. Please reach out to the Rox team for help.

<figure><img src="/files/ZHuzAsprvo1Y8AFzyra0" alt="" width="563"><figcaption></figcaption></figure>

These fields show up in the Opportunity panel and Rox system intelligently does a dual write-back for these fields. Rox frequently syncs the changes to these fields made in the CRM and any changes made by sellers in the Rox opportunity are written back to the CRM. Refer to [this](/development/engineering/docs/rox-enterprise-integrations/crm-integration.md) page for details on our write-back mechanism.

<figure><img src="/files/ZvQoS3vvzQ1Alakgaxya" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rox.com/development/product/revenue/syncing-opportunities-with-crm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.