On a marketplace, verification doesn't concern only the companies that receive requests: it applies just as much to those that supply them. The supply-side players who capture final customers' requests and pass them to the platform are called "sellers" — or, more accurately, providers or sources. A marketplace aggregates sources it doesn't operate itself: that's its strength, but also its point of vulnerability. Without rigorous, continuous control of each source, a single careless or dishonest one would be enough to pollute the average quality of an entire catalogue.
This dossier lays out the verification chain leads-qualifie.ch applies to sellers and their sources, independent of the category concerned: what is checked before a source is activated, what sets a genuinely "verified" source apart from an anonymous list, how each request is tied back to its origin and its consent, how a source's reliability is scored and then continuously audited, and what happens when a source stops following the shared rules. The goal is the same everywhere: to guarantee that every distributed request comes from a known, traceable and accountable origin.
What a marketplace checks about a seller before activating it
Before a seller — which the platform prefers to call a provider or source — passes on a single request, it goes through an intake step that determines whether it's activated at all. The marketplace first verifies its real existence and identity: who operates the source, under what name, through which capture channels. It then asks how requests are actually generated — a form on a specialised site, a comparison platform, a local campaign, an inbound call — and rejects on principle any source that would merely resell a file bought or scraped elsewhere, with no intent expressed by the final customer. A provider that can't describe its capture method precisely doesn't get past this step.
Next comes a series of technical and contractual checks. The platform examines a sample of real requests to verify the validity of contact details, the coherence of the information and the absence of massive duplication. It makes sure the original form collects explicit consent and that the declared categories genuinely match what the source produces. The provider commits contractually to these rules. Finally, a newly admitted source doesn't immediately get full access: it usually goes through a probation period at limited volume, during which its first requests are observed closely before any ramp-up.
What makes a lead source verified
Not all sources are equal, and a serious marketplace only calls a source "verified" when its capture method is documented and reproducible. In concrete terms, this means you know how, when and through which channel the final customer's purchase intent was collected: the origin of the request (the site or form), the timestamp of capture, and the exact wording of the consent shown to the customer at the moment they agreed to be contacted. A verified source stands in direct opposition to an anonymous contact list, whose provenance, age and collection conditions are unknown.
This requirement has practical consequences. A verified source passes on fresh requests, captured a short time earlier, not contact details dug out of an old stock. It documents a single origin per request, without mixing several channels that can't be told apart. And it accepts that the operator can, at any moment, follow the thread back to check one of these elements. It's this ability to prove origin — not just assert it — that separates a genuinely verified source from a mere provider who promises quality without ever being able to furnish evidence of it.
Traceability: tying every request to its source and its consent
Verification would be nothing but a promise without traceability. On a structured marketplace, every request passed on carries metadata linking it to its source of origin and to the corresponding consent event: which provider produced it, through which channel, at what moment, and with what proof of the final customer's agreement. This audit trail, invisible to the receiving company day to day, is what makes the system accountable for its results rather than dependent on the sources' good faith alone.
Its value shows above all when a problem arises. If a receiving company reports an unreachable contact, a disputed consent or incorrect information, the operator doesn't just log the complaint: it traces the request back to its source, checks the associated consent record, and compares what was declared with what actually happened. Each complaint traced this way feeds the reputation of the source concerned. Traceability is therefore not mere archiving: it's the mechanism that turns an isolated incident into a usable signal, and that makes it possible to attribute each defect to the precise source responsible, without penalising the entire catalogue.
Source reliability scoring and continuous audit
A source isn't verified once and for all then forgotten. Each provider carries a living reliability score, recalculated from signals observed on the ground: the reachability rate of the contacts it passes on, the proportion of duplicates, complaints received, coherence between the information announced and that observed, and respect for the perimeter — categories and zones — it declared it would cover. This score isn't a one-off judgement but an average that evolves as new requests are distributed and tracked.
On top of this automatic monitoring comes a periodic human audit. The operator re-examines a sample of a source's requests, re-checks consent records, and compares the capture method declared at intake with what the source now actually produces — a source can indeed drift over time, change channel or loosen its controls without saying so. The score then determines the source's standing in the system: distribution priority, authorised volume, level of scrutiny. This mechanism is the exact mirror, on the supply side, of the scoring applied to receiving companies on the demand side — the same discipline is exercised symmetrically on both sides of the marketplace.
What happens when a source fails: downgrade and exclusion
Verification would carry no weight if a breach went without consequence. When a source sees its reliability score deteriorate, the first response is graduated: its flow is narrowed, more of its requests are held for checking, and its authorised volume is lowered until the situation clears up. This progressive downgrade leaves a good-faith provider the chance to correct a one-off problem — a faulty form, a channel temporarily of lower quality — without being immediately removed.
But some breaches aren't passing errors. A fabricated consent, the resale of a scraped file presented as fresh requests, or systematically unreachable contacts signal a source that doesn't respect the shared rules, and lead to its outright exclusion from the catalogue. It's precisely because the sanction exists and is applied that verification means something: it protects both the receiving companies, which don't get requests from a disqualified source, and the serious providers, whose work isn't drowned in the flow of a careless competitor. The continuity of this control — intake, traceability, scoring, sanction — is what sets a leads marketplace apart from a plain resale point.