Guide · Duplicate portal leads

One buyer, many property portals

Operational merge so three portals do not create three deals. The same 3BHK shopper clicks Oakshire on 99acres at 10:04 and MagicBricks at 10:11. If both rows become New enquiry with two qualifiers, you double-text them, double-book Saturday, and report fake funnel volume. Speed-to-lead without merge is just faster chaos.

Phone is the merge key
One qualifier thread
Volume metrics lie if you do not merge

Start free Duplicate leads playbook

Definition

Duplicate portal-lead handling is matching inbound enquiries on phone (and email when present) to an existing CoPulse contact on the Project, merging the new source into that timeline, and letting one conversation agent continue — instead of three pipeline cards and three WhatsApp openers.

Why portals manufacture twins

Each portal has its own lead id. CSV v1 import creates new rows. Marketplace allocations are a separate path with no suppression against CRM numbers (G17). Personal WhatsApp adds a fourth copy. RMs think demand tripled.

Duplicate-leads playbook is the job. Speed-to-lead is the sibling clock.

HowTo: merge before the first extra ping

Check phone before the qualifier fires a second greeting. If you only import CSV at 6 p.m., merge in the sheet first — still worse than live match.

Normalize the number Country code. Same digits, one contact.
Match before greet If contact exists, append source, continue thread.
One pipeline card Do not keep three New enquiry deals.
Router still one agent Do not assign developer and broker bots to twins.
Marketplace separately No auto-suppression vs CRM (G17). Operators must not casually mix lists.

How it runs on the platform

CRM identity, then conversation agent. Campaigns to a raw portal dump will triple-message. Autonomous the same. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: 10:04 and 10:11

First portal creates contact, qualifier greets. Second portal same number: operator or import match attaches ‘magicbricks’ source. No second ‘Hi thanks for enquiry.’ Buyer already answering budget. Saturday slot once. Funnel counts one New enquiry.

If two numbers (work and personal), you may still have twins — merge when they say so. Do not merge different people who share a family phone without asking.

Match decision

When to merge vs keep separate.

Signal	Action	Risk if ignored	Notes
Same phone	Merge	Double WhatsApp	Default
Same email, different phone	Review	Two people	Ask
Same name, no identity	Do not auto-merge	Wrong deal mash	Wait
Marketplace vs CRM same phone	Operator choice	G17 no auto-suppress	Do not mix casually
After two qualifiers already spoke	Merge + apologize	Trust	Stop one bot

Honest limitations

CSV v1 (G13). No marketplace-CRM suppression (G17). We do not claim a consumer-grade identity graph. SMS not a third merge channel today.

Keep this Duplicate portal leads article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Customers contacts / pipeline. CSV import v1 with care. Inbox. Qualifier on WhatsApp. Duplicate-leads playbook. Canonical playbook: Duplicate leads playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Speed to lead. New enquiry. Pipeline.

Frequently asked questions

CRMs whose New enquiry count is 3× unique phones.

Will CoPulse auto-merge every portal webhook?

Match on phone when the number is present. Garbage rows without numbers will not magically collapse.

Two agents already chatting?

Stop one via router/inbox. Merge the contact. Apologize once.

Does merge change campaign analytics?

Campaigns are sends to recipients. Clean lists before blasts. Conversion remains reply rate.

Family shared phone?

Do not auto-merge different deals. RM notes.

Brokers vs developer portals?

Still one human. Scripts may differ by Project, not by duplicate cards.

Wallet?

Duplicate sends waste wallet. Merge is cheaper. Pricing.

Hub, sibling guides, canonical playbook, product, pricing.

One number, one card, one greeting

Match portal rows on the Project before the second Hi — duplicate-leads playbook.

Get started free