> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/i-synced-my-accounts-but-they-are-not-showing-in-my-crm-what-to-do.md).

# I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?

If you've synced accounts/developers from **Reo.Dev** to your **CRM (HubSpot/Salesforce)** but they are **not appearing**, here’s what to check:

#### **1. Wait for the Sync Interval**

Reo.Dev syncs **newly added or manually sent accounts/developers automatically every 24 hours**. If you're checking before this interval, the accounts may not have been pushed yet.

{% hint style="info" %}
So we recommend to wait for **24 hours** and check again.
{% endhint %}

#### **2. Still Not Showing After 24 Hours?**

If the accounts still do not appear in your CRM after **24 hours**, please reach out for support:

**Contact Support:**

* **Your Reo.Dev Account Manager**
* **Email us at:** <support@reo.dev>

***

#### **Related Guides:**

For additional troubleshooting or setup instructions, check these guides:

* [How to Connect and Configure HubSpot in Reo.Dev](broken://pages/qIlng8yz565Wfi80f2uC)
* [How to Connect and Configure Salesforce in Reo.Dev](/~/revisions/CBft97pr7Q1KpU4KFthF/integrations/output-integrations/crm/salesforce.md)
* [How to Sync a Segment to Your CRM in Reo.Dev](/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/how-to-sync-a-segment-to-crm.md)


---

# 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://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/i-synced-my-accounts-but-they-are-not-showing-in-my-crm-what-to-do.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.