Getting sales to accept your leads
When sales starts sending marketing leads back, “lead quality” quickly becomes the explanation. But poor data is only one reason a lead can be rejected, and treating every rejection as the same problem makes it harder to fix.
Sales may reject a lead because the data is wrong, because the follow-up failed, because marketing and sales are using different qualification criteria, or because the person simply is not ready. Checking a record when it is created can address the first kind of problem. The others need different remedies.
Start with the reason for rejection
The fastest way to improve lead quality is to stop using “bad lead” as a single category.
A sales-accepted lead is one sales has reviewed and agreed meets the criteria both teams set. When that acceptance does not happen, the reason matters.
| Why the lead was rejected | Can checking at capture help? | What needs to change |
|---|---|---|
| Contact data is wrong, incomplete or duplicated | Yes | Check the record as it is created, before it enters the CRM |
| The lead was followed up too slowly or routed to the wrong person | No | Fix follow-up and routing |
| Marketing and sales are using different qualification criteria | No | Agree a shared definition and consistent rejection reasons |
| The person or account fits but is not ready | No | Treat it as a timing and nurture question |
The point is not to decide which cause is more common. It is to identify which one you actually have.
If sales says the email bounced, the number was unusable or the record was duplicated, that is a data problem you can investigate at capture.
If sales says the person was genuine but not ready, changing the contact-data checks will not make that lead ready.
What early checking can fix
Checking a record when it is created gives you a chance to catch testable data faults before they become somebody else's problem.
Contact details can be checked. Duplicate records can be identified. The four checks are applied before the record moves into the buyer's systems.
Some values can also be checked against third-party services. That is different from simply confirming that a field is in the right format.
The limit is just as important. A technically sound record can still be rejected because the account is not ready, because sales and marketing disagree over qualification or because the follow-up process failed.
That is why checking data earlier improves one part of lead quality rather than guaranteeing sales acceptance.
If you need a managed programme built around agreed acceptance criteria, see Managed lead generation.
A bad record gets more expensive later
A data fault found before delivery is one thing. The same fault found after the record has entered the CRM may already have travelled further.
It may have entered reporting. It may have been routed and assigned. A salesperson may have tried to work it. Other systems may already have acted on the record.
The data can still be corrected later. The point is that the downstream work has already begun.
That is why the timing of the check matters. Moving a testable decision closer to the moment the record is created reduces the amount of work that can happen before somebody discovers the fault.
Checking the record at capture
On a LeadScale programme, lead data is checked as the record is created, before it reaches the client's CRM.
Every lead goes through four checks: data hygiene, contact verification, spec and duplication, and human verification. The criteria within them are agreed at the start. Some values can be checked against third-party services, while consent and provenance are recorded with the record.
On business contacts, a person checks the role and company are real and current.
For the technical flow, see lead validation. The buyer guide to lead checks describes the four quality checks.
What a checked record contains
The buyer receives a record whose relevant contact data has been checked before delivery against the programme specification.
The record can also carry its consent and provenance from capture, including when and where it was created.
That does not decide whether sales should accept the opportunity. It gives sales and marketing a cleaner basis on which to make that decision.
A good lead still has to be usable, correct and worth working.
Frequently asked questions
Sales is rejecting marketing leads. What should marketing do first?
Ask sales to record why each lead is being rejected in terms specific enough to act on. Separate data faults from follow-up, qualification and timing. Once you know which cause you are dealing with, you can choose the right remedy instead of treating every rejection as a data-quality problem.
Why is our MQL-to-SQL conversion rate low?
A low conversion rate can have several causes. Start by asking whether the records themselves are usable, whether sales and marketing agree on qualification, whether leads are reaching the right salesperson quickly enough, and whether the people being passed across are ready for a sales conversation.
What makes a lead a bad lead?
There is no single failure. A record can contain bad data, be outside the agreed criteria, be routed badly, arrive at the wrong time or represent somebody who is simply not ready. “Bad lead” is useful only when the reason underneath it is clear.
What causes poor lead quality?
Poor lead quality can come from the data in the record, the criteria used to create it, the process after it arrives or the timing and readiness of the person behind it. Those causes need different fixes.
Would lead scoring have caught the problem?
It depends on the problem. Scoring after a record arrives can help prioritise leads against the signals available to the scoring model. It does not replace checking whether the underlying contact data was usable when the record was created.
What is the difference between validation and verification?
Format validation checks the pattern or format of a value. Verification checks the value against a third-party service to establish whether it is correct and true.
Find out why your leads are being rejected
Book a discovery call and bring the rejection reasons your sales team is using. We can start with the pattern rather than the assumption that every rejected lead has the same problem.