Review duplicates, merge, archive, and restore

Cleanr suggests duplicates from explainable same-business signals. It never silently merges records.

Review a duplicate

On web, open Customers → CRM workspace → Duplicates. A candidate shows the matching signals and their weights, such as an exact email, phone, or address. Select a candidate to compare both profiles.

Review contacts, properties, appointments, quotes, invoices, balances, activity, import sources, and retained billing identities. The preview shows an obligation count and required policy for open follow-ups; it does not expose private follow-up notes in the comparison. Choose the canonical profile and decide which conflicting identity, account-type, organization, and provenance values to keep.

On iPhone, Customer CRM → Duplicates provides the evidence and a read-only comparison. Final merge confirmation requires web because it needs a fresh, accessible side-by-side preview and is never queued offline. Cleanr does not currently ship an Android app.

Confirm the merge

Choose Preview merge immediately before confirmation. The preview includes dependency counts, conflict decisions, record versions, and billing identity state. It expires after ten minutes. Any intervening edit makes it stale.

The atomic merge keeps the source as an inactive alias and records an immutable audit. Historical financial and legal snapshots remain unchanged. Cleanr does not combine Stripe Customers or move PaymentMethods. Existing Stripe identities remain attached to the canonical CRM relationship for routing and support.

Repeated confirmation with the same request key is safe. A concurrent or stale request returns a clear rejection instead of partially moving records.

Dismiss a suggestion

Choose Not a duplicate and provide the applicable reason. Cleanr keeps the dismissal while identity evidence is unchanged. A material email, phone, name, or address change can resurface the pair for review.

Archive and restore

Open a customer on web and choose Archive. Review future appointments, active recurring schedules, open quotes, outstanding invoices, queued communications, contacts, and properties. Acknowledge obligations explicitly. Archiving does not cancel or move them.

Archived customers leave default operational views. Open CRM workspace → Relationships → Archived relationships to restore one. Shared contacts, payers, organizations, and properties are not archived automatically.

Support can rehearse merge compensation from the restricted recovery manifest. Restoration is blocked after subsequent activity makes reversal unsafe.

Access, correct, export, or remove customer data

Customer privacy requests are separate from Archive. Archiving hides a relationship from day-to-day work and can be restored. A completed privacy request removes eligible live identity, revokes portal and communication authority, deletes protected access details, and leaves a permanent archived non-PII tombstone that cannot be restored or repopulated.

For access and portability, open Customers → CRM workspace → Reports and create an authorized export. For correction, update the customer, contact, and property records before starting a removal request. Exports exclude access secrets, payment credentials, and message bodies by default.

On web, open the customer profile and choose Privacy. Select the request intent, then choose Review exact impact. Cleanr checks the latest record online and lists every blocking obligation, including future appointments, recurring schedules, open quotes, balances, queued communications, follow-ups, payment attempts, and payer relationships. Resolve each blocker through its linked workflow before continuing.

The preview separately lists what will be anonymized, which shared contacts or properties remain for other customer relationships, and what must be retained. Financial and tax documents, issued or accepted quote evidence, provider routing identities, non-PII audit history, and import reconciliation evidence remain for the reason shown beside each class. Cleanr never merges, moves, or deletes a Stripe Customer or PaymentMethod as part of this flow.

Type the displayed confirmation phrase and acknowledge the exact scope. Cleanr revalidates the preview immediately before applying it. If the customer changes or the preview expires, review the refreshed scope and confirm again. The operation is never queued offline.

Identity removal can finish before protected photo or prior-export storage is physically deleted. In that case the receipt says storage cleanup pending and keeps the original request ID while durable workers reconcile the remaining objects. Check that request instead of starting a second one.