How to handle channel partner leads without conflict

Agree the attribution rules in writing before anyone dials: what proves that a partner introduced a buyer, how long that claim lasts, and what happens when a buyer reaches you by two routes. Then keep the calling lines clean. The developer calls its own enquiries, each partner calls the buyers it registered, and nobody calls a buyer registered to someone else. Script every agent to name the company it calls for in its first sentence, so the buyer always knows who is on the line and nobody can later claim otherwise.

This post is part of our guide to AI lead qualification for Indian real estate.

Where the conflict comes from

A channel partner is a broker who brings buyers to a developer's project in return for a commission. Partners are how many projects reach buyers the developer's own marketing never touches. They are also a steady source of disputes, and the typical one has a simple shape: two parties believe they introduced the same buyer.

It happens easily. A buyer sees a partner's post about your project, then sees your Meta ad and fills in the form. Your team calls them. The partner brings them to the site on Saturday. Both have a fair claim, and whoever loses the argument feels cheated.

There is a speed cost too. The Harvard Business Review article The Short Life of Online Sales Leads (2011) listed, among the reasons companies were slow to respond to leads, "rules for distributing sales leads among agents and partners based on geography and “fairness.”" Rules that need a meeting to apply are rules that leave buyers waiting. Good attribution rules can be applied by looking at a record.

Write down the attribution rules

Put these on one page and share it with every partner before a launch, not after the first dispute.

The numbers in those rules are commercial decisions, and they differ between developers. What matters is that they exist before the first call, and that every partner has agreed to the same ones.

Who calls whom

Clear calling lines stop disputes before they start:

• The developer calls its own enquiries. Leads from the developer's ads, portal listings and hoardings are called by the developer's team or its AI voice agent.
• Partners call the buyers they registered. The developer does not ring a partner-registered buyer to "check in". To the buyer that is a second company chasing them; to the partner it looks like poaching.
• The site visit is the handover. When a partner brings a buyer, the developer's site team takes over at the site visit, with the partner named on the lead record.

Buyers do not read partner agreements, so some will ring the developer's number directly after a partner has registered them. The agent should answer, help and record the call like any other. Whether the buyer mentioned a partner goes on the record, and the attribution rules, not whoever picked up the phone, decide who earns the commission. Turning a buyer away because of a registration they have never heard of helps nobody.

To keep a registered buyer off the developer's calling list, exclude the number from your import, or keep partner-registered leads in their own batch. Do not put registered numbers on the suppression list. That list means "never call this person again", and a number on it is never rung by the agent again, even when the buyer is ready to book.

Calling for a developer versus calling for a broker

The rule that prevents the worst confusion is simple: the agent should name the company it calls for in its first sentence. Every time. At BlackWolf that opening is written into each agent's brief when we set it up with you. It is a scripted line, not a check the platform runs, so read it before the agent goes live.

A developer's agent names the developer. The buyer knows they are speaking to the company that builds the project.

A partner's agent names the partner's own firm, not the developer. It can say it is an authorised partner for the project if that is true. It never says it is calling from the developer. When we set up an agent, the company it names on the call is set separately from the account, because for a channel partner the two differ.

That separation matters. Set up a partner's agent as though it sold for a single developer, because that developer's projects come first in the brief, and it will describe itself that way to buyers. Then, when it recommends another developer's project that fits a buyer better, the right answer looks like a mistake. The fix is to the identity, not the recommendation: the agent says who it really is, a partner across developers, and recommends what fits the buyer's area and budget, whoever built it.

Here is the difference in practice, for an illustrative 3 BHK enquiry in Gota, Ahmedabad. The words in italics stand for the real names, and the English under each line is a translation for this page, not part of the call:

Developer's agent: "Namaste, main Riya bol rahi hoon, developer ka naam ki taraf se. Aapne Gota mein hamare project ke baare mein enquiry ki thi. Kya abhi do minute baat ho sakti hai?"

(Hello, this is Riya, calling on behalf of the developer's name. You had enquired about our project in Gota. Could we talk for two minutes now?)

Partner's agent: "Namaste, main Riya bol rahi hoon, partner firm ka naam se. Hum Gota mein developer ka naam ke project ka naam ke authorised channel partner hain. Aapne project ka naam mein 3 BHK ke baare mein poocha tha. Kya abhi do minute baat ho sakti hai?"

(Hello, this is Riya, from the partner firm's name. We are an authorised channel partner for the developer's name's project name in Gota. You had asked about a 3 BHK in project name. Could we talk for two minutes now?)

The developer's agent can say "our project", because it is. The partner's agent says whose partner it is, names the developer, and talks about the project by name, not as its own. Both name the company in the first breath, and both ask before carrying on.

Two rules follow for any partner's agent:

• Do not overclaim. Never say "we have" about a project the partner has no relationship with. Saying a project exists in an area is information. Implying you can sell it is not honest.
• Answer only from the documents the partner has. Prices, offers and possession dates come from what the developer has shared. A pre-launch price or a special offer that is not in those documents is a callback, not an answer.

And if a buyer asks "who do you actually work for?", they get a straight answer.

Qualify the same way, whoever calls

A buyer should not get a better or worse conversation depending on which company reached them first. Use the same lead qualification questions (configuration, locality, possession timeline, budget, purpose, financing) and the same definition of a qualified buyer across your team and your partners. Then a partner's "qualified" means the same as yours, and the site team knows what to expect. How to ask those questions well is in how to qualify home buyers on budget, BHK and timeline.

The record settles disputes

Most attribution arguments are about facts nobody wrote down: who spoke to the buyer first, and what they were told. BlackWolf keeps every call against its lead, with the transcript and the recording. When a dispute comes up, you can check:

• When the buyer was first called, and by whom.
• Whether the buyer mentioned a partner on the call.
• What price or offer the buyer was told, and where it came from.

Pair that with a timestamped registration from the partner, and a dispute can settle on the record rather than on who argues longer.

Partners with their own agents

Some partners run their own AI agent to call the buyers they source. That works well, with one condition: each company's data stays its own. In BlackWolf every lead, call, recording and document belongs to one workspace, and every query is scoped to it. A partner's workspace holds the partner's leads; the developer's holds the developer's.

When a partner hands a buyer to the developer, decide what goes across: usually the qualifiers, the visit time and a short summary. Before sharing a buyer's details between companies, check what your privacy notice and data-protection obligations allow. Our post on the DPDP Act for sales teams is a starting point.

Speed still counts for a partner-registered buyer. If partners hold buyers but do not call them, the buyer goes cold while the registration stays valid. Agree a response expectation in the partner terms.

Each company that calls buyers also carries its own obligations on commercial calls. Our compliance page sets out which parts BlackWolf handles and which stay with the company placing the call.

What to do next

Write your attribution rules on one page, share them with every partner before the next launch, and set up your calling lists so that no registered buyer is on two of them. The real estate page shows how developer and partner agents are set up.