When you pay an agency or vendor for leads, “we’ll deliver quality leads” is a promise with no teeth unless it’s written into a service-level agreement that defines quality and specifies what happens when leads fall short. A lead-quality SLA is the document that holds a lead provider accountable. This article explains what a lead-quality SLA should contain and how to write one that actually protects you.

What a lead-quality SLA does

A lead-quality SLA (service-level agreement) is a written agreement defining the standards a lead provider must meet, how lead quality is measured, and the consequences when delivered leads don’t meet the agreed standards. It transforms a vague promise (“quality leads”) into enforceable, specific commitments. A strong lead-quality SLA contains several components. Lead definition — precisely what constitutes a valid, acceptable lead (the fit and qualification criteria). Acceptance criteria — the specific, checkable conditions a lead must meet to count (correct title, industry, company size, valid contact details, genuine interest). Rejection process — how you flag and reject leads that don’t meet criteria, and the timeframe for doing so. Replacement or credit terms — what the provider owes you for rejected leads (free replacements, credits, refunds). Volume and delivery commitments — how many leads, how fast. Measurement and reporting — how quality is tracked and reported. The SLA’s power is specificity. “Deliver quality leads” is unenforceable; “deliver leads matching these exact title and firmographic criteria, with valid business email, that we can reject within X days if they don’t match, replaced free of charge” is enforceable. The SLA turns lead quality from a hope into a contractual obligation with consequences — which is what actually holds a provider accountable.

Common questions

What should a lead-quality SLA define first?

The lead definition — precisely what constitutes a valid, acceptable lead. This is the foundation everything else rests on. The definition should specify the fit criteria (exact titles, industries, company sizes, geographies) and the qualification standard (what level of interest or readiness counts). Vague definitions (“decision-makers in tech”) cause disputes; precise ones (“VP-level or above, in software companies of 200+ employees, in these regions, with valid business email”) are checkable and enforceable. Get the definition exactly right, because every other SLA term depends on it.

What acceptance criteria should I include?

Specific, checkable conditions: the required job title or seniority, the target industry and company size, valid and deliverable business contact information, geographic match, and any interest or qualification threshold. Each criterion should be objectively verifiable — you should be able to look at a delivered lead and determine clearly whether it meets the criterion. The more objective and specific the acceptance criteria, the less room for dispute and the easier it is to hold the provider accountable for leads that miss the mark.

How should the rejection process work?

The SLA should specify how you flag leads that don’t meet criteria, the timeframe for rejecting them (e.g., within a set number of days of delivery), and what justifies rejection (failing the acceptance criteria). A clear rejection process is essential — without it, you have no mechanism to enforce quality. The timeframe matters: too short and you can’t properly evaluate leads; too long and the provider can’t manage their accountability. A reasonable, defined rejection window with clear criteria makes the SLA workable for both sides.

What should happen to rejected leads?

The SLA should specify the remedy — typically free replacement (the provider delivers a valid lead to replace each rejected one), credit (rejected leads credited against future delivery), or refund. Replacement is most common: you only pay for leads that meet criteria, and rejected ones are replaced at no cost. This is the consequence that gives the SLA teeth — without a defined remedy for rejected leads, the acceptance criteria are toothless. The remedy ensures the provider bears the cost of leads that don’t meet standards.

How do I measure lead quality objectively?

Through the acceptance criteria (each lead either meets the specific, checkable conditions or doesn’t) and through downstream conversion tracking (MQL-to-SQL rates, lead-to-opportunity rates for the delivered leads). The acceptance criteria measure immediate validity; conversion tracking measures whether the leads actually perform. A strong SLA references both — immediate acceptance criteria for clear accountability, and conversion metrics over time to assess whether “valid” leads are also productive. Objective measurement is what makes the SLA enforceable rather than subjective.

What volume and delivery terms should I include?

How many leads over what period, the delivery cadence, and how delivery integrates with your systems (CRM delivery, format, timing). Volume commitments ensure you get the lead flow you’re paying for; delivery terms ensure leads arrive in a usable form and timeframe. The SLA should also address what happens if the provider can’t meet volume commitments. These operational terms, alongside the quality terms, ensure the agreement covers both how many leads and how good they are.

What’s the biggest mistake in lead-quality SLAs?

Vagueness — accepting an SLA with undefined lead definitions and no enforceable rejection or remedy process. A vague SLA (“provider will deliver quality leads, measured reasonably”) is unenforceable and provides no real protection. The biggest mistake is treating the SLA as a formality rather than the document that actually protects you. Insist on specific, checkable lead definitions and acceptance criteria, a clear rejection process with a defined window, and a concrete remedy for rejected leads. Specificity is what makes an SLA worth having.

How this applies to your business

Insist on a specific, enforceable lead-quality SLA before engaging any lead provider, and treat the lead definition as its foundation. Define precisely what constitutes a valid lead — exact titles, industries, sizes, contact requirements, and qualification threshold — because every other term depends on it. A precise, checkable definition prevents the disputes that vague definitions cause and gives you a real basis for holding the provider accountable. Ensure the SLA has teeth through a clear rejection process and a concrete remedy. The acceptance criteria are only meaningful if you can reject leads that fail them within a defined window and receive replacement, credit, or refund. Without this enforcement mechanism, the quality criteria are unenforceable wishes. The rejection process and remedy are what transform the SLA from a formality into actual protection. Measure both immediate validity and downstream performance. The acceptance criteria confirm leads meet specifications at delivery; conversion tracking over time (MQL-to-SQL, lead-to-opportunity rates) confirms they actually perform. Referencing both in your SLA and your ongoing measurement gives you immediate accountability and longer-term assurance that “valid” leads are also productive — protecting you on both quality dimensions. Iscope Digital’s Online Lead Generation service operates under a documented lead-quality SLA with defined acceptance criteria, a rejection process, and replacement terms. For the lead definitions that anchor an SLA, see MQL vs SQL and What is online lead generation?