Receiving requests through a leads marketplace is not automatic. Many receiving companies — the "buyers" in the platform's sense — blame the marketplace for disappointing results that in fact stem from the way they use it. A two-sided marketplace runs on a precise mechanism: verified sources, request scoring, traceability of every contact, a capped distribution. Poorly understood, that mechanism produces recurring misunderstandings that have nothing to do with the intrinsic quality of the requests in circulation.
This dossier lists the five most common mistakes made by receiving companies on leads-qualifie.ch, independent of any single category, and explains for each what the platform's actual workings imply. The goal is not to measure any return, but to understand how to make the most of the structural mechanisms — the two-sided model, scoring, arbitrated exclusivity, traceability, the consent framework — rather than working against them. Each mistake described below shares the same root: confusing how a structured marketplace works with how a plain provider reselling a file works; correcting them therefore comes down to using the platform as it is designed.
Mistake 1: judging a source by volume, not by quality
The first mistake is to assess a source of requests solely on the quantity it sends. A marketplace aggregates several sources, each scored continuously; yet raw volume says nothing about reachability, freshness, or consent. A source that fills the queue with contacts that are easy to produce but rarely reachable can look attractive on a dashboard and still feed poorly qualified relationships.
On leads-qualifie.ch, every active source carries a scoring history that reflects the field returns observed on its requests. A buyer who favours the most prolific source, ignoring that signal, exposes itself to contacts the system is precisely in the process of downgrading. It is wiser to read the quality signals the scoring exposes — share of reachable contacts, coherence of the information, how recent the consent is — than to chase the sheer number of requests received. In practice, a smaller but steady source, whose contacts answer and confirm their need, is worth more than an abundant flow that clogs the callback schedule with dead ends; it is this steadiness, not the one-off spike, that the scoring seeks to reward.
Mistake 2: a poorly configured intake profile
The second mistake comes from an intake profile set up in haste: a category that is too broad, a loosely drawn geographic zone, an unrealistic monthly volume. The platform distributes according to this profile, so an approximate configuration produces off-target requests, which the buyer then wrongly blames on the marketplace's overall quality rather than on its own settings.
The intake profile is the interface between the buyer and the distribution queue specific to each category and zone. Narrowing the zone to the real coverage area, choosing the most precise category rather than an umbrella one, and declaring a sustainable volume all channel genuinely relevant requests toward the company. A profile refined in light of observed returns captures the right requests, whereas one left on default mixes in needs that should never have reached it. It is better to start with a narrow scope, observe how relevant the first requests are, then gradually widen the zone or category rather than the reverse: an overly ambitious profile from the outset drowns useful requests under unsuitable ones and distorts the reading of the sources' real quality.
Mistake 3: confusing exclusive and shared leads (and reacting too late)
The third mistake is to treat a shared lead as if it were exclusive. On a marketplace, the exclusive/shared preference is explicit and the number of recipients is capped and known in advance. A shared lead is, by design, sent to a small number of competing companies: response speed is decisive, because the customer will talk to whoever calls back first.
A buyer who calls a shared lead back several hours after receiving it arrives after a competitor, gets a lukewarm reception, and then wrongly concludes that "the request was bad". Freshness is one of the factors that weigh most heavily on conversion into an appointment. Understanding the difference between the two regimes — and matching one's responsiveness to the regime chosen — avoids blaming the quality of the request for what is really an overly long callback delay. In concrete terms, this means organising a fast handling — a callback within minutes of receipt, a follow-up message if the first call fails — rather than waiting for a free slot at the end of the day, by which point a shared lead has already been largely worked by the other recipients.
Mistake 4: ignoring traceability and never disputing
The fourth mistake is failing to use the traceability the platform provides. Every request keeps the imprint of its capture: source, timestamp, channel, proof of consent. A buyer who ignores these elements gives up a way to verify a contact's legitimacy and to tell an isolated case apart from a recurring source problem.
Its corollary is never disputing. The arbitration mechanism exists precisely to flag an unreachable contact, a duplicate, or a need outside the covered area — and those reports feed the scoring of the sources. A buyer who suffers in silence deprives the feedback loop of the information that, aggregated with other returns, downgrades a failing source. Disputing within the set window is not a quarrel: it is the normal mechanism that keeps the average quality of circulating requests up. A buyer who disputes regularly, with precise reasons and within the deadlines, contributes directly to cleaning up the flow it benefits from: its reports refine the scoring, push out failing sources and, over time, improve the average quality of the requests it receives itself.
Mistake 5: neglecting the three-party consent framework
The fifth mistake is to treat a lead as a plain contact file, forgetting that the marketplace rests on a three-party consent framework: the final customer, the source that captured the request, and the receiving company. The customer consented to being contacted again by a professional in the sector about a specific need — not to having their details reused outside that scope.
Contacting a customer for an entirely different purpose, passing their data to a third party, or soliciting them long after the consent's relevance has lapsed exposes the buyer and erodes the trust the whole model depends on. Compliance (the FADP framework) is not a side formality: it underpins the legitimacy of every match. The prudent buyer records the purpose of the contact, respects the scope of the consent, and handles the data received with the same care as data it collects itself. In concrete terms, this means keeping a record of the consent attached to each request, limiting the retention of the contact details to the time needed to handle the need, and being able to answer any request for access or deletion from the customer — all obligations that flow directly from the three-party framework.