On the leads-qualifie.ch catalogue, every request carries a precise distribution status: exclusive, reserved for a single receiving company, or shared, sent at the same time to a limited number of recipients known in advance. This status only means anything if it is verifiable and enforced with equal rigour on both sides of the marketplace — because an exclusivity that's announced but not honoured penalises the company that chose it, while an exclusivity imposed without proper recognition penalises the source that captured the request. It's this dual requirement that makes arbitrated exclusivity a central mechanism of how the platform works, rather than a marketing claim printed on a listing.
This dossier explains how this status is set before distribution, how it's technically locked to prevent any undeclared parallel distribution, what it concretely guarantees to the company that receives the request, what it guarantees to the source that submitted it, and how the platform operator arbitrates the disputes that arise despite these safeguards. The angle taken is that of the marketplace as a whole — both sides at once — not that of a single side of the market.
Exclusive lead, shared lead: two statuses arbitrated from the moment of capture
A request captured on the platform is assigned a distribution status the moment it enters the processing queue, before it is ever sent to a receiving company. The "exclusive" status means a single company will receive that specific request, to the exclusion of any other, for the category and geographic zone involved. The "shared" status means it will be sent to several companies at the same time, but within a limit set in advance and disclosed to both sides — never to an indefinite number of recipients decided on the fly according to the commercial opportunities of the moment.
This classification only makes sense if it is arbitrated by a neutral third party rather than declared unilaterally by either side. A source claiming to sell a request "exclusively" without the platform actually locking its distribution elsewhere offers no verifiable guarantee; a company demanding exclusivity without accepting the shared classification rules would destabilise the system for other receiving companies. That's why the status of each request is set and enforced by the platform operator, using identical criteria applied across the whole category, rather than negotiated case by case between two parties that don't know each other.
The exclusivity lock: how the platform freezes distribution
Technically, locking an exclusive request follows a precise sequence. As soon as a validated request is offered to a company whose intake profile matches, it is pulled from the distribution queue for its category and zone, timestamped, and marked as assigned. No other company can subsequently receive it, even if its own intake profile would have matched the same criteria. This immediate removal from the queue is what sets a genuinely honoured exclusivity apart from a plain marketing claim with no control mechanism behind it.
The duplicate-detection system reinforces this lock: every newly captured request is checked against contact details already on record — phone number, e-mail address, the initial request's fingerprint — to prevent the same need, captured twice by two different sources or submitted twice by the same end customer, from being billed and distributed as if it were two separate exclusive requests. The history of every assignment is retained, which lets the operator retrace, in the event of a dispute, the full path of a request from capture through to final distribution.
What exclusivity guarantees the receiving company
For the receiving company, exclusive status has direct operational value: it knows no competitor in its category and zone is working the same request at the same time, which changes how it organises its follow-up — callback timing, the content of its proposal, how much time it spends qualifying the need. That certainty rests entirely on the lock described in the previous section — without it, exclusivity would be nothing more than an unverifiable promise.
If a company notices or suspects that a request announced as exclusive was in fact worked by a competitor — an end customer who mentions being contacted by another company for the same need, contact details already present elsewhere in its own system — it can open a dispute with the operator, who retraces the assignment history kept in the system. It's this verifiable avenue of recourse, not a mere declaration of trust, that gives the exclusivity guarantee its practical meaning on the platform.
What arbitration guarantees the source that submitted the request
Arbitration also protects the source that captured the request, even though its interest is less visible than the receiving company's. A source that scrupulously follows the classification rules — correctly declaring a request as exclusive or shared according to the platform's shared criteria, without trying to artificially maximise its distribution — sees that discipline reflected in the scoring system, alongside the freshness and validity of its requests. Without centralised arbitration, this discipline would go unrewarded: a rigorous source would find itself competing directly against less scrupulous sources redistributing the same contact details beyond the announced cap, in a way invisible from the outside.
The distribution cap set for shared requests plays the same protective role: it prevents a request from being redistributed to a growing number of companies over time, which would eventually devalue the source's flow in the eyes of receiving companies grown weary of requests already widely distributed. By enforcing this cap uniformly across the whole catalogue, the operator protects the value of the capture work done by every source active on the platform, regardless of its tenure or the volume it submits.
Resolving disputes: the operator's ongoing arbitration role
Despite the technical lock and the classification rules, disputed cases do arise: an end customer approached a second time by another company after already responding to the first, a configuration error that links the same request to two distinct intake profiles, a company disputing that it did not receive the exclusivity its intake profile was set up for. In each case, the operator reviews the matter using the timestamped history kept in the system, within a timeframe set in advance, and communicates its decision to both parties involved.
This arbitration function is not an exceptional mechanism reserved for serious incidents: it operates continuously, and its outcomes feed directly into the scoring system described in the other dossiers in this collection — a source whose requests are repeatedly disputed sees its flow downgraded, a company whose complaints repeatedly turn out to be unfounded also has its profile reassessed. It's this continuity, more than the technical lock taken on its own, that lets arbitrated exclusivity stay credible over time, for both sides of the marketplace alike.