CRM dedupe and matching rules
CRM dedupe and matching rules
CRM dedupe rules keep Pipeline On from creating messy duplicate records.
Set these rules before sending a large number of recovered leads into your CRM.
Recommended match order
Use this order when possible:
- Email.
- Phone.
- Full name and postal code.
- Address.
- Manual review.
What to do when a match exists
If the CRM already has the person:
- Add a note.
- Create a task.
- Attach page visited.
- Update blank fields only.
- Route to assigned owner if one exists.
Do not blindly create another customer.
What to do when no match exists
Create the object that fits your workflow:
- Lead.
- Customer.
- Contact.
- Opportunity.
- Estimate request.
- Task.
For uncertain records, create a review task instead of a customer.
Required fields
Some CRMs require phone, job type, business unit, campaign, or service address.
Use Zapier filters or fallback paths so missing optional Pipeline On fields do not break delivery.