When direct and partner enquiries point to the same customer

Decide what is actually duplicated

Before cleaning a lead list, agree what each entry represents.

A contact is a person you communicate with. A company or household may have several contacts, even when they share a phone number.

An opportunity is a specific buying requirement. A customer asking about two separate warehouse shipments may need two opportunities. Two enquiries comparing apartments for the same intended purchase may belong to one. Ask what the customer is trying to buy before deciding.

An interaction is an event: a website submission, phone call, email or partner introduction. Several interactions can belong to the same opportunity without being duplicates worth deleting.

This distinction changes the clean-up. You may merge two records for the same person, retain two legitimate opportunities and attach four interactions to the appropriate records. Combining everything into one row would lose useful information.

Match carefully before merging

Standardise phone formats and check email spelling, while retaining the values originally supplied. Confirm the country code rather than guessing it. Use names, the stated requirement and supporting context to review likely matches.

A phone match is a clue. Families share numbers. A purchasing team may use one office line. A channel partner may submit their own number while making introductions for several buyers. Different contact details can also belong to the same person.

Put uncertain matches into a review list. Let a named reviewer compare the records and, where needed, confirm the requirement with the customer or partner. Link records as possible matches while that review is pending. Avoid automatic deletion.

For an approved merge, retain the surviving record ID, the original IDs, source details, timestamps and relevant correspondence. Log who approved it, when and why. Keep enough history to correct a mistaken merge, with access limited to the people who need it.

Keep service ownership separate from partner attribution

Give each opportunity one internal person responsible for coordinating the customer conversation. Other staff and the partner can still contribute. This assignment should not decide commission entitlement.

Keep separate fields for the operational owner, recorded introduction sources, partner claim status and the eventual commercial decision. A later direct enquiry should not silently overwrite an earlier partner introduction. Equally, a partner submission should not automatically convert every existing opportunity into a partner-sourced sale.

Apply the commercial rules already agreed with the partner. These may specify registration requirements, applicable projects, validity periods and evidence needed for a claim. Check what your actual agreement says. “First entry wins” is appropriate only if that is genuinely the agreed rule, and the evidence supports it.

Where the agreement leaves a gap, flag the dispute for the authorised commercial decision-maker. Keep customer service moving while the claim is reviewed. Record the decision and its basis separately from the deduplication action.

Hypothetical worked example from a Pune developer

A buyer submits a website enquiry about a 3 BHK in Project A. The next day, a channel partner registers an enquiry with the same phone number. A site-office call creates a third record.

The reviewer confirms that all three relate to the same buyer and intended purchase. The team keeps one contact and one opportunity, linking all three interactions. It preserves the website submission, partner registration and call note, including their timestamps.

The project sales executive coordinates the conversation. The partner claim remains marked “under review” until the commercial manager checks it against the agreed registration rules. The website being first does not, by itself, settle the claim.

During review, the team finds another enquiry using that number: the buyer's spouse is separately looking for an office unit in Project B. That remains a separate contact and opportunity, with the shared number noted. A phone-only merge would have mixed two people, two requirements and potentially two attribution decisions.

A duplicate enquiry checklist

Take one suspected duplicate group and check:

• Have we confirmed the person, rather than assumed identity from a phone number?

• Is this the same intended purchase, or a separate requirement?

• Are the original interactions and source details still available?

• Can we explain and correct any merge?

• Is one internal person coordinating this opportunity?

• Is partner attribution assessed under the agreed rules, with unresolved claims visible?

Start with a small reviewed sample before switching on automatic matching. Test shared numbers, different spellings, repeat customers and multiple requirements. Check whether the proposed rules wrongly combine any of them.

Where SolvTree fits

For this workflow, SolvTreeAI's automation layer can be scoped around linking channel records, flagging possible duplicates and routing uncertain matches for review. The starting point is your record structure and agreed ownership rules. Commercial decisions stay with the people authorised to make them.

Bring one anonymised example of overlapping direct and partner enquiries to a free 30-minute operational audit. We can map which records belong together, what must remain separate and where a human decision is needed.