Marketplace

Resolve duplicate records with a clear audit trail

Give CRM owners a structured process for reviewing duplicate records. The agent compares the records against survivorship rules, merges safe duplicates where permitted, and routes ambiguous cases for a decision.

How it works

A requester submits a duplicate record merge request through Slack, Teams, or the Duplicate Merge Request Form, creating a tracked request row. The agent confirms the request type, retrieves context from CRM records and data quality rules, checks the relevant policy source, and asks for any missing details in chat.

Where policy permits, the agent completes duplicates with clear primary record, matching identifiers, and no ownership conflict and records the outcome without waiting for manual handling. The agent escalates conflicting account ownership, open opportunities on both records, or uncertain survivorship to the responsible owner with a decision summary and supporting context.

An approver reviews the escalation in chat or the Data Quality Review Queue, then approves, rejects, or returns it for more information.

Where people stay in control

People remain responsible for approval exceptions; risky or ambiguous requests.

Adapt it to your organization

Connect the systems listed alongside this description and configure the workflow for your organization’s data, permissions, and policies. Review the named agents, apps, and automations before using them with your own records.