adsoraAsk when the homeowner submitted
Lead age should refer to the event you are trying to understand. A record can be new to your CRM while the homeowner’s original inquiry is weeks old. Ask for the original submission time and the delivery time, with timezones. If the vendor re-contacted the homeowner, keep that event in a separate field.
Define what the proposed program means by real-time delivery and how delays will be reported. Avoid assuming a universal age threshold. Agree which timestamp starts the clock, how queued records are handled and whether delayed deliveries require separate approval. The agreement should let your receiving team classify the record without asking the supplier each time.
Request the distribution history that changes the purchase
For aged inventory, ask whether the record was previously sold, how many buyers received it under the seller’s rules and whether there was later contact with the homeowner. A recent file-export date does not answer those questions. Where the supplier cannot document a field, record it as unknown instead of filling the gap with a favorable assumption.
Ask whether the original project request is still the basis of the offer. A homeowner may have completed the work, postponed it or changed the scope. Your team needs a way to record those outcomes. The supplier should also explain how contact restrictions and the approved use of the data are checked for the proposed workflow.
Keep the dates and status in separate fields
| Field | What it should describe |
|---|---|
| Original capture time | When the homeowner first submitted this inquiry |
| Reconfirmation time | A later confirmation event, if one occurred |
| Delivery time | When your system received the record |
| Previous distribution | What the seller can document about earlier delivery |
| Project status | Current status, its source and when it was recorded |
Preserve the original values if the record is updated. A sales rep’s later note should not overwrite the original project request. In a dispute, both the capture details and the later conversation may be relevant, and they answer different questions.
Give different lead ages separate test groups
Track aged and newly captured inquiries separately. Use the same stage definitions, but label each group’s original capture period and receiving date. If you combine them in one source average, you lose the ability to see whether freshness, prior distribution or a follow-up change affected the result.
Budget the contact work as well as the record purchase. A low unit price can still consume substantial team time when many projects are no longer active. Compare the cost per reached homeowner or held appointment using your own results, and keep unresolved records visible. There is no reason to assign a universal conversion rate to either category.
Set a rule for delayed records
A live program also needs a delay policy. Decide what happens when a queue resumes after an outage or a source delivers records outside approved hours. Some buyers may accept that group after review; others may require a pause. Record the decision before the delayed batch enters normal intake.
Bring your lead-age requirements to the source-onboarding discussion. Adsora can review your requested capture and delivery criteria alongside project fit, markets and the receiving setup; the published guide does not promise inventory in any particular age band.