> ## Documentation Index
> Fetch the complete documentation index at: https://hopsdocs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# CRM hygiene

> Find and fix missing fields, bad close dates and duplicates.

CRM data decays quietly: close dates pass, fields stay empty and duplicates pile up. Hops checks the CRM every week and sends each owner a list of what to fix.

<Info>
  **How it runs:** Scheduled. An automation runs every Wednesday at 9:00 AM, posts each owner's list and saves the results as a Doc. You can also ask Hops any time.
</Info>

## What it does

* **Finds the usual problems.** Past close dates, missing required fields, duplicate contacts and deals with no next step.
* **Groups by owner.** Each owner gets only their own records, so lists are short and actionable.
* **Suggests merges.** Duplicate contacts and companies are listed with the record to keep.
* **Checks required fields per stage.** A deal in Negotiation needs more fields than one in Discovery.
* **Never edits records without approval.** Hops proposes fixes and waits for your go-ahead.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/revops-crm-hygiene.gif?s=3246179cc54022678a580dab90505712" alt="Salesforce connection, Hops scanned opportunities for missing fields, past close dates and duplicates" width="1440" height="810" data-path="images/use-cases/revops-crm-hygiene.gif" />
</Frame>

## Ask Hops

Copy a prompt into any chat with Hops, or mention `@Hops` in a Space.

```text theme={null}
Which Salesforce deals have a close date in the past?
```

```text theme={null}
List deals in Negotiation that are missing a next step, grouped by owner.
```

```text theme={null}
Find duplicate contacts at Acme and suggest which to keep.
```

```text theme={null}
Send each owner their CRM hygiene list for this week.
```

Example reply:

> CRM hygiene check done:
>
> * 31 deals have close dates in the past.
> * 12 duplicate contact merges suggested.
> * Lists sent to 7 owners, none edited yet.

## What you get

* **A Slack or Space post** every Wednesday with counts and the owners notified.
* **A saved Doc** in **Docs** with the full list of issues per owner.
* **On-demand checks** for any owner, stage or segment.

## Connections needed

Connect these apps. Each card opens Connections in the app.

<CardGroup cols={3}>
  <Card title="Salesforce" icon="salesforce" href="https://app.hops.ai/my-hops/connections">
    Opportunities, owners and close dates (or HubSpot).
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Where Hops posts the results and nudges owners.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect the apps above in **Connections**.

    See [Connections](/docs/connections/overview).
  </Step>

  <Step title="Pin context">
    Create a **revops** Space and pin the required fields per stage in Space context.

    See [Spaces](/docs/spaces/overview) and [Space context](/docs/spaces/space-context).
  </Step>

  <Step title="Add the skill">
    Create a skill with this prompt so the output has the same format every time.

    ```text theme={null}
    You check CRM hygiene. Find past close dates, missing required fields, duplicates and deals with no next step. Group by owner and send each owner their list. Never edit records without approval.
    ```

    See [Build a skill](/docs/agents/build-a-skill).
  </Step>

  <Step title="Schedule it">
    Run every Wednesday at 9:00 AM. Hops posts the summary to the Space, sends each owner their list and saves a Doc.

    See [Automation](/docs/spaces/automation).
  </Step>
</Steps>


## Related topics

- [RevOps](/teams/revops.md)
- [CRM follow-up](/teams/sales/use-cases/sales-follow-up.md)
- [Troubleshooting](/help/troubleshooting.md)
- [Sales](/teams/sales.md)
- [Chase missing submissions](/teams/sales/use-cases/chase-submissions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.