Modes and settings

Open CRM Cleaning ▸ Settings. Changes take effect when you click Save settings.

​

One setting per check: Off, Ask me, Do it

Every check that can change your CRM has one setting. That setting is the only thing that decides what happens to the changes it finds. The checks that only report have Off or Report instead: Report lists what they find in Findings, and Clustr never changes it.

​

Apply to all rules

Autonomy ▸ Apply to all rules sets every check that changes your CRM at once. Pick Off, Ask me or Do it, then change the few checks you want to treat differently in What the agent checks. Findings keep their own setting: Apply to all rules never turns them off. Do it never reaches Standardise values: it rewrites values to the ones you mapped, so it stays on Ask me until you set that row itself to Do it. Off and Ask me reach it like any other check. A check you change shows “not the default”, with a link to reset it. When your checks use different modes, the control reads Set per rule.

​

Suggestions to switch to Do it

When your team keeps accepting a check’s changes, Clustr suggests letting it run on its own. The suggestion appears under the check, with Switch to Do it; click it, then Save settings. Nothing changes until you save. A check is suggested when, over the last 90 days:

• it is on Ask me;
• it is Format & casing or LinkedIn URL (merges and company changes are never suggested);
• people accepted at least 20 of its changes, and dismissed or reverted none. From 50 decisions on, one dismissal is allowed if at least 98% were accepted. Any revert rules it out.

Changes Clustr applied on its own do not count: only decisions people made. The weekly email lists up to two of these suggestions under “Ready to run on its own”. Over the API, read them from GET /api/crm/cleaning/settings/suggestions.

​

Defaults

Until you change anything: The defaults apply to manual scans as well as scheduled ones. A new workspace with these defaults gets formatting fixes written on its first manual scan.

​

Schedule

Turn on Run on a schedule to scan automatically. Off means manual scans only. Pick the cadence (hourly, daily, weekly or monthly), the day, the time and the time zone. The app suggests weekly, Monday at 09:00 in your browser’s time zone. The schedule also turns on the rest of the automatic loop: cleaning a record soon after it changes in your CRM, and the weekly email. The On / Off pill in the Runs header switches the schedule at once, without Save; only a workspace admin can use it. More on scans and runs.

​

Summary email recipients

Summary email recipients (optional) lists who gets the weekly email, separated by commas or new lines. Leave it empty to send it to your workspace admins. The field is shown while the schedule is on, because the email only runs then.

​

Weekly summary highlights

CRM Cleaning sends one summary email a week, plus an immediate email only when changes fail to write to your CRM. Weekly summary highlights has two switches that decide what the summary’s “Worth a look” section may mention. Both are on until you turn them off, and neither sends an email of its own:

• Many new duplicates: when 25 or more new groups of possible duplicates show up in a week, and that is at least 3 times your usual week.
• Field getting emptier: when the share of contacts or companies with a field like job title or industry drops 5 points or more in a week, on an object with at least 100 records.

What each one says is in Weekly summary highlights.

​

Duplicates

Check new records right away checks a contact or company for duplicates as soon as it is created in your CRM, instead of waiting for the next scan. It is on by default and follows the Contact duplicates and Company duplicates checks: a certain match under Do it is merged, anything else waits in Review. It needs the schedule on, and it is off while merges are off. See new records. Through the API the field is realtime_duplicates. Leaving it out means on.

​

Enrichment

The Enrichment section has the master switch, Fill in missing data, the Credits this month meter, When your CRM already has a different value and, once something was sent this month, the match rate (“Found 412 of 640 records (64%): 300 filled, 112 already complete”). The fields to fill, their modes and Which records to enrich are in the Enrichment group of the checks list. See Enrichment. When your CRM already has a different value is set for contacts and for companies. Contacts default to Ask me: the new value is proposed as a change that always waits for you in Review, even on Do it, and the weekly email does not count it. Companies default to Keep yours: enrichment fills their blank fields only. Over the API it is enrichment.when_different, per object type (contact, company), keep or suggest.

​

Record to keep

Record to keep is an ordered list of rules that decide which record a merge keeps: has an owner, furthest lifecycle stage, oldest record, most recently updated, most fields filled, or a field with a given value. Add up to 10 rules from the list, move them up or down, or remove them. The first rule that tells two records apart decides; with no rules, or when none decides, the record with an owner and the most filled fields is kept. See Which record is kept.

​

Match rules

Match rules adds your own duplicate rules, up to 5 for contacts and 5 for companies. Click Add rule, then pick up to 6 fields that must all be the same, such as First name, Last name and Company. A pair only your rule finds is always Likely and waits for you. See Your own match rules.

​

Configure a finding

Ownerless records, Incomplete records and Lifecycle anomalies have a Configure button:

​

Exclusions

An exclusion tells Clustr never to propose a change. In the app, you create one by choosing Dismiss & stop suggesting this on a group in Review, or Dismiss and stop reporting this on a kind in Findings. They are listed under Advanced ▸ Suppressed, where Remove brings the suggestions back. Over the API, an exclusion can be narrower. Each one matches a change when every field it sets matches: An exclusion with no field set excludes nothing. To stop automatic scans, turn the schedule off. To stop every change to your CRM, set Apply to all rules to Off.

​

Quick-start recipes

Advanced ▸ Quick-start recipes applies a ready-made preset. You see what it changes before anything is saved, and nothing is saved until you click Save settings.

​

Settings only the API sets

These settings have no control in the app. Set them with PUT /api/crm/cleaning/settings:

• merge_enabled: the merge switch. It is on unless set to false. Turning it off stops every merge, and leaves formatting, links and enrichment running. Merges already accepted are held, not dropped, and continue when you turn it back on.
• survivorship: how a merge picks the record to keep. The app sets only survivorship.primary_rules (Record to keep); the strategy and field rules are API only. See Duplicates and merges.
• alerts.duplicate_spike_threshold: the fewest new groups of possible duplicates in a week for the weekly summary to highlight them. Leave it out, or set 0, for the default of 25. The two switches are alerts.duplicate_spike and alerts.completeness_drop; leaving either out means on.
• enrichment.contact_budget_share: a fixed share of the monthly enrichment budget kept for contacts, from 0 to 1. Leave it out to let Clustr work it out from how many contacts and companies you have. See the monthly budget.